How do we keep focused on purpose? A B2B business approves a transformation to make buying and onboarding easier for customers. Leadership wants fewer delays, less repeated information and clearer responsibility from the first commercial conversation through to a working service.
The programme introduces a new platform, revised processes and staff training. Months later, the implementation is complete. The delivery team can demonstrate that the agreed work has been done.
Customers still repeat information. They still chase updates. Sales, onboarding and service still give different answers about what happens next.
In this illustrative example, the organisation has delivered much of what it commissioned. Somewhere between the original decision and the completed work, it lost the conditions needed to achieve the intended improvement.
This is how a transformation can retain its authority after its original meaning has dropped out of the work. The programme continues to command resources and attention, while its purpose becomes harder to recognise in the decisions being made.
Purpose has to survive translation
Leadership intent cannot remain a broad statement. People need budgets, requirements, responsibilities and a workable plan.
The difficulty lies in translating the purpose without reducing it to a list of outputs.
Making buying easier may become a website workstream. Reducing customer effort may become a systems integration. Improving accountability may become a governance structure. Helping employees work differently may become a training schedule.
Each could be necessary. Completing them does not establish that buying has become easier, customer effort has fallen or responsibility has become clearer.
For our onboarding business, the platform should support a change in how information and responsibility move between teams. If the work is defined only as implementing the platform, an essential part of the transformation can disappear from the brief.
The connection between each deliverable and its intended effect needs to remain visible as the work develops.
Reasonable local decisions can weaken the whole
Purpose is not always lost through carelessness or resistance. It can be diluted through decisions that make sense within individual responsibilities.
Finance protects the approved budget. Procurement needs a scope suppliers can price and contracts can measure. Technology must address architecture, integration and security. Operations needs continuity. Suppliers must deliver the requirements they have accepted.
Those responsibilities are legitimate. The problem arises when nobody examines their combined effect on the intended outcome.
Suppose simpler onboarding requires one team to take responsibility for keeping the customer informed throughout the process. That change raises questions about capacity and authority, so it is deferred. The platform proceeds using the existing departmental boundaries.
The programme can now automate notifications and transfer records, but customers still have to discover which team owns their problem. Some information moves faster while the underlying uncertainty remains.
The business has made a technical improvement. It has not yet resolved the organisational condition preventing easier onboarding.
Delivery pressure changes what gets protected
As deadlines approach, a programme will encounter choices about scope, cost and timing. Adapting the plan is often necessary.
The leadership test is whether those choices preserve a credible route to the outcome.
A contracted technical milestone may be difficult to move. Customer testing, process redesign or support for new working practices may appear easier to defer. Their value can also be harder to demonstrate before the benefits emerge.
Yet these activities may determine whether the investment works in practice.
In the onboarding example, teams might retain separate approval steps to protect the launch date. Employees receive training on the new screens, but little opportunity to rehearse exceptions or resolve ambiguous handovers. The system goes live while important decisions about the service remain unsettled.
A phased approach could still be sensible. Leadership needs to acknowledge what the first phase can achieve, what remains necessary and who owns completing it.
A material reduction in the expected outcome should prompt an explicit decision. The original promise should not remain attached to work that can no longer deliver it.
Customers experience the workstreams together
Customers do not experience a successful technology workstream separately from an unresolved operational handover. They experience how the business works as a whole.
They want to know whether the offer is clear, whether the promises hold and whether somebody can help when the process stalls.
Customer Spectacles provides a practical test throughout delivery: what is becoming meaningfully better for the customer, and how do we know?
For onboarding, that might mean fewer requests for information already supplied, clearer expectations and less time spent seeking an update. Testing should include difficult cases as well as the straightforward journey shown in a demonstration.
Employee experience matters too. If staff still depend on spreadsheets, personal contacts or repeated escalation to make the process work, the programme needs to understand why. Those workarounds can reveal missing capabilities, unclear responsibilities or requirements that never reached the delivery plan.
This evidence should influence decisions while there is still time to change the work.
Someone must retain ownership of the outcome and purpose
A transformation needs more than an author for its original business case. It needs continuing accountability for what the organisation expects to change.
The sponsor should retain ownership of the business outcome and the decisions needed to protect it. Programme leadership should expose dependencies, explain trade-offs and identify where the current scope no longer supports that outcome.
Workstream owners need enough context to understand how their local decisions affect the wider result. This does not require constant reference to a strategy presentation. It requires clear answers to practical questions: what must improve, for whom, and which conditions are essential?
Teams also need to know when a decision exceeds their authority because it threatens the intended benefit.
Without that clarity, escalation can focus on budget and deadlines while changes to the purpose pass unnoticed. Leadership hears that the programme remains on track without understanding how far the expected result has moved.
Five questions before the next programme review
At a significant review point, leaders can ask:
- What was this transformation approved to change? Describe the intended difference in business, customer or employee terms.
- Can we trace that change into the current work? Identify the deliverables and organisational conditions required to produce it.
- Which decisions have weakened the expected outcome? Examine accumulated compromises alongside formal scope changes.
- What are customers or employees experiencing so far? Look for evidence of improvement, continuing friction and new problems.
- Should we continue, adapt or reconsider the commitment? Make a decision based on what the work can now credibly achieve.
The discussion should produce decisions, owners and an agreed next move. Repeating the purpose at every meeting without changing how the programme is governed would add another reporting ritual.
Recover the connection to purpose before adding more activity
A transformation that has lost direction may need a focused reset. Restate the intended outcome, compare it with the current work and identify the conditions that are missing.
For our onboarding business, that could mean resolving ownership, removing unnecessary approval steps and testing the revised journey with customers before commissioning further functionality.
The next move should address what is preventing the outcome. More development, training or governance only helps where it responds to that evidence.
Oak Consult’s Product & Transformation Leadership support and Oak CORE help leaders reconnect strategic intent, operational reality and practical delivery.
Transformation theatre emerges when the programme’s status carries more weight than its continuing contribution. Leadership must be willing to examine that contribution, even when substantial work has already been completed.
The programme’s authority should depend on its continuing ability to deliver the purpose for which it was approved.