Where delivery actually comes apart
A programme in trouble usually looks fine on paper for a long time first. The status report and the real position separate slowly, and the separation is not visible to anyone reading the report. By the time a steering committee is told, the options that remain are the expensive ones.
My work is to hold structure, governance and pace in place from the first week. In practice that means an honest baseline taken before anyone commits to a date, decision rights written down while they are still uncontroversial, and reporting an executive can act on this month.
Wrenwell leads programmes end to end, stands up PMO capability where there is none, and takes over delivery that has drifted. Benefits sit inside delivery rather than arrive afterwards as a measurement exercise, because a benefit nobody owns during execution is a benefit nobody achieves.
Delivery leadership
- Programme & Project Delivery — End-to-end ownership across technical, operational and business change. Wrenwell chairs the governance and makes the calls that keep work moving, which means most decisions never travel upwards at all.
- Delivery Recovery — An independent baseline of scope, spend, schedule and risk comes first, before anyone agrees what can be salvaged. Plans get rebuilt around what the evidence supports. It’s the least comfortable engagement on this list, because the baseline often contradicts something already reported to a board.
- Benefits Realisation — Benefits defined in operational terms, owned by named people, and tracked through the delivery cadence, so that a programme drifting from its rationale shows up early enough to correct.
PMO & Governance
- Fractional & Embedded PMO Leadership — Wrenwell runs the function, lifts the standard of what it produces, and develops the people already in it. The test is whether the PMO still produces decision-grade information three months after the engagement ends.
- Governance Design & Operation — Decision rights, escalation paths, reporting cadence and controls, designed for daily use. The governance is operated here first and handed over once it demonstrably works.
- Portfolio Risk Partnering — Delivery risk managed where interdependencies and resource contention actually bite, which is at portfolio level and almost never at project level. Issues get raised while they are still cheap to fix.
How an engagement runs
- Baseline — Two to three weeks establishing what is actually true about scope, spend, schedule and risk, independent of whatever has been circulating.
- Reset — A plan the organisation can commit to, with decision rights, cadence and controls settled before execution restarts.
- Execute — Delivery run to that plan, with the governance actually in use, and reporting that holds up when it is tested.
- Transfer — Capability, documentation and governance handed over. What finished looks like for this step is agreed at the outset, because otherwise it never arrives.