top of page

When an Initiative Stalls, Who Owns the Recovery?

Nov 14
4 min read
Duane L. Nicholson, Fractional Executive & Strategic Advisor, beside the headline Who owns the recovery? The Project Sponsor.

The Project Sponsor owns the recovery.


The project manager or designated recovery leader leads the effort. The sponsor remains accountable for confirming priorities, authorizing changes, securing resources, and resolving decisions beyond the project manager’s authority.


When delivery dates keep moving, the sponsor needs a credible answer to three questions: what can still be delivered, what must change, and who can lead the effort?


Stalled project recovery starts by establishing the facts and making the decisions those facts require.


Understand why the delays keep repeating


Before resetting the delivery date, conduct a retrospective with the people who understand the work.


Where did delivery diverge from previous commitments? Which assumptions proved unreliable? What prevented completion? Which decisions remained unresolved?


Look at the signals as carefully as the delivery itself.


When did someone recognize the problem? When was it communicated? When did its significance reach someone authorized to act?


In my experience, many issues had already been discussed somewhere in the organization. Their consequences never reached leadership with enough clarity or urgency to prompt intervention.


The sponsor should expect the retrospective to explain what will change before accepting another commitment.


Decide what can realistically be delivered


Bring together the participants who understand product priorities, technical constraints, dependencies, and available capacity.


Determine what can get done, what will not get done, and why.


During an enterprise modernization effort, I brought key participants together to determine which products could realistically be migrated within the available constraints. That established a focused effort people could have confidence in. It also forced us to determine how we would address the products outside that commitment.


Start with a simple MoSCoW analysis: what must be delivered, what should be delivered, what could be delivered, and what will remain outside the current commitment.


Put the options before the sponsor. A smaller release may protect the date. Additional investment may preserve more scope. Deferring part of the work may create operational consequences that require separate action.


The sponsor owns those tradeoffs. Deferred work still needs an owner and a decision about its future.


Put execution discipline to work


For smaller organizations, I would establish FranklinCovey’s Four Disciplines of Execution: focus on the critical outcome, identify actions that influence it, make progress visible, and establish regular accountability.


Enterprise organizations should put their established project management practices and PMP certified professionals to work.


In my experience, monitoring and controlling is where discipline too often slips. Plans exist, meetings happen, and reports circulate. Yet changing conditions do not consistently lead to timely intervention.


The sponsor should expect project management to connect evidence with corrective action, escalation, and decisions throughout execution.


Establish early recovery checkpoints


Completion rate is one of my starting measures: the proportion of committed items completed and accepted during each delivery cadence.


Begin simply, then develop a more granular understanding of the significance of each incremental delivery.


Across a quarterly commitment, the completion trend provides an early signal of whether the target remains credible. A burn up chart shows cumulative accepted work against the total scope, making that trajectory visible.


Establish checkpoints early enough to intervene. An Amber signal should mean the commitment is at risk, a recovery plan is underway, and there is a defined checkpoint for assessing whether it works.


The sponsor needs to know when recovery remains credible and when the evidence requires a change in scope, timing, or expectations.


Own dependencies after planning


Big Room Planning, often called PI Planning, brings people together to establish direction and commitments. Those commitments require coordination throughout execution.


I have worked in organizations where the Release Train Engineer, or RTE, facilitated the planning event and then returned to another primary job. Dependency coordination lacked sustained attention.


Where an RTE exists, that follow through should be an explicit responsibility supported by sufficient capacity and authority.


The sponsor should know who owns dependency coordination and which unresolved dependencies require executive intervention.


Give every risk a time horizon


One persistent problem I encounter is a misunderstanding of risk itself.


A risk concerns an uncertain future event. Once that event occurs, we are managing an issue and its consequences.


Even when people identify a risk, they frequently omit when it could affect delivery. Without that time horizon, the sense of urgency is poorly established.


When is the dependency needed? When could its absence affect the commitment? By what date must someone intervene?


Develop a scored risk log with accountable owners, anticipated impact dates, response actions, and escalation requirements.


The sponsor needs visibility while there is still time to act. Recording the risk is only the beginning.


Conduct a weekly impact session


I call this an impact session because a weekly status meeting has little value if it leaves the course of delivery unchanged.


Review what changed, what it means for the commitment, and what action is required. Examine approaching risk dates, unresolved dependencies, delivery confidence, and decisions awaiting leadership.


Participants should leave knowing what they own and when they must act. The sponsor should leave having resolved the decisions that require their authority.


I have seen a project update of three to five sentences consume five hours of combined effort, with three people refining the wording. That is a practical opportunity to test AI assisted preparation against a measured baseline, explored further in Where Can AI Give Delivery Leaders Time Back This Week?.


Establish the conditions for recovery


Start by baselining the Iron Triangle: scope, schedule, and cost. Establish the current position, the remaining commitment, and which constraints can change.


Determine whether you have someone who can lead the recovery. Assess their capacity, authority, and ability to bring people together and carry difficult decisions through execution.


Establish how quickly recovery is required. That urgency should shape the intervention and the timing of any leadership change.


If replacement is necessary, personality counts. Experience and credentials matter. So does the ability to rebuild trust, navigate conflict, challenge assumptions, and work effectively with the sponsor and delivery teams.


Plan the handover from the beginning so ownership, decision history, and remaining commitments transfer to the people sustaining delivery.


Through Fractional Executive & Strategic Advisory, or FESA, I help organizations establish that focus and sustain the executive involvement recovery requires.



About the author


Duane L. Nicholson is Founder and Chief Transformation Officer of NBD Consulting Services and a Fractional Executive & Strategic Advisor. He works with technology, product, and delivery leaders on modernization, operating model change, and strategic execution. His experience includes DTCC, Experian, Amgen, Toyota Financial Services, and Pacific Life. He is a SAFe Practice Consultant (SPC).


Comments


bottom of page