The Great Resignation Is a Programme Risk — Because Capability Leaves Before Headcount Does
Programme capability leaves before programme headcount does.
The Great Resignation Is a Programme Risk — Because Capability Leaves Before Headcount Does
What the first 2021 talent shocks reveal about integration roles, delivery memory and the limits of retention plans
The emerging discussion about a “Great Resignation” is being treated largely as a workforce problem: a matter for recruitment, reward, engagement and human resources. Programme leaders cannot afford that framing. In complex delivery, the risk is not simply that more people may leave. It is that the wrong departures can remove the connective capability on which the programme quietly depends.
A programme may lose only a small proportion of its people and still suffer a disproportionate loss of control. The critical question is therefore not, “How many vacancies do we have?” It is, “Which decisions, relationships and pieces of delivery memory have just become unavailable?”
Programme capability leaves before programme headcount does.
Headcount is a poor proxy for delivery capability
Programme plans describe roles, work packages and milestones. They rarely describe the informal architecture that makes those things work together. That architecture sits with people who know why a dependency exists, which stakeholder can unlock a decision, where a supplier’s estimate is fragile, and which apparently minor issue will become a release blocker.
These people are not always the most senior or the most expensive. They are often the release lead who can reconcile three competing delivery calendars; the planner who knows which dates are political commitments rather than engineering forecasts; the process owner who can translate between operations and technology; or the analyst who remembers why a benefit was defined in a particular way.
When one of them leaves, their post can remain in the organisation chart and their tasks can be reassigned. The capability does not transfer so neatly. It is distributed across judgement, trust and context. A replacement can inherit the files without inheriting the programme.
That distinction matters now. After a year in which many people have reconsidered where and how they work, organisations are preparing for greater labour mobility. Yet most programme risk reporting still converts attrition into vacancy numbers, recruitment lead times and perhaps a red-amber-green indicator. Those measures describe staffing administration. They do not describe delivery exposure.
A small departure can create a large fracture
Consider a composite example drawn from familiar programme conditions. A 120-person transformation loses eleven people over ten weeks. The headline attrition rate attracts attention, but it does not appear catastrophic. Recruitment begins. Contractors cover several vacancies. The steering pack continues to show most workstreams as adequately resourced.
Among the eleven departures, however, are a release lead, an enterprise data architect, a benefits analyst, a senior operational process owner and the planner who has maintained the integrated schedule since mobilisation.
None owns an entire workstream. Together, they hold much of the programme’s connective tissue.
Within a month, decisions take longer because nobody can quickly explain their history. Two workstreams make individually reasonable design choices that conflict at integration. A supplier revises an estimate that the former release lead would have challenged. The benefits case loses its link to operational measures. The schedule still contains thousands of activities, but confidence in the dependencies between them declines.
The programme has not simply lost eleven units of capacity. It has lost several mechanisms by which capacity became coordinated delivery.
The visible consequence may arrive later as rework, missed releases or a benefits dispute. By then, the original cause will be obscured. The programme will record a design issue, a supplier issue or a planning failure—anything except the capability loss that made those failures more likely.
The reasonable objection: people have always moved
The obvious challenge is that employee turnover is neither new nor necessarily unhealthy. Programmes should not become dependent on individuals. Higher pay, faster recruitment, stronger documentation and sensible succession planning can reduce the disruption. In a flexible labour market, organisations may also gain access to new skills.
All of that is true. It is not sufficient.
The textbook response assumes that capability is modular: document the process, recruit the role and hand over the work. Complex programmes are not modular in that way. Their hardest work happens at boundaries, where formal accountabilities overlap and information is incomplete. Effectiveness there depends on accumulated context and relationships that cannot be captured fully in a handover note.
Nor can salary alone resolve the issue. If people are leaving because sustained overload has become normal, a counter-offer may postpone rather than remove the risk. If the organisation replaces experienced integrators with scarce contractors, it may restore activity while weakening institutional memory. If every critical role is filled by one exhausted expert, a retention bonus merely preserves a single point of failure.
The answer is not to prevent all movement. It is to design the programme so that movement does not remove its ability to think and coordinate.
Map capability, not just roles
Programme leaders should begin with a capability exposure map. This is not another skills inventory. It should identify the human mechanisms required for delivery across workstream boundaries.
For each major outcome, leaders should ask:
– Who can explain the decision history? – Who is trusted across the relevant business and supplier boundaries? – Who can challenge an estimate or design with enough context to be credible? – Who understands the operational consequence of a technical choice? – Where is there only one person who can connect these perspectives? – What would slow down, become less reliable or stop if that person left next week?
This exercise will reveal risks that a resource plan misses. It may show that a fully staffed workstream depends on a single architect shared with four others. It may show that the official process owner has authority but a deputy holds the working relationships. It may show that the programme management office can produce the schedule but only one delivery lead can interpret its weak signals.
Once visible, the exposures can be reduced deliberately.
Critical integration roles should operate in pairs, with both people participating in real decisions rather than one acting as a nominal deputy. Decision records should capture the reasoning, rejected alternatives and conditions under which a choice should be revisited—not merely the final approval. Key supplier and stakeholder relationships should have more than one organisational connection. Benefits logic should be understood jointly by finance, operations and delivery.
Most importantly, leaders should reduce the load that makes critical people want to leave. That may require cancelling low-value reporting, narrowing simultaneous priorities or renegotiating milestones. A programme that responds to attrition by distributing the same work among fewer people converts a talent risk into a further wave of talent risk.
<callout icon=”⚠️” color=”orange_bg”> Retention activity cannot compensate for a delivery model that consumes the people it depends upon. </callout>
Rescope before the capability gap becomes a performance fiction
There is a temptation to protect confidence by maintaining the original plan while recruitment catches up. That is often the most dangerous choice. It encourages teams to report nominal coverage, defer difficult trade-offs and preserve milestones whose underlying assumptions no longer hold.
When critical capability has left, the programme board should decide explicitly which outcomes remain protected, which work will pause, and which risks it is willing to carry. This is not an admission of failure. It is the exercise of judgement under changed conditions.
The board should also distinguish capacity recovery from capability recovery. A new hire may increase available hours immediately while taking months to acquire the context needed for independent decisions. Progress reporting should reflect that ramp-up honestly. Otherwise, the programme will count a filled vacancy as a restored control and discover the difference only at the next integration point.
The leadership question beneath the labour-market story
The prospect of widespread resignation is exposing a deeper weakness in programme management. Many organisations have built delivery systems that appear robust only because a small number of people continually compensate for unclear governance, fragmented suppliers and overloaded teams.
Those people remember what the process forgot. They resolve what the operating model left ambiguous. They absorb the consequences of decisions made elsewhere. Their departure does not create every problem; it stops concealing the problems already present.
Programme leaders should therefore resist treating 2021’s talent movement as a temporary interruption to be managed by HR. It is a test of whether delivery capability has been designed into the programme or borrowed from a few individuals.
The programmes that respond well will not be those that retain everyone. They will be those that know where capability truly resides, spread critical judgement before it becomes a bottleneck, preserve decision memory, and change commitments when the underlying capacity to deliver has changed.
Headcount tells a board how many people remain. Capability tells it whether the programme still knows how to deliver.