Change management and programme delivery
Most organisations don’t fail because the strategy is “wrong”.
They fail because change is not engineered, owned, and delivered with enough discipline to survive competing priorities, real-world constraints, and human behaviour.
Modern programmes
Modern programmes typically involve multiple workstreams, vendors, internal teams, and decision-makers, often across jurisdictions.
Without a structured delivery approach, progress becomes meeting-driven rather than outcome-driven, and the programme starts to drift: scope expands, decisions slow down, accountability blurs, and reporting turns into hindsight.
A useful global marker is how low success rates still are for complex transformations.
McKinsey’s research highlights that digital transformations are particularly difficult, with only 16% of respondents reporting sustained performance improvement and long-term capability building.
Figure 1 (image shown above). Digital transformation success rate (McKinsey Global Survey)
Source reference (full address): https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/unlocking-success-in-digital-transformations
Image file (if you need it): sandbox:/mnt/data/chart_digital_transformation_success_mckinsey_2018.png

Programme delivery as a management system
This is exactly why programme delivery needs to be treated as a management system, not an admin function. In our view, the biggest causes of failure are consistent across sectors.
First, programmes start with activity, not outcomes. Teams begin building, hiring, buying, or implementing before they have defined what “done” means, how success will be measured, and which decisions must be made early to avoid expensive rework later.
Second, ownership is not explicit. Many organisations have “responsibility” spread across a large group, which feels collaborative, but in practice it means no single person has end-to-end accountability for pace, quality, and decisioning. That is when timelines slip and risk becomes normalised.
Third, the human side of change is treated as a comms exercise rather than an adoption plan. That is a measurable mistake. Prosci’s research shows projects with effective change management meet or exceed objectives far more often than projects with poor change management.
Figure 2 (in gallery). Change management effectiveness and meeting objectives (Prosci)
Source reference (full address): https://www.prosci.com/blog/change-management-principles
Image file (if you need it): sandbox:/mnt/data/chart_change_management_effectiveness_prosci.png
Finally, poor delivery discipline is expensive, even when the programme appears “busy”.
PMI’s Pulse of the Profession 2023 reports a global average of 5.2% wasted investment due to poor project performance (with materially worse outcomes where organisations place a low priority on core capability).
Figure 3 (in gallery). Wasted investment due to poor project performance (PMI Pulse of the Profession 2023)
Source reference (full address): https://www.pmi.org/learning/thought-leadership/pulse/pulse-of-the-profession-2023 Image file (if you need it): sandbox:/mnt/data/chart_wasted_investment_pmi_pulse_2023.png

How CGI approaches programme delivery
CGI is built to make complex change feel controlled. We are deliberately small, senior-led, and outcomes-first. That means clients don’t get a “rotating cast” of consultants, long handovers, or a dependency on junior teams producing decks. You tell the story once, we translate it into a structured delivery plan, and we stay accountable through to implementation.
We start by locking down the minimum viable clarity: what is the objective, what has to be true for it to be successful, and what are the critical risks and constraints. Then we define workstreams with owners who have real authority, set milestones that reflect dependencies (not wishful thinking), and establish a cadence that forces decisions to happen at the right time.
A strong programme rhythm is not about more meetings; it is about the right meetings, run properly. The cadence we implement is designed to surface exceptions early, maintain momentum, and protect senior leadership time. Reporting is built to be decision-grade: what changed, what is blocked, what needs a decision, and what the next actions are. This is where many organisations and larger consultancies fall short: they generate volume reporting that looks polished but does not drive faster, better decisions

Typical delivery ouputs
Typical delivery outputs include a practical programme charter, a workstream map, RACI and decision rights, an integrated timeline with dependencies, a RAID log (risks, assumptions, issues, dependencies), and a benefits tracker that links activities to outcomes.
Where appropriate, we also run a decision log so topics are not recycled, and an action log so ownership is visible and follow-through is measurable.
Because we are Dubai-based with cross-border experience, we are comfortable coordinating multi-jurisdiction stakeholders, vendors, and specialist advisers when required.
We do not “replace” existing teams; we complement them, add structure, and improve execution speed. The client takeaway should be simple: clearer ownership, faster decisioning, and a programme that keeps moving without sacrificing control.

Call to action
If you have an initiative that matters and you want it delivered with pace and accountability, book a discovery session.
We will sanity-check the objective, identify the constraints and dependencies, and propose a clear delivery approach with milestones, KPIs, governance cadence, and a practical path from decision to implementation.





