Transformation programmes are frequently planned with the same certainty as conventional projects, despite operating under very different conditions. When the future state is forced into early definition rather than allowed to emerge through delivery, momentum and stakeholder confidence are usually the first casualties.
Key Insights:
- The problem in a transformation is usually clear well before the solution is. Forcing early certainty on both ends up relitigating decisions instead of delivering.
- Momentum loss midway through a transformation is rarely a delivery symptom, but often the result of treating it as one large executable solution instead of a sequence of learning and delivery cycles.
- Sponsors need to hold the team to outcomes and original intent, not a fixed scope.
Most projects start with the scope defined and the approach documented, built on assumptions that are expected to carry through to delivery. Delivery becomes a matter of executing against the plan and testing those assumptions as the work progresses.
Transformation programmes are different due to their scope and complexity, because they involve changing how an organisation operates – whether that be through new business models, new capabilities, new ways of working or fundamentally different customer experiences.
In these environments, the problem may be clear but the solution often isn’t. An organisation might know it needs to improve customer experience, modernise operations, reduce costs or respond to changing market conditions. What remains uncertain is exactly how that future state will take shape.
This distinction changes the nature of delivery, though not every project sits neatly on one side of it. Some projects can be executed largely as planned, with limited need to revisit the solution once work begins. Others, particularly large-scale transformations, require organisations to discover solutions as they move through delivery, learning from new capabilities, operational realities and feedback along the way.
Many organisations run into difficulty because they approach transformation as though it were simply a larger version of a conventional project. They attempt to define the future state in detail upfront, then execute towards it.
The reality is that transformation rarely works like that.
Why transformation moves through transition states, not a single leap
One of the most common misconceptions about transformation is the idea that the future state can be fully designed before delivery begins.
Transformation is rarely a single, fluid movement from current state to future state; instead, it usually unfolds through a sequence of transition states that gradually build new capabilities, expose new opportunities and generate new information. Assumptions should be – and need to be – tested continually along the way.
For example, the first phase of a transformation programme may involve implementing a new platform, introducing new capabilities or creating the foundations required for future change. While these activities can appear incremental, they create the conditions that allow more substantial change to occur.
This is where transformation differs from conventional delivery. As new capabilities are introduced, organisations begin learning. Some assumptions prove correct, while others don’t. Opportunities almost always emerge that weren’t visible at the outset. And perhaps most importantly, priorities will change as the operational realities become clearer.
In many cases, these discoveries extend well beyond technology. Organisations often find themselves revisiting decision-making structures, workflows, accountability and ways of working as they move through the transformation as operating implications are often more significant than the technology itself.
The most successful transformation programmes we’ve worked on evolve through these learning cycles. Each transition state creates the conditions for the next. That doesn’t mean abandoning planning or discipline, but it does ask leaders to recognise that the future state becomes clearer through delivery, not solely through early design.
Loss of momentum as a symptom of certainty
Challenges almost always arise when organisations attempt to define the entire future state of the programme before delivery begins.
This is understandable to a point, because leaders and external stakeholders want a degree of certainty before committing to and investing in large programmes of work. Governance processes are designed to reduce risk and create confidence that investment decisions are well understood.
Unfortunately, transformation programme leaders can very rarely provide the level of certainty that traditional delivery models expect. When organisations attempt to fully articulate the future state upfront, programmes can become trapped in design rather than delivery. Requirements continue to change and scope creep may occur as stakeholders try to account for every possible scenario. Decisions thought to be settled are revisited as new perspectives emerge, and scope becomes increasingly detailed as teams try to remove uncertainty before moving forward. Each of these responses is reasonable in isolation, but together they push the programme further from delivery rather than closer to it.
In transformational environments, many questions can only be answered once new capabilities are introduced, and the organisation begins learning from them. Trying to solve those questions too early can create a perpetual design loop where activity remains high, but progress becomes difficult to see.
Teams spend more time refining possibilities than testing realities, and months can easily pass without anything meaningful entering production. As momentum slows, stakeholder confidence gradually slips away.
What appears to be mid-programme loss of momentum is often the consequence of a much earlier error: the programme itself was framed as a large executable solution, rather than a series of learning and delivery cycles.
The loss of momentum is the symptom. The underlying issue that needs to be addressed is that the transformation was expected to deliver certainty before the organisation had generated enough information to achieve it.
Anchoring the programme while the solution evolves
Leaders of successful transformation programmes don’t set out to eliminate uncertainty; rather, they create mechanisms that allow the organisation to move through uncertainty without losing alignment on the benefits and outcome. This requires a different form of leadership than many traditional projects.
In a conventional delivery environment, sponsors often provide oversight against an agreed scope, schedule and business case. In transformation programmes, the role must be broader. Sponsors help maintain alignment around the problem being solved and the outcomes the organisation is trying to achieve, even as the solution itself continues to evolve.
This becomes increasingly important as new capabilities are introduced and stakeholder expectations begin to change over time. Teams are likely to discover opportunities that weren’t anticipated, and operational realities may challenge earlier assumptions. Stakeholders will naturally begin advocating for changes that reflect their own priorities and preferences.
Without a clear point of reference, programmes can become trapped in continual relitigation. On the other hand, strong transformation programmes establish guiding principles early and use them throughout delivery. These principles provide a consistent reference point for decision-making when complexity increases and competing priorities emerge.
Rather than debating every issue from first principles, delivery teams can return to the original intent of the transformation and assess whether decisions support the outcomes the organisation is trying to achieve. This allows programmes to remain flexible about how the solution develops, while maintaining discipline around why the transformation exists in the first place.
Leadership visibility is critical for realising transformation value
Leaders of transformation programmes that are set up for success recognise uncertainty as a delivery condition, rather than a delivery failure. They understand that their role is to create enough strategic visibility, governance discipline and organisational alignment to keep moving through uncertainty without losing sight of the outcome being pursued.
Organisations that can do this are often better positioned to sustain transformation momentum and realise the full value of transformation over time.
Quay Consulting is a professional services business specialising in the project landscape, transforming strategy into fit-for-purpose delivery. Meet our team or reach out to have a discussion today.