No Wrong Door Still Requires the Right Person
The resident should not have to understand your organizational chart to reach the person who can actually move the problem.
A resident asks for help.
The first employee knows part of the answer.
Another program owns another part.
A partner organization has the expertise needed for the next question.
The request starts moving.
So does the resident.
Another phone number.
Another explanation.
Another referral.
Another person who understands only part of the problem.
Activity is happening.
The blocker is still there.
That is exactly the kind of operating problem Los Angeles County is trying to reduce through its newly designated Aging and Disability Resource Connection, or ADRC, network.
Los Angeles County announced the designation on August 6, 2026. Effective July 1, the countywide network brings together the County Aging & Disabilities Department, the City of Los Angeles Community Investment Department, 211 LA, and six regional Independent Living Centers. Its stated goal is to reduce bureaucratic runaround and create a coordinated “No Wrong Door” approach to services. Residents can begin with participating organizations and receive guidance, coordinated referrals, and direct connections rather than being left to navigate multiple agencies alone.
The federal Administration for Community Living describes the larger No Wrong Door model around the same problem. Long-term-service systems can involve multiple agencies, funding streams, intake processes, and eligibility structures. The model is designed to make access more coordinated regardless of where someone first enters the system.
That creates a useful leadership lesson far beyond this particular program.
No Wrong Door does not mean every person solves every problem.
It means the person asking for help should not become responsible for integrating the system.
The Leadership Trap
The trap is process cycling.
A frontline employee receives a question they cannot completely answer.
So they refer it.
That feels responsible.
Sometimes it is.
The next person receives the same resident, recognizes another piece of the problem, and refers it again.
That can also be reasonable.
But eventually the organization has to ask whether the issue is still moving through a legitimate process or simply circulating because nobody has identified the capability actually required to clear the blocker.
That distinction matters.
A resident can be transferred five times and still be no closer to resolution.
A supervisor can also make the opposite mistake.
They see the frustration, step in, take ownership of every part of the request, call every department, handle every conversation, and become the permanent answer whenever something becomes difficult.
That is not better.
One response leaves the resident trapped in process.
The other turns the supervisor into the process.
Manual Engagement sits between those failures.
It is targeted human involvement when the blocker requires the right judgment, authority, trust, access, relationship, or technical skill rather than another generic process step.
What Usually Happens Under Pressure
Imagine you supervise a small resident-services team.
Your employee has a resident on the phone who needs help navigating several services.
The employee has already given the information they know.
They have checked the resources available to them.
The resident has already spoken with another organization.
The employee asks you what to do next.
The easy answer is:
“Send them to this number.”
That gets the call moving.
It gets your employee back into the queue.
It reduces the immediate pressure on your team.
It may also send the blocker somewhere that cannot clear it.
The other easy answer is:
“Give it to me.”
Now the supervisor becomes responsible for everything.
That feels decisive.
It also teaches the team that complicated equals supervisor-owned.
Neither response begins with the question that matters most:
What capability is missing from the current path?
Field Note
Some blockers do not need another process step. They need the right person.
That does not automatically mean the manager.
It may be the program specialist.
The relationship owner.
The person with approval authority.
The employee with direct system access.
The partner who understands the service.
The person trusted to have the conversation.
The leadership decision is not simply whether to escalate.
It is whether the blocker has reached a point where human capability, rather than more routing, is the missing control.
Field Scenario: The Resident Keeps Moving, the Problem Does Not
The following is an illustrative Direct Action scenario based on the type of coordinated-service environment represented by Los Angeles County’s ADRC network. It is not a claim about a specific resident, employee, or event inside the Los Angeles County program.
A service-center supervisor is leading a small intake team.
One of the employees receives a call from a resident trying to understand several support options involving transportation, independent-living assistance, and another community resource.
The employee can explain the general information available to the team.
The resident has already been given one referral.
That referral led to another organization.
Now the resident is back.
The visible problem looks like a complicated request.
The supervisor’s first instinct is reasonable:
Find the next program and send the resident there.
But the employee has already done that.
The problem is no longer a lack of available organizations.
The issue has reached a specific point where the resident needs someone who understands how that part of the service system connects and can make sense of the options.
That is a different blocker.
The frontline employee is not failing.
The employee has reached the limit of the capability available at that point in the process.
The supervisor does not need to take over the resident’s entire situation either.
The leadership requirement is smaller and more practical:
Recognize that the process has reached the point where the right person needs to engage the specific blocker.
That is a decision a team lead or supervisor can realistically make.
No executive authority required.
No countywide reorganization.
No new policy.
Just a cleaner read of what is actually stuck.
The Problem Path
The resident entered through a legitimate service point.
The employee followed the normal process.
Information was provided.
A referral occurred.
The resident remained stuck.
At that point, repeating the same mechanism deserves inspection.
The question is no longer:
Where else can we send this?
The question becomes:
Why has normal routing stopped moving the objective?
That changes what the supervisor is looking for.
The Blockage
The blockage may be knowledge.
It may be authority.
It may be system access.
It may be trust.
It may be judgment.
It may be a relationship between organizations.
The important point is that the supervisor should not confuse the existence of another process step with evidence that another process step will solve the problem.
The federal No Wrong Door model exists partly because fragmented systems can force individuals and families to navigate multiple organizations and duplicative processes while trying to find the right support.
The Direct Action leadership read is narrower:
If the resident keeps moving but the blocker does not, stop measuring progress by the number of referrals.
The Decision Point
This is where developing leaders often get caught between two bad instincts.
The first is under-engagement:
“Send it through the normal process again.”
The second is over-engagement:
“I will handle everything myself.”
Manual Engagement requires a different recognition point.
The leader needs to determine whether the blocker now requires a specific human capability.
Not more people.
Not more attention.
Not a larger meeting.
The right capability.
That is a much more controlled decision.
The Next Movement
Los Angeles County’s ADRC model is built around coordinated access rather than requiring residents to independently navigate every organization involved. Participating partners are intended to provide personalized guidance, coordinated referrals, and direct connections to relevant community resources.
The leadership lesson is not that every frontline employee should become an expert in every program.
That would be impossible.
The lesson is that the system needs to know when general routing has reached its limit.
For the supervisor, the next movement is recognition:
This is no longer just a routing problem.
This blocker requires someone with a capability my current path does not have.
That is where Manual Engagement becomes relevant.
Consequence Chain
Process cycling looks harmless at first.
One referral.
Then another.
Then another.
But each transfer creates work.
The resident explains the situation again.
Another employee reviews it.
Another organization receives it.
Another person has to determine what has already happened.
The original team may receive another call when the referral fails.
Now the organization has created more contacts without necessarily creating more resolution.
The consequence starts spreading.
Repeated explanation creates resident frustration.
Repeated routing creates duplicated staff effort.
Duplicated effort consumes capacity.
Reduced capacity affects the next person entering the queue.
Supervisors receive more escalations.
Employees begin losing confidence in where they should send complex cases.
The resident begins losing confidence that anyone actually owns the problem.
What looked like a simple referral problem becomes a workload and trust problem.
More movement does not automatically mean more progress.
Better Read
The better read is not:
Who else can I send this to?
The better read is:
What capability is missing from the current path?
Is the blocker waiting on authority?
Specialized knowledge?
Direct access?
Relationship trust?
Judgment?
That question does not execute Manual Engagement.
It does something more appropriate for public content.
It helps the leader recognize when continuing normal process may no longer be the best read.
That is the point where a developing supervisor begins moving from managing activity to managing the actual blocker.
How This Fits the Direct Action System
Manual Engagement sits inside Decision Execution and Problem Navigation.
CSA improves the situation read first. It helps the leader understand what is actually happening instead of reacting to the resident’s most recent transfer or the employee standing in front of them.
DEPN then helps the leader determine what kind of problem movement is required.
Manual Engagement becomes relevant when the limiting factor is a human capability that the normal path cannot provide.
From there, communication and ownership still matter. If the right person engages the blocker but nobody understands what changed afterward, the organization can create another handoff failure.
The sequence is controlled:
Read what is happening. Recognize what is actually stuck. Put the appropriate capability on the blocker. Keep the larger objective moving.
The full execution method goes deeper than this article. That boundary is deliberate. The public field note teaches recognition. The paid training provides the complete application structure.
The Point
Los Angeles County’s new ADRC designation gives us a useful operating example because the model starts from a simple recognition:
People should not have to navigate a complicated network alone simply because the services they need cross organizational boundaries.
The Direct Action lesson is equally simple.
A referral can be correct.
A second referral can also be correct.
But if the same blocker remains after repeated routing, continuing to route harder is not automatically leadership.
Neither is taking over everything yourself.
Some blockers require the right person, not more process.
A Practical Field Exercise
Use this the next time a member of your team brings you a problem that has already moved through the normal process.
1. Identify What Is Still Stuck
Do not start with the number of calls, emails, or referrals.
Ask:
What does the person still need?
What specifically has not moved?
Where did normal process stop producing progress?
Keep the blocker small enough to understand.
2. Check Whether You Are Repeating the Same Mechanism
Ask:
Are we about to send this through another version of the same process?
Has the resident already received that kind of referral?
Are we creating another contact or actually changing the condition?
This helps expose process cycling.
3. Identify the Missing Capability
Ask:
Does this blocker require authority, trust, judgment, knowledge, or access that the current team does not have?
Do not immediately decide who should handle it.
First recognize what is missing.
4. Avoid the Takeover Reflex
Ask:
Does the whole problem need me?
Or does one part of the problem need someone with a specific capability?
That distinction protects the employee’s ownership and keeps the leader from becoming the permanent bottleneck.
These questions help you recognize Manual Engagement.
They do not replace the full Manual Engagement process.
What Leaders Should Watch For
The Same Resident Keeps Returning
The problem may not be the resident.
The process may be sending them into a loop.
Employees Keep Asking, “Who Do I Send This To?”
That is sometimes a routing question.
Repeated often enough, it can become a signal that the team has not identified the actual blocker.
Every Difficult Issue Becomes a Supervisor Issue
That is not necessarily strong leadership.
It may be a sign that the team does not know when targeted engagement ends and normal ownership resumes.
The Right Expertise Exists, but the Current Path Never Reaches It
An organization can possess the capability and still fail to apply it at the right point.
More Referrals Are Being Counted as Progress
Referrals are activity.
The operating question is whether the resident is getting closer to the objective.
Why This Matters for Public Sector Leaders
Public-sector work often crosses organizational boundaries.
Residents do not experience those boundaries the way employees do.
They see government.
They see a service network.
They see a phone number or counter that is supposed to help.
Internally, the request may touch separate programs, different agencies, nonprofit partners, distinct authorities, specialized staff, and different systems.
That complexity is real.
The person at the front counter did not create it.
The team lead usually cannot redesign it.
But a supervisor can recognize when the normal process is no longer moving the blocker.
That level of leadership matters because the choice is often made well below the executive level.
Do we send this person somewhere else?
Do I take it over?
Or do I identify the capability missing from the current path and get the right person involved at the point that actually needs them?
That is a practical leadership decision.
Where Manual Engagement Fits
This is where Manual Engagement fits.
It helps leaders recognize when the blocker requires human judgment, authority, trust, skill, relationship, or access that normal process cannot supply.
It is not micromanagement.
It is not the supervisor doing everybody’s job.
It is not bypassing process simply because process feels slow.
It is targeted engagement at the point where human capability has become the missing control.
A full Manual Engagement application goes much deeper.
That belongs inside the Decision Execution and Problem Navigation training path.
What to Practice This Week
The next time somebody on your team says, “I already sent them there,” stop before giving another referral.
Ask:
What is still stuck?
What has the normal process already accomplished?
What capability is missing now?
Does this whole problem need escalation, or does one blocker need the right person?
Am I helping clear the blocker, or am I taking over the work?
Those questions will not execute Manual Engagement for you.
They will help you recognize when you may need it.
Final Thought
“No Wrong Door” is a strong service philosophy because it recognizes something organizations easily forget:
The person asking for help should not have to understand the architecture behind the service.
Los Angeles County’s ADRC network is designed to create coordinated access across county, city, nonprofit, and independent-living partners rather than leaving people to navigate the network alone.
For the leader closest to the work, the lesson is smaller and immediately usable.
Do not confuse another referral with progress.
Do not confuse taking over with leadership.
When the process reaches a blocker it cannot move, identify what human capability is missing.
The resident should not have to understand your organizational chart to reach the person who can actually move the problem.
Put the Right Capability on the Blocker
Manual Engagement is one strategy inside Decision Execution and Problem Navigation.
Start with the Public Sector Direct Action Starter Sheet.
Use it to slow the read, identify the operating pressure, and separate what is visible from what actually needs leadership attention before you react, escalate, delegate, or take over.
From there, the training path moves into structured problem navigation.
DEPN Fast Track provides the compressed starting point for recognizing different problem conditions and selecting the appropriate DEPN strategy rather than treating every blocker the same way.
Get the Direct Action Starter Sheet
Do not leave the read in your head.
Use the Starter Sheet before the next decision, correction, handoff, escalation, obstacle, or recovery move.
It gives you six prompts to assess what is happening, identify the pressure, locate the obstacle, and choose the next controlled move.
After submitting, you will go directly to the download page.
