The fastest sequence of project deliveries is not necessarily the fastest route to sustainable enterprise value.
Executives have good reasons to push transformation hard. Delay can destroy competitive advantage, extend duplicated operating costs, postpone benefits and weaken confidence. A program that moves too slowly can become an expensive holding pattern.
But the opposite failure is equally real.
Technology can be deployed faster than people can learn it. New processes can arrive before roles and controls are redesigned. Several programs can target the same operational teams in the same quarter. A program can therefore be ahead of schedule and still damage the organisation's ability to perform.
Transformation has a pace. Program leadership has to govern it.
The Strategic Context
The supplied Week 8 material introduces different approaches to program architecture and lifecycle, including linear, incremental, experimental and evolutionary forms. The point is not that one method is universally superior. Different levels of uncertainty, urgency and organisational readiness require different rhythms of change.
The historical BIS guidance uses tranches to divide a program into stages that deliver step changes in capability and associated benefits. Thiry's lifecycle interpretation adds a particularly useful insight: periods of stability can allow the organisation to absorb change at a rhythm consistent with its culture before the next cycle begins.
Harrin's practitioner advice approaches the same issue from the workforce side. Long-running programs cannot operate at maximum intensity indefinitely; leaders need to manage pace, create visible progress and protect teams from burnout.
Taken together, the sources support a broader executive principle: delivery velocity and organisational absorption are separate variables.
Related article: Capacity Is a Strategic Constraint: Match Ambition to What the Organisation Can Absorb
What Leaders Commonly Misread
The first misread is faster is always better. Speed creates value only while the receiving system can absorb the change without excessive disruption, rework or benefit leakage.
The second misread is project capacity equals enterprise capacity. A program may have enough developers, engineers or contractors to deliver the next release while operations lacks trainers, supervisors, data stewards, maintenance people or change capacity to adopt it.
The third misread is tranches are just large milestones. A tranche should create a meaningful decision or capability boundary. If it is merely a date on the schedule, it does not provide the organisation with a chance to learn or absorb.
The fourth misread is quick wins prove the whole strategy. Early visible success can strengthen confidence, but it may be drawn from easier components. Leaders need to distinguish momentum from evidence that the hardest parts of transformation are working.
Reframing the Issue
Transformation pace is a balance among four clocks:
- Strategic urgency: how quickly the external or enterprise need is changing.
- Delivery capability: how quickly the program can produce reliable capability.
- Absorption capacity: how quickly operations and stakeholders can adopt the change.
- Learning speed: how quickly evidence can be collected and converted into better decisions.
The sustainable pace is constrained by the slowest critical clock.
If competitors are moving fast but the organisation's data foundation is weak, rushing the front-end digital experience may create more failure than advantage. If technology is ready but regulation requires staged approval, compliance becomes the pace constraint. If a plant can install new automation rapidly but maintenance and process capability are not ready, operational absorption becomes the constraint.
The program manager's job is not to accept the constraint permanently. It is to identify it, strengthen it and sequence around it.
Strategic Analysis: Four Delivery Rhythms
Linear delivery
A linear approach can fit situations where dependencies are well understood, requirements are comparatively stable and value depends on completing a defined sequence. It offers clarity but can lock the organisation into early assumptions.
Incremental delivery
Incremental programs release usable capability in stages. This can create early benefits, spread change load and provide evidence for later decisions. It is particularly useful where the target state is clear but the organisation should not absorb the whole change at once.
The risk is architectural fragmentation. If each increment is optimised locally, the enterprise can accumulate temporary solutions that become permanent complexity.
Experimental delivery
Where uncertainty is high, small experiments can test customer behaviour, operating assumptions or technology before large commitments. This protects option value and can reduce the cost of being wrong.
The risk is endless experimentation without a path to scale. Governance should define what evidence moves the program from experiment to commitment.
Evolutionary delivery
Some transformations need the target state itself to evolve as the organisation learns. This is appropriate where technology, policy or market conditions remain fluid. It requires strong strategic guardrails because detailed end-state control is weaker.
The risk is drift. The program needs stable outcomes and decision principles even when component design changes.
Decision Framework: The Transformation Pace Test
Before accelerating a program tranche, test five conditions.
1. Benefit urgency
What value is lost by waiting? If delay materially damages market position, compliance, safety or economics, faster movement may justify additional cost and risk.
2. Delivery confidence
Can the program deliver the next capability at the required quality without creating hidden technical or commercial debt?
3. Operational readiness
Are process owners, people, data, training, support, suppliers and controls ready to use the capability?
4. Change collision
What other programs are affecting the same part of the organisation? A tranche that is manageable alone may be unmanageable when combined with two other transformations.
5. Recovery capacity
If the change creates an unexpected problem, does the organisation have enough slack, fallback and leadership attention to respond?
If the answer to several of these is no, acceleration may increase activity while delaying value.
From Strategy to Execution
Immediate action is to add an absorption review to tranche approval. Require the receiving business to demonstrate readiness, not simply sign off that delivery is complete.
Medium-term capability building means creating an enterprise change calendar that shows cumulative impacts on functions, sites, customers and critical roles. Portfolio and program leaders can then see collisions before they emerge as operational overload.
Long-term strategic positioning is to invest in the capabilities that allow the organisation to change faster: modular technology, stronger training systems, reusable data and architecture, flexible workforce capability, better change leadership and more resilient operations. The goal is not to accept a slow absorption rate. It is to raise it deliberately.
Related article: Build Capability Before Strategy Depends on It
Signals to Monitor
Watch for rising overtime, change fatigue, training completion without competence, temporary workarounds, repeated requests to defer adoption, declining operational performance immediately after releases, support queues that remain elevated, and benefits that lag while project completion remains strong.
Another warning sign is a program that continually advances because stopping would look like failure. Sometimes a deliberate stabilisation period is the fastest way to protect the next tranche.
Positive signals include planned periods of operational consolidation, benefits appearing after each capability release, readiness criteria that influence dates, and the ability to accelerate once earlier tranches demonstrate real absorption.
References
- Thiry, M. 2012, 'Understanding the program management lifecycle', Project Manager.
- Department for Business, Innovation and Skills 2010, Guidelines for Managing Programmes, UK Government.
- Harrin, E. 2019, '10 Things Every New Program Manager Should Know', The Balance Careers.
- University of South Australia, MPM9104 Week 8 Program Lifecycle Management and Supporting Activities, supplied teaching material based on PMI 2017 and supplementary sources.
Questions for the Leadership Team
- What currently sets the pace of this transformation: urgency, delivery capability, operations or learning?
- Which business units are being changed by several programs at the same time?
- Are our tranches designed around meaningful capability and benefit steps, or simply reporting periods?
- What evidence tells us operations can absorb the next release?
- Which quick wins are creating genuine strategic learning, and which are mainly creating confidence?
- What capability investment would allow us to transform faster without increasing failure risk?
Closing Perspective
Transformation is not a race between project schedules. It is a controlled movement from one operating state to another. Program leaders create value when they move fast enough to protect strategic urgency but not so fast that the organisation loses the ability to absorb, learn and sustain the change. The right pace is therefore not the slow option. It is the pace at which value can survive delivery.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.