I've been in the retrospective where someone on the team worked 60-hour weeks for a month to save a delivery and watched leadership celebrate it as a triumph. The person deserved recognition. But what got celebrated was the rescue, not the conditions that made the rescue necessary. This essay is about why that distinction matters more than most organizations realize.
"The organization that depends on heroic individuals to deliver has not built a delivery system. It has built a dependency and disguised it as a capability."
The Celebration Problem
The retrospective follows a familiar script. A difficult program reached its finish line. The deadline was tight, the complexity was real, and delivery happened because a small number of people put in extraordinary effort to make it so. Leadership acknowledges them. The team applauds. The story that gets told afterward is a story about individual capability, commitment, and resilience.
What the organization is doing in that moment is celebrating the rescue without examining what required rescuing. The heroic individuals are real. Their contribution is real. But the frame that treats their exceptional effort as the cause of success, rather than as a response to structural failure, is a diagnostic error. And it is one with consequences.
Heroic delivery is not a capability. It is a compensation mechanism: evidence that something in the delivery structure did not work as designed, and that individual effort filled the gap. Celebrating it without examining what created the gap is how organizations ensure the gap persists.
The distinction matters because the stories organizations tell about how delivery succeeds shape the structures they build to support it. An organization that believes it succeeds through exceptional individuals will invest in identifying and rewarding exceptional individuals. An organization that understands it succeeds through sound structure will invest in building and maintaining sound structure. These are not equivalent strategies, and they do not produce equivalent results.
What Heroism Is Compensating For
Heroic delivery is not random. It appears in predictable conditions: in organizations with structural gaps that become acute under pressure. The specific gaps vary, but the pattern is consistent. Individual effort expands to fill the space that structure was supposed to occupy.
When decision rights are unclear, someone has to make the call anyway. In a crisis, that person is usually the most capable, most senior, or most willing individual available. They make decisions that the structure should have assigned in advance. The delivery succeeds. The authority gap remains unaddressed because the individual filled it.
When teams, functions, or workstreams are not structurally connected, coordination does not happen automatically. Under pressure, it produces crisis. The heroic individual becomes the coordination layer: the person everyone routes through because the formal coordination mechanism does not work.
When escalation thresholds are not defined, decisions accumulate at the top. The individual who manages this traffic, who absorbs the volume and filters what actually needs escalation, becomes indispensable. Their indispensability is a structural problem that looks like a talent asset.
When scope is not formally controlled, it expands. The team that finds a way to deliver despite unplanned growth is celebrated for resilience. The absence of scope governance that allowed the growth is rarely the focus of the retrospective.
When critical knowledge lives in individuals rather than in systems and documentation, delivery depends on those individuals being available, engaged, and healthy. This is a structural fragility that feels like a staffing strength until the individual leaves, burns out, or moves on.
Each of these conditions has a structural correction. None of them requires heroism as a permanent operating mode. But when heroism repeatedly fills the gap, the gap stops feeling like a problem. It feels like a feature of delivery: the hard part that requires good people. The organization has confused the compensation mechanism with the capability itself.
The Organizational Cost
The costs of structural dependence on heroic delivery are real, cumulative, and largely invisible in standard delivery reporting.
The most immediate cost is burnout. The individuals who repeatedly fill structural gaps do so at personal cost: extended hours, compressed recovery time, and responsibility that should be distributed across a functioning system. Organizations that rely on these individuals are drawing down a finite resource. The depletion is predictable. It is also almost never attributed to the structural condition that caused it.
The second cost is talent risk. When delivery depends on specific individuals, the organization becomes fragile in ways disproportionate to the actual talent gap. A single departure, promotion, or reassignment can destabilize a delivery program that appeared robust. Nobody wrote down that the program worked because of one person. But it did.
When the indispensable person leaves and delivery fails, the organization diagnoses a talent problem. The actual problem is that it built a delivery structure that could only function if one person stayed.
The third cost is learning suppression. Heroic delivery produces outcomes that obscure the structural failures that preceded them. The retrospective focuses on the success. The conditions that made success so difficult are noted but not corrected because delivery succeeded. The next project inherits the same structural conditions.
The fourth cost is cultural. Organizations that consistently reward heroic delivery communicate what is valued. Individuals learn that the path to recognition runs through crisis response, not through building structures that prevent crises. The structural work: the quiet, painstaking work of designing governance and defining authority, is invisible in this reward system. It does not produce moments of rescue. It produces an absence of crises that no one celebrates.
Why the Story Persists
If the costs are real and predictable, why does the story persist? The answer is partly cognitive and partly organizational.
Cognitively, rescue narratives are compelling in ways that structural maintenance narratives are not. The story of the individual who stayed late, made the call, and saved the program is vivid, causal, and emotionally resonant. The story of the governance framework that prevented three authority conflicts from becoming crises is invisible by design. Good structure is most evident in what does not happen, and organizations are not well equipped to celebrate non-events.
There is also a more uncomfortable dynamic. Some leaders benefit from heroic delivery culture in ways that are not always conscious. A team that depends on its leader to navigate structural ambiguity is a team that cannot function without that leader. Structural clarity distributes capability. It makes the leader less necessary in the day-to-day. For leaders whose identity is tied to being needed, building structural clarity can feel like an erosion of relevance rather than a contribution to organizational health.
- Visible rescue under pressure
- Personal availability during crisis
- Individual knowledge and indispensability
- Recovery from structural failure
- Resilience in the face of poor design
- Conditions that prevent crises
- Systems that function without specific people
- Knowledge distributed across documentation
- Design that reduces the need for recovery
- Predictability as a delivery output
The Structural Alternative
The alternative to heroic delivery culture is not a demand for mediocrity or a devaluation of individual capability. Strong individuals are genuinely valuable. The argument is narrower: individual capability should be deployed in service of strategic decisions and complex judgment, not in continuous compensation for structural gaps that could be designed away.
The structural alternative begins with a diagnostic reframe. When delivery succeeds through extraordinary individual effort, the first question is not "how do we recognize this person?" It is "what structural condition required this level of effort to compensate for?" The recognition can follow. The diagnosis has to come first.
Post-mortems should identify which structural conditions required heroic compensation: which authority was undefined, which coordination was informal, which scope was uncontrolled. The individual recognition and the structural correction can coexist. They rarely do when the structural analysis is skipped.
When the same individual is regularly indispensable to delivery, the organization has a structural dependency, not a talent asset. The question is not how to retain that individual indefinitely. It is what the structure would need to look like for delivery to function without any single individual being irreplaceable.
If the only recognized contribution is crisis response, the organization will get crisis response. The work of preventing crises, designing governance, documenting authority, building coordination systems, needs to be explicitly valued in how performance is assessed and rewarded.
A delivery program that succeeds when the right people are present has not demonstrated structural resilience. The relevant test is whether delivery would hold up under personnel change, increased complexity, or reduced capacity. If the honest answer is no, the program has a structural problem that current success is temporarily masking.
The goal is not an organization without exceptional individuals. It is an organization where exceptional individuals can do exceptional work: strategic, creative, genuinely difficult work that requires their specific capability, rather than spending their capacity filling gaps that good design could close.
Heroic delivery is a symptom. Treating it as a virtue ensures the disease goes undiagnosed.
The PM Reality Check
Weekly strategies for the human side of delivery. Plus the free Stakeholder Field Guide on signup.