Project Management

Please login or join to subscribe to this thread

Reducing Delivery Risk by 40%

linkedin twitter facebook   Risk Management   Stakeholder Management  
avatar
Tim Williams Senior Project Manager/PMO Manager| Tim Williams consulting Ltd Halesowen, United Kingdom

A recent programme I led had a familiar challenge:
High delivery risk, unclear ownership, and slipping milestones.

Here’s how we turned it around:

Situation:
 A multi‑team transformation with fragmented governance and inconsistent reporting.

Action:


• Re‑established a single source of truth


• Introduced weekly risk surfacing


• Reset stakeholder expectations


• Tightened RAID discipline


• Re‑aligned delivery teams around a shared roadmap

Outcome:
 Delivery risk reduced by 40% within 8 weeks — and confidence restored across the programme.

Lesson:
 Most delivery problems aren’t technical.
 They’re alignment problems.

#ProgrammeManagement #RiskManagement #DeliveryLeadership #Transformation
Sort By:
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Excellent example of a principle that is often overlooked in complex programmes: risk rarely emerges in isolation.

When multiple teams begin operating with different assumptions, different priorities, and different interpretations of reality, delivery risk becomes almost inevitable.
In that sense, fragmented governance is not simply a reporting problem. It is a coherence problem.

What I find particularly interesting is that most of the actions you described were not focused on accelerating delivery directly.
They were focused on restoring shared understanding across the programme.

Perhaps that is why confidence improved alongside risk reduction.
When people operate from a common view of priorities, risks, ownership, and direction, better decisions tend to follow naturally.

This case is a useful reminder that alignment is not a soft concept.
In complex delivery environments, alignment is often a leading indicator of execution capability.
avatar
Imran Afzal Author| The Strategic PMO Cary, NC, United States
Interesting case study, but the outcome raises a question for me.

How did you determine delivery risk was reduced by 40%?

As someone who has spent a significant amount of time building executive dashboards, portfolio intelligence systems, operating reviews, and PMO metrics, I've found that risk itself is difficult to measure directly. What we typically measure are proxies.

Was the reduction based on:

  • Number of open risks?
  • Aggregate risk exposure?
  • Probability and impact scores?
  • Schedule confidence?
  • Milestone predictability?
  • Escalation volume?
  • Stakeholder confidence?
The distinction matters because those indicators do not always move together.

For example, open risks may decrease because teams stop reporting them. Escalations may decline because leaders become disengaged. Schedule confidence may improve because estimates become more conservative. Stakeholder confidence may rise even while underlying technical risks remain unchanged.

That's why I've always found risk measurement to be one of the most challenging aspects of delivery governance. We often assume risk is improving because a particular indicator improves, when in reality we may only be observing a change in perception or reporting behavior.

The actions you described—establishing a single source of truth, surfacing risks more frequently, clarifying ownership, and aligning teams around a common roadmap—are all valuable. However, what interests me most is how those actions translated into a measurable reduction in risk and which indicators gave you confidence that delivery health was genuinely improving.

I'd be interested in hearing more about the measurement approach behind the 40% figure.
avatar
Lissette Indhira Pimentel Sosa
Community Champion
Program Manager| HARPER SRL Santo Domingo / Distrito Nacional, Dominican Republic
I've seen similar situations where the biggest improvements came from clarifying ownership, dependencies, and decision-making rather than implementing new tools or processes.
When teams have a shared understanding of priorities and risks, delivery tends to become much more predictable.

Please login or join to reply

Content ID:

"One of the symptoms of approaching nervous breakdown is the belief that one's work is terribly important."

- Bertrand Russell

Sponsors

Newsletters

Oct 28: Leadership Isn't a Popularity Contest
Oct 21: Leadership Takes Courage
Oct 7: The Skill That Refuses to Be Automated

See all newsletters