Start with the business decision, not the programme label.
A platform replacement may improve resilience, integration and the ability to make changes. Those are important benefits. They do not, by themselves, mean customers receive a better service or teams make better decisions.
The leadership task is to connect the investment with an operating outcome: what should become easier, faster or more reliable; whose work changes; and who will be accountable for that change. This matters whether the programme is called technology modernisation, digital transformation or something else.
An illustrative example: replacing a customer system.
Consider a business replacing an ageing customer-management system. The technical programme can migrate records and launch the new platform successfully while customer response times remain unchanged.
If teams still re-enter information, wait for the same approvals and pass unresolved requests between departments, the operating constraint remains. The decision is not only which system to buy. It is which handoffs, authority and working practices must change alongside it. This is an illustrative scenario, not a HarleyShift client case.
Make four things visible before committing.
A short decision brief can expose gaps that a large programme plan obscures.
- Foundation: which reliability, data or integration constraint must be addressed?
- Outcome: which customer or operating result should change, and what is the current baseline?
- Ownership: who can change the process, roles and decisions around the technology?
- Sequence: what can be tested now, what depends on the platform, and what should wait?
A reset should produce decisions, not just another status report.
For an active programme, compare the original value case with the work actually under way. Identify the assumptions that changed, the unresolved sponsor decisions and the capacity needed for adoption.
The useful output is a smaller, defensible set of priorities with owners and decision dates. Some work may continue, some may be resequenced and some may no longer justify further effort. Implementation and the change in business results then need to be measured separately.
If the technology plan is clear but the operating outcome is not, that is a useful place to begin a focused transformation review.