Working Genius Gap Audit
Use the team map to find missing, overloaded, and frustrated stages
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 99%
The Gap Audit reads a Working Genius team map as a capacity system. Each of the six columns is checked for no genius coverage, a single overloaded contributor, or widespread frustration. The team then compares those visual signals with real work: ideas that never ship may expose missing tenacity, efficient execution without new opportunities may expose missing wonder, and chronic reluctance to help may expose missing enablement. A gap becomes actionable only after it explains a recurring project outcome. Leaders can then redistribute responsibilities, protect the scarce contributor, borrow support from another team, or prioritize a future hire. This avoids the common mistake of adding headcount when the existing team is simply assigned against its energy.
Origin
Patrick Lencioni illustrated the audit with teams missing tenacity, wonder, enablement, or invention and showed how the map made their recurring problems predictable.
Core principles
- 01Every stage of work needs coverage
- 02One capable finisher is a bottleneck, not full coverage
- 03Frustration clusters predict unsustainable work
- 04Past project failures make map gaps easier to validate
How to run it
- 1
Scan for empty columns
Review all six geniuses and mark any stage where nobody has a genius. Note whether the team only has competencies or frustrations there.
Watch out No green does not mean no one can perform the work; it signals an energy and sustainability risk.
- 2
Find single points of failure
Identify stages where one person carries nearly all required work. Estimate how often projects funnel to that person and whether they are at risk of quitting or burning out.
Pro tip Ask the person directly which tasks create the overload.
Watch out Do not celebrate apparent coverage if it depends on crushing one contributor.
- 3
Inspect frustration clusters
Look for columns with many frustrations. These stages may technically get done while generating delay, avoidance, or resentment.
- 4
Match gaps to evidence
Take recent failed or delayed projects and locate the stage where each one broke. Confirm whether the map predicts the observed failure.
Pro tip Use more than one project before treating a pattern as established.
Watch out Do not blame every failure on genius coverage.
- 5
Close the gap
Choose the smallest effective intervention: reassign work, borrow a genius, reduce load, alter the process, or prioritize that genius in the next hire.
Pro tip Try role changes before adding headcount.
In the wild
A ten-person startup had only one person with tenacity. Every project reached its final stage and landed on Laura, making both her and the team fear she would quit. The map made the bottleneck visible and prompted the team to consider more finishers or a different process.
→ The team recognized completion capacity as a structural risk rather than Laura's personal problem.
A highly organized company has no wonder genius. It executes existing plans well but fails to ask whether customers are unhappy or whether a new product is needed.
→ The audit identifies opportunity discovery, not execution, as the missing stage.
Common mistakes
Counting people instead of coverage
A large team can still have a severe stage gap if everyone clusters around the same geniuses.
Overusing the sole contributor
Routing every final-stage task to one finisher converts insight into burnout.
Confusing wiring with laziness
A frustration shows energy cost, not a lack of hunger or willingness to work.
Is it for you?
Best for
Small teams that can name recurring project failures but cannot explain the pattern behind them.
Not ideal for
Leaders who need to diagnose low motivation, misconduct, or skill deficits unrelated to work energy.
From the transcript
“you only have one te on your team and you're killing her or you're killing him because every time you get to the last stage…”
“any Gap in the six things if there's an egregious Gap causes problem”
“usually teams look at the gap on the thing and in five minutes they're like oh yeah this is why that project failed or this…”
From the episode
Patrick Lencioni: Build an A-Team with Working Genius
Patrick Lencioni