Why agreed plans stall before they reach the floor

Agreed plans carry their risk into delivery. At the end of March 2026, 58% of the 189 projects in the Government Major Projects Portfolio were rated Amber, meaning delivery looked feasible but significant issues needed management attention (NISTA Major Projects Annual Report, 2026). These are the government’s most closely overseen programmes.

In a growing technical business specifically, a similar pattern plays out at a smaller scale. The owner and senior team agree a new scheduling system or a revised quality process, and an operator inherits the job of making it run on Monday morning with the people who already do the work.

This article argues that the implementation gap is a design fault, built in before launch whenever the people who plan a change sit apart from the people who run the work. You will get a five-question scorecard to test your next plan and three actions that close the gap before go-live. More on this theme sits in our change and transformation Insights.

The implementation gap is a design issue

The implementation gap is a design issue because most plans are written in one room and delivered in another. The assumptions travel with them, untested. They surface weeks later, when the floor tries to use the plan on a busy day.

• Designers and doers sit apart. At National Savings & Investments, a December 2024 culture review found that staff saw decision-making as slow and hierarchical, with decision processes they found opaque (Committee of Public Accounts, 2026).
• Decisions run ahead of the problem. The National Audit Office traced a consistent pattern of underperformance in digital change to technology choices made before the business problem was properly understood (NAO, 2021).
• Time and measures run thin. In the ONS management survey, 36% of businesses named too little time to think about or implement changes as their main barrier, and KPIs were the weakest practice at 0.42 out of 1 (ONS, 2024).

In summary, each driver lets a plan stay accurate on paper while it drifts from the work, and Exhibit 1 shows that smaller businesses have the thinnest basics for catching that drift.

Why does the design–delivery gap matter for cost and time?

The gap matters because every untested assumption is paid for later, at a higher price. National Savings & Investments estimated its transformation programme at £3.0 billion in 2024, an increase of £1.3 billion on its 2020 estimate (Committee of Public Accounts, 2026). The National Audit Office found the programme was insufficiently thought through before key decisions were made (NAO, 2025).

Involvement is the lever. A review of 79 quantitative studies, 14 of which measured participation, found that people involved in planning and implementing a change reported higher readiness and acceptance, and that early involvement reduced change-related stress and withdrawal (Oreg, Vakola and Armenakis, 2011). The cost of skipping it lands on the operator, because a fix found during design is an edit to a document, while the same fix after launch means reworking the rota and resetting customer commitments.

What goes wrong when a plan is signed off above the floor?

What goes wrong is that the signals leaders watch stay reassuring while the work itself drifts, because those signals track the decision and say little about its use. A signed-off plan and a positive staff survey both look strong in a board pack. Asked about a culture of good news, the NS&I leadership pointed to higher engagement scores, while the programme still lacked an agreed integrated plan five years after it began (Committee of Public Accounts, 2026).

This article calls the hidden cost translation debt: the distance between how the plan says work will run and how it actually runs, which grows every week it goes unchecked and is repaid later as rework. It stays invisible on a dashboard. It surfaces instead as side spreadsheets, and as teams quietly returning to the old routine whenever a week gets busy, long after the launch report has been filed.

A kitchen drawn without the cook: plans that miss how work moves

Imagine a kitchen designed from a brochure, with the fridge placed across the room from the hob because it photographs well there. Within a week, the first cook is stacking pans by the door to save the walk.

Every measurement on the drawing was accurate. What the drawing missed was the route the cook takes between the hob and the pass, and that route is exactly what the person running the work knows best.

Three actions for operators to carry an agreed plan to the floor

Map the work — walking the process as it runs before the plan is costed

Before a plan is costed, walk the process with the person who does it and draw each step as it happens today. When we map a process this way, we look first for every handoff and workaround the written procedure leaves out, because each one is an assumption the new plan has to absorb. The output is a one-page current-state map that the plan’s author reviews before the budget is agreed.

Name a floor owner — giving one person who runs the work authority to pause

Give one person who does the work every day the authority to pause the rollout when an assumption proves false. A supervisor who can raise a stop on Tuesday saves the month a problem would otherwise spend climbing the hierarchy. The named role also gives middle managers a defined part, which matters because opening strategy work to front-line staff can unsettle their sense of role (Splitter, Jarzabkowski and Seidl, 2023).

Track the first 30 days — measuring whether the new way is used

Set one adoption measure before launch, such as the share of jobs logged in the new system, and review it weekly for 30 days. Launch dates are easy to celebrate. KPIs are the weakest practice in the ONS survey, and a single adoption measure turns translation debt into a number the owner can see and act on.

How ready is your business to carry its next plan to the floor?

Readiness comes down to five checks you can complete in ten minutes, so score each one for your next agreed change and read the band underneath.

Question	0	1	2
Has someone who does the work reviewed the plan’s assumptions before sign-off?	No	Partly	Yes, documented
Is the current process mapped as it actually runs?	No	Partly	Yes, documented
Does one person on the floor have authority to pause the rollout?	No	Partly	Yes, documented
Is time set aside in the rota for the people whose work is changing?	No	Partly	Yes, documented
Will you track an adoption measure weekly for 30 days after launch?	No	Partly	Yes, documented

0–3: Pause the launch date. Walk the process with the person who runs it this week, then rescore. 4–7: Fix your lowest-scoring question before sign-off, because it marks where the plan is most likely to stall. 8–10: Keep the floor owner in place after launch and reuse the 30-day measure on your next change.

What to do next

This method stops working in two places. When a regulator mandates a change with fixed wording, floor review can shape the rollout while the decision itself stays fixed. In a business of fewer than about ten people, the person designing the change usually runs the work too, so the gap is small to begin with.

Everywhere else, the gap closes when you test the plan against the work before sign-off. This week, pick the next agreed change and book 60 minutes to walk its process with the person who runs that work.