A technically ready system can still be an operationally unready service.
Testing may be complete and infrastructure available, yet the business may lack the people, processes or support arrangements needed to operate confidently after migration.
In my experience, readiness needs to bring three perspectives together:
• Technical: Have applications, data, interfaces, access and infrastructure been validated, with monitoring and contingency arrangements in place?
• Business: Can users complete critical activities? Are process changes understood, validation owners available and the timing workable for the business?
• Operational: Can support teams take ownership? Are responsibilities, support routes, documentation and escalation arrangements understood?
On a retail cloud migration programme, I worked with stakeholders to sequence application moves by business unit, considering complexity and overall readiness across technical, business and operational teams. That shared view was essential to agreeing an achievable migration sequence.
A useful readiness review asks five questions:
- What must be true before we proceed?
- What evidence demonstrates it?
- Who owns the assessment and acceptance?
- What gaps remain, and what is their operational impact?
- Who has authority to accept the residual risk?
Define these criteria early enough to act on the answers. At the go/no-go review, make outstanding gaps, contingency options and risk acceptance explicit.
The aim is a decision supported by evidence, with the people who will run and use the service ready to take responsibility.
