Patrick Lencioni developed the Working Genius model after noticing that some tasks energized him while others made him miserable even when he could perform them competently. He presents the idea through a business fable, then explains six contributions arranged across three stages of work. Ideation begins with Wonder, which notices unmet potential and asks whether something should change, and Invention, which creates an original response. Activation requires Discernment, the intuitive judgment that evaluates ideas, and Galvanizing, the energy that rallies people into motion. Implementation depends on Enablement, the willingness to support what others need, and Tenacity, the drive to finish and verify results. Lencioni argues that most people have two geniuses that give energy, two competencies they can perform without much joy, and two frustrations that drain them. Teams should cover all six rather than expect every person to contribute equally at every stage.

What it gets right

• Separates capability from energy, explaining why a high performer can still be badly matched to recurring work
• Gives teams a shared vocabulary for workflow gaps without turning every problem into a personality conflict
• Makes role redesign practical by focusing on tasks and project stages rather than demanding immediate career changes

What it overstates or misses

• Presents a proprietary six-part model with little independent validation or evidence that the categories are stable traits
• Encourages tidy labels that may understate learning, context, incentives, and the need to perform unpleasant work
• Uses a long fable to deliver a framework that can be explained clearly in a few pages

The book's evidence is largely Lencioni's consulting experience, internal assessment data, and reader recognition rather than peer-reviewed organizational psychology. That does not make the model useless, but it should be treated as a conversation tool, not a diagnosis of permanent human wiring. Its practical value appears when teams map real work, redistribute recurring tasks, and notice missing stages. The verdict: skip the mystique, keep the workflow map.