A new platform launches, the project team disbands and attention moves elsewhere. Over time, reviews slip, workarounds return, publishing slows and measures flatten. Nobody reverses the transformation in a single decision. The new standard simply loses its owners and its capacity to improve.
The missing element is usually sustainability design. A programme can deliver useful change without establishing how the service will be owned, measured and adapted after project governance ends.
Continuous improvement does not mean keeping an organisation in permanent transformation mode. It means creating a manageable operating rhythm that detects drift, makes small decisions and connects them to longer-term direction.
Define the service after the project
Before closing delivery, identify the enduring service and the people accountable for it. The handover should state:
- service outcome and users;
- product or service owner;
- operational, content, data and technical responsibilities;
- support, incident and escalation routes;
- supplier and licence commitments;
- quality, security, accessibility and records controls;
- measures, baselines and review frequency;
- improvement capacity and funding route;
- known debt, assumptions and deferred work.
Training is part of transition, not proof that capability will persist. Confirm that authorised colleagues can perform essential tasks, recover from common problems and access current documentation. Remove temporary project dependencies or make their continuation explicit.
Agree when the steering committee dissolves and which forum receives ownership. A permanent project meeting can obscure the fact that nobody in normal operations has accepted the service.
Review outcomes and drift together
A quarterly review can work well for many established services, but cadence should follow how quickly a material issue can develop. A high-volume or regulated service may need operational monitoring far more frequently and a strategic review less often.
The review should answer four questions:
- What has changed in users, the market, the organisation or the technology?
- What outcome or standard improved, held or deteriorated?
- Which single decision or small set of decisions matters now?
- What longer-term option or dependency must be prepared next?
Keep operational incidents and routine reporting in the appropriate working forum. Senior review time should focus on interpretation, priorities and trade-offs.
Use a short evidence pack rather than a celebratory dashboard. Include outcome measures, guardrails, qualitative evidence, known data limitations, unresolved commitments and capacity. A favourable metric can coexist with an accessibility issue or a support burden; both belong in the decision.
Make drift observable
Choose measures connected to why the investment was made. These might include qualified demand, completion of an important client task, time to publish, adoption, service failure, manual work, cost or satisfaction. Define the denominator, source, owner and expected decision use.
Avoid attributing a commercial movement to one digital change without evidence. Compare against baseline, segment where useful and examine external or operational explanations. Combine quantitative signals with interviews, support themes and observation.
Drift also appears in behaviour before headline outcomes change. Watch for increasing exceptions, manual overrides, delayed content, declining data quality, ageing defects, supplier dependency or reduced participation. Treat these as diagnostic signals rather than automatic proof of failure.
Make successful operation visible as well. Recognition is not decoration; it helps colleagues understand which behaviours and standards should continue. Be specific about the contribution and evidence rather than presenting routine work as a triumph.
Protect capacity for improvement
Every service needs some route for maintenance, risk reduction and evidence-led improvement. Closing the budget entirely can force small issues to accumulate until another large programme appears necessary.
Capacity may be a dedicated product team, a shared portfolio allocation or a planned supplier arrangement. Whatever the model, make demand and trade-offs visible. Separate:
- mandatory operation and remediation;
- small improvements with established value;
- discovery needed to test a larger opportunity;
- strategic change requiring a new investment decision.
Do not begin unlimited initiatives because a review surfaced many ideas. Limit work in progress and finish or consciously stop existing commitments before adding more. Focus beats a long roadmap whose items rarely receive enough attention.
A prioritisation rule should still allow urgent duties and incidents to interrupt. Define who can make that exception and what other work will move.
Connect Now and Next with WHNN®
Distinction’s WHNN® framework asks about the What and How for the Now and Next. In a recurring review, it can prevent tactical fixes from becoming disconnected activity.
“Now” identifies the outcome, decision and capacity that deserve attention in the present period. “Next” preserves direction by making later options, prerequisites and evidence visible. Results from Now may enable, reshape or stop Next.
This separation matters because a transformation roadmap often creates false certainty. Market conditions, client behaviour and internal readiness will change. Direction can remain coherent while individual investments are made at the point where evidence supports them.
The companion article on WHNN explains the framework in more depth. Use it as a decision aid rather than a label that replaces reasoning.
Treat workarounds as evidence
When colleagues return to an old spreadsheet or parallel process, avoid assuming resistance. The workaround may be faster, may meet an edge case the design missed or may reflect insufficient training. It can also create genuine control and data problems.
Observe the task, identify the need and compare the consequence. Then improve the service, adjust guidance, accept the exception with controls or remove the workaround. Repeating “use the new system” without addressing its cause drives the behaviour out of sight.
The same principle applies to poor adoption. Examine relevance, role design, workload, incentives, accessibility, confidence and support before launching another communication campaign.
Revisit the business case without rewriting history
The original investment case provides a baseline, not an eternal promise. Review which assumptions held, which benefits appeared, which costs changed and what unintended effects emerged.
Do not preserve an initiative merely because it was once strategic. If the outcome no longer matters or evidence repeatedly fails, stop or redirect it. Equally, do not judge a long-term outcome before enough time or adoption exists to observe it. Record the basis for the decision.
Avoid illustrative compounding calculations that assume every quarterly improvement produces the same percentage lift. Improvement is rarely smooth and gains can interact. Build forecasts from local evidence, use ranges and include the operating cost required to sustain them.
Start before the project team leaves
Schedule the first service review as part of launch and name the owner. Establish the baseline, initial guardrails, open risks and improvement capacity. Decide what evidence the review must have and who can act on it.
The one-page quarterly transformation review template available below structures change in context, drift, current decisions and next options around WHNN®. Adapt the cadence and measures to the service rather than treating the template as governance by itself.
Transformation becomes a habit when the organisation can notice, decide and improve after the launch story has ended. The goal is a service that remains useful and changeable, supported by ordinary ownership rather than periodic rescue.
