The L6 Expertise Search
Find the operational expert buried beneath the organizational hierarchy
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 98%
The L6 Expertise Search treats organizational status as an unreliable proxy for useful knowledge. Begin with a specific operational failure, then trace the work downward through the hierarchy until you find the person who understands the system in practice. Evidence includes repeated problem-solving, detailed knowledge of edge cases, recognition from other practitioners, and measurable outcomes—not title or visibility. Once identified, the expert must be given a direct path to decision-makers so that hierarchy does not filter or distort the information. The method is especially valuable during crises, when leaders need precise knowledge quickly and official reporting structures may conceal the people capable of fixing the problem. Its output is an evidence-backed expert with both access and authority to influence the response.
Origin
Michael Lewis describes entrepreneur Todd Park deriving the L6 insight from Sue Henderson, an overlooked hospital employee whose command of medical billing became the foundation for a major healthcare company.
Core principles
- 01Status and expertise are not the same thing
- 02Operational knowledge often resides deep in the hierarchy
- 03Hierarchy obstructs the upward flow of specific knowledge
- 04Decision-makers must actively search below official leadership
- 05Frontline competence matters most when systems fail
How to run it
- 1
Define the operational failure
State the exact outcome that is failing and identify the work required to produce it. Avoid broad questions that invite generic executive answers.
Pro tip Frame the problem around an observable process, such as unpaid claims or broken software.
Watch out Do not begin by asking senior leaders whom they consider important.
- 2
Trace the work downward
Follow the process through departments, contractors, and frontline roles. Look beyond the formal owner of the system.
Pro tip Ask each person who actually resolves the hardest cases.
Watch out An organizational chart shows authority, not necessarily expertise.
- 3
Identify the repeat solver
Find the person with specific knowledge who repeatedly handles exceptions or prevents failure. Seek corroboration from colleagues and operational records.
Pro tip Detailed explanations of edge cases are a strong expertise signal.
Watch out Confidence and seniority alone are weak evidence.
- 4
Validate through outcomes
Test whether the candidate's knowledge explains past results and produces workable interventions. Distinguish genuine expertise from undocumented folklore.
Pro tip Give the candidate a bounded real problem to diagnose.
Watch out Do not expose a live system to an untested recommendation.
- 5
Create a direct information path
Bring the expert into contact with the relevant decision-maker and preserve the substance of their evidence. Remove unnecessary hierarchical filters.
Pro tip Let the expert explain the mechanism in their own words.
Watch out Managers may resist a channel that appears to bypass them.
- 6
Match authority to knowledge
Give the expert enough authority, resources, or sponsorship to implement the solution. Capture their knowledge so the organization does not remain dependent on one person.
Pro tip Convert repeatable expertise into tools, training, or software.
Watch out Surfacing expertise without granting influence leaves the original failure intact.
In the wild
A government enrollment website crashes at launch. Rather than relying exclusively on agency leaders, the response team traces the software through vendors and subcontractors until it finds engineers several levels down who understand the failing components. Those engineers are brought directly into the recovery room and given authority to repair the system.
→ The response shifts from executive speculation to technically informed recovery work.
A healthcare company discovers that clinics perform valid work but cannot consistently collect payment. It searches beyond administrators and finds a basement-level employee who understands thousands of insurer rules and knows how to convert rejected claims into payment. Her knowledge is formalized into a scalable system.
→ Hidden operational expertise becomes the basis of a functioning medical-billing business.
Common mistakes
Starting at the top
Senior leaders may understand strategy while lacking detailed knowledge of the failing process. Treating rank as proof of expertise can prolong the crisis.
Choosing the most confident speaker
Fluent certainty can conceal shallow knowledge. Validate candidates through mechanisms, edge cases, and outcomes.
Finding expertise but withholding authority
An overlooked expert cannot improve the system if their information is filtered or their recommendations cannot be implemented.
Is it for you?
Best for
It is best for leaders diagnosing crises, failed systems, complex operations, or problems that senior management cannot explain.
Not ideal for
It is not ideal when responsibility legally requires a designated executive or when frontline knowledge cannot be safely disclosed.
From the transcript
“it's never at the top of the organization. It's always some someone low in the organization who has some specific knowledge.”
“you've got to go to these people”
From the episode
Michael Lewis on His Journey to Wall Street