Practice : Change Readiness Assessments
Purpose and Strategic Importance
Change Readiness Assessments enable teams to reduce risk and improve system resilience by ensuring that technical, operational, and organisational factors are considered before major changes such as migrations, infrastructure upgrades, or platform rollouts.
By deliberately pausing to assess readiness, teams prevent disruptions, avoid rushed deployments, and build confidence that systems and teams are prepared for change. Without readiness assessments, changes may introduce instability, degrade performance, or increase incident rates.
Description of the Practice
- Readiness assessments are lightweight, structured reviews conducted before significant technical or organisational changes.
- Assessments cover technical risks, system health, observability, rollback plans, and team preparedness.
- Outcomes determine whether the change proceeds, is paused for further preparation, or requires additional mitigation actions.
- The process is collaborative, involving engineering, operations, product, and platform stakeholders.
How to Practise It (Playbook)
1. Getting Started
- Define criteria for when readiness assessments are required (e.g. high-risk deployments, major architectural changes, platform migrations).
- Create a simple assessment checklist covering technical, operational, and human factors.
- Conduct the assessment early enough to allow for mitigation without delaying delivery unnecessarily.
2. Scaling and Maturing
- Incorporate lessons from incidents and near misses to continuously improve the assessment process.
- Automate checks where possible (e.g. system health, test coverage, observability readiness).
- Align assessments to platform roadmaps, migration plans, and reliability objectives.
- Foster a culture where raising readiness concerns is encouraged, not penalised.
3. Team Behaviours to Encourage
- Treat readiness assessments as an enabler for safe, confident change, not a blocker.
- Collaborate across teams to address gaps before change proceeds.
- View assessments as a learning opportunity to strengthen systems and practices.
- Celebrate successful, low-risk changes as a team achievement.
4. Watch Out For…
- Assessments becoming bureaucratic or overly complex.
- Teams skipping assessments under delivery pressure.
- Readiness criteria that are vague or inconsistently applied.
- Focusing only on technical factors, ignoring human or operational readiness.
5. Signals of Success
- Major changes proceed with minimal disruption or incidents.
- Teams feel confident and prepared when delivering significant technical change.
- Readiness assessments are seen as valuable, not obstructive.
- System reliability and team resilience improve over time through proactive preparation.