Readiness assessment and adoption sequencing
This is the seventh of 8 Migration and Delivery modules. It explains the C220 Part 3 business transformation readiness assessment technique in full, including all readiness factors, the scoring approach, and how readiness findings should reshape the Architecture Roadmap rather than merely annotate it. The module treats readiness as an architecture sequencing input, not a late training exercise. No prior knowledge beyond the preceding modules in this stage is assumed.
By the end of this module you will be able to:
- Explain why readiness assessment is an architecture sequencing input rather than a late training exercise
- List all readiness factors from the C220 Part 3 business transformation readiness assessment technique
- Explain how each readiness factor is scored and what the scoring reveals about adoption risk
- Describe how readiness findings should change work-package order, transition pace, and risk mitigation within the roadmap
- Distinguish genuine readiness assessment from token readiness exercises that do not influence the plan
- Apply readiness logic to London's planning, publication, governance, and resilience changes, identifying the readiness factors most likely to constrain each work package
Real-world case · 2023
Sound architecture. Wrong assumption: every office was equally prepared.
A water utility approved a target architecture that required every regional office to adopt a new asset-management platform within twelve months. The architecture was sound. The readiness assessment was not.
Three regional offices lacked the network capacity to run the new platform reliably. Two had no local technical support for the transition period. One had a workforce that was 60 per cent contract staff with no contractual obligation to attend training. The architecture team had assessed technology readiness but had not assessed governance readiness, information readiness, or business adoption readiness at the regional level.
The architecture team had designed the right target but sequenced the delivery as though every office was equally prepared. The result was a twelve-month programme that took twenty-six months and cost nearly double the original estimate. Readiness is not a training plan bolted on at the end. It is an architecture input that should shape the sequence before the enterprise commits to a path it may not be able to absorb.
If the architecture is sound but the organisation cannot absorb the change at the planned pace, is the roadmap still credible?
That story illustrates what happens when readiness is assessed too late, too narrowly, or without the power to change the plan. This module explains the full C220 Part 3 readiness assessment technique, how readiness should influence the migration sequence, and how to keep readiness work honest rather than decorative.
If you are already confident with readiness assessment, use the knowledge checks to confirm your understanding and move to Module 51: London transformation roadmap and evidence gates.
50.1 Why readiness belongs early in the planning cycle
Readiness is often discussed late, when the roadmap is already emotionally fixed and the programme board has committed to timescales. At that point, readiness findings can either delay the plan (which nobody wants) or be acknowledged and ignored (which everybody pretends is acceptable). Neither outcome is useful.
The C220 Part 3 technique positions readiness assessment as an input to migration planning, not a post-planning validation step. The distinction matters because early readiness findings can change the work-package order, the transition pace, and the risk mitigation approach before the enterprise overcommits. Late readiness findings can only create friction with an already-agreed plan.
Readiness is broader than training. The C220 technique assesses whether the enterprise can absorb the change across multiple dimensions simultaneously. A technology-ready enterprise that is governance-immature will execute change it cannot control. A governance-ready enterprise that is information-unready will govern decisions based on data it cannot trust. Readiness assessment must cover all the dimensions that affect adoption success, not just the most visible one.
“Business transformation readiness assessment evaluates the enterprise's readiness to accept change.”
The TOGAF Standard, 10th Edition - C220 Part 3, ADM Techniques
The key phrase is 'readiness to accept change'. The assessment is not about whether the technology works. It is about whether the organisation can absorb the change at the planned pace across all affected dimensions. The assessment should influence the roadmap, not merely annotate it.
50.2 The C220 readiness factors
C220 Part 3 identifies specific readiness factors that the enterprise should assess before committing to a migration path. Each factor represents a dimension of organisational capacity that can constrain or enable the transformation. The factors are not optional additions. They are the dimensions along which the enterprise may fail to absorb the change even when the architecture itself is correct.
Vision readiness
Does the enterprise have a clear, shared understanding of the transformation purpose? If executives, operational managers, and front-line staff hold different views of what the change is for, the transformation will fragment under delivery pressure. Vision readiness tests whether the Architecture Vision has actually been absorbed by the people who will live with the change, not just by the people who wrote it.
Desire, willingness, and resolve
Do the affected stakeholders want the change to succeed? Desire is not the same as compliance. Compliance means people will do what is required. Desire means people will invest discretionary effort when the plan encounters friction. Readiness without desire produces minimum-viable adoption that erodes under the first serious obstacle.
Need
Is there a genuine operational need for the change, or is the transformation driven by strategic ambition alone? Transformations that address a felt need have stronger adoption because the affected teams can see why the change matters to their own work. Transformations driven purely by executive strategy without an operational pain point are harder to sustain.
Business case
Is the business case compelling and understood by the people who must act on it? A business case that exists only in a board presentation does not influence operational behaviour. The assessment should test whether the people who must change their working practices understand and accept the economic rationale.
Funding
Is the funding sufficient, secured, and structured to survive multi-year delivery? Architecture transformations that depend on annual re-approval are more fragile than those with committed multi-year funding. The assessment should also test whether funding covers the non-technology costs (training, change management, parallel running) that are often underestimated.
Sponsorship and leadership
Is there an executive sponsor with sufficient authority, persistence, and organisational credibility to sustain the transformation through its difficult phases? Sponsorship readiness is not about whether a name appears on a chart. It is about whether that person will defend the transformation when competing priorities threaten its resources or scope.
Governance readiness
Are decision rights, review forums, exception paths, and compliance processes mature enough to support the change? Governance readiness tests whether the Architecture Board, decision log, and exception register described in Stage 7 actually exist and function, not just whether they are planned.
Accountability
Are roles, responsibilities, and accountability structures clear enough that every significant decision and delivery commitment has a named owner? The assessment should test whether accountability is operational (someone will actually be held to account) rather than nominal (someone's name appears on a chart that nobody references).
IT capacity to execute
Does the technology function have the platforms, tools, skills, and capacity to deliver the change at the planned pace? This includes infrastructure readiness, development toolchain maturity, testing capability, and operational support capacity for the transition period.
Enterprise capacity to execute
Can the wider organisation absorb the change alongside its other commitments? This is the factor most often underestimated. An enterprise that is simultaneously running three other transformations may not have the management attention, change fatigue tolerance, or operational slack to absorb another one at the planned pace.
50.3 How readiness factors are scored
C220 Part 3 recommends a structured scoring approach for each readiness factor. The technique assesses two dimensions for each factor.
Readiness rating
How ready is the enterprise in this dimension? The rating typically uses a scale (such as A through E, or 1 through 5) that distinguishes between strong readiness, adequate readiness, partial readiness, weak readiness, and not ready. The rating should be based on evidence, not optimism. Evidence includes documented governance maturity, staffing data, platform performance metrics, and stakeholder survey results.
Urgency of improvement
How urgently does the enterprise need to improve this readiness factor before the transformation can proceed safely? A factor rated as weak readiness with high urgency is a sequencing constraint: the transformation cannot proceed in this area until the readiness improves. A factor rated as weak readiness with low urgency may be acceptable as a managed risk with compensating controls.
How the scoring influences the roadmap
The combination of readiness rating and urgency creates four quadrants that should directly influence the roadmap.
- High readiness, low urgency. Proceed as planned. The factor is not a constraint.
- High readiness, high urgency. Proceed but monitor closely. The factor is currently strong but critical, so degradation would have serious consequences.
- Low readiness, low urgency. Managed risk. Accept the current state with compensating controls and a defined improvement path.
- Low readiness, high urgency. Sequencing constraint. The work package that depends on this factor should be deferred, the transition pace should be slowed, or a dedicated readiness improvement initiative should precede the main transformation.
“The readiness assessment should be used to modify the architecture roadmap and to manage the risk of transformation.”
The TOGAF Standard, 10th Edition - C220 Part 3, Business Transformation Readiness Assessment
The key verb is 'modify'. The assessment is not a report that sits alongside the roadmap. It is an input that should change the roadmap when readiness evidence contradicts the planned sequence. If the assessment cannot change the plan, it is decorative.
50.4 Genuine readiness versus token readiness
Not all readiness exercises are genuine. Token readiness has three recognisable symptoms.
- Assessment after commitment. The readiness assessment is conducted after the roadmap has been approved and the programme has been funded. At this point, the assessment can only delay the plan (which creates political friction) or confirm the plan (which serves no diagnostic purpose). Genuine readiness assessment happens before the sequence is committed.
- No authority to change the plan. The readiness findings are presented to the programme board, but the board has no mechanism to adjust the roadmap based on readiness evidence. The assessment informs but does not influence. Genuine readiness assessment feeds directly into migration planning with the authority to change work-package order, transition pace, or risk mitigation.
- Single-dimension assessment. The readiness exercise evaluates only technology readiness or only training needs, ignoring governance, information, sponsorship, and enterprise capacity. Genuine readiness assessment covers all the C220 factors because any single weak factor can constrain the transformation regardless of strength in other areas.
Common misconception
“Readiness assessment is mainly about training plans.”
Training is one dimension of readiness, but C220 Part 3 identifies at least ten readiness factors including vision, desire, governance, sponsorship, accountability, funding, IT capacity, and enterprise capacity to execute. An enterprise that is training-ready but governance-immature will execute change it cannot control. The assessment must cover all dimensions that affect adoption success.
50.5 London Grid Distribution: readiness across four work packages
The London roadmap cannot assume that planning reform, publication discipline, resilience strengthening, and governance change are all absorbable at the same pace. Each of the four London work packages from Stage 6 has a different readiness profile, and the differences should shape the migration sequence.
Work Package 1: Case spine and evidence model
Strongest readiness factors: Vision (clear regulatory driver), need (Ofgem connections reform creates a felt operational pain), funding (ED3 investment supports this area).
Weakest readiness factors: Information readiness (the existing evidence model has quality gaps that must be closed before the new case spine can operate reliably), accountability (ownership of evidence-quality rules is not yet assigned to named roles).
Work Package 2: Authority and publication controls
Strongest readiness factors: Governance readiness (the Architecture Board structure exists and is functional), business case (LTDS and data publication obligations create a clear rationale).
Weakest readiness factors: IT capacity to execute (the publication pipeline requires integration work that competes with operational maintenance priorities), enterprise capacity (the organisation is simultaneously managing connections reform, ED3 submission preparation, and operational resilience requirements).
Work Package 3: Model and standards pipeline
Strongest readiness factors: Sponsorship (strong engineering leadership support for network modelling improvement), need (current modelling inconsistencies create operational planning risk).
Weakest readiness factors: IT capacity (network modelling platforms require specialist skills that are scarce), desire (some operational teams prefer their existing local modelling practices and are reluctant to adopt a governed pipeline).
Work Package 4: Cross-layer assurance hardening
Strongest readiness factors: Vision (NCSC Cyber Assessment Framework provides a clear external reference), governance readiness (cyber governance structures are relatively mature compared to other governance areas).
Weakest readiness factors: IT capacity (OT/IT boundary work requires specialist knowledge that is concentrated in very few people), enterprise capacity (assurance hardening touches every operational domain and competes for attention with all other work packages simultaneously).
Sequencing implication
The readiness profiles suggest that Work Package 1 (case spine) should start first because its regulatory driver creates urgency and its readiness profile is the strongest. Work Package 4 (assurance hardening) should not run at full pace simultaneously with Work Packages 2 and 3 because enterprise capacity is already constrained. The London roadmap should reflect these readiness realities rather than assuming all four packages can run in parallel.
A readiness assessment is conducted after the roadmap has been finalised and approved. What is the most likely weakness of this approach?
An enterprise rates its technology readiness as high but its governance readiness as low. The roadmap starts with a major technology migration. What is the risk?
C220 Part 3 recommends assessing both a readiness rating and an urgency of improvement for each factor. A factor is rated as low readiness with high urgency. What should happen to the work package that depends on this factor?
Key takeaways
- Readiness assessment is an architecture sequencing input, not a training afterthought. It should happen before the roadmap is committed.
- C220 Part 3 identifies at least ten readiness factors: vision, desire, need, business case, funding, sponsorship, governance, accountability, IT capacity, and enterprise capacity.
- Each factor is scored on readiness rating and urgency of improvement. The combination creates four quadrants that directly influence the roadmap.
- Low readiness with high urgency is a sequencing constraint that should change work-package order, transition pace, or risk mitigation.
- Token readiness exercises happen too late, lack authority to change the plan, or assess only a single dimension. Genuine readiness assessment covers all factors and feeds migration planning directly.
- London's four work packages have different readiness profiles. The roadmap should reflect those differences rather than assuming uniform absorption capacity.
Standards and sources cited in this module
The TOGAF Standard, 10th Edition (C220)
Part 3, ADM Techniques: Business Transformation Readiness Assessment
The core standard defining the readiness assessment technique, all readiness factors, and the scoring approach.
G186, Practitioners' Approach to Developing Enterprise Architecture Following the TOGAF ADM
Full guide
Practical guidance on readiness and adoption planning within the ADM.
G184, Leader's Guide to Establishing and Evolving an EA Capability
Full guide
Leadership guidance on organisational readiness as a component of architecture capability.
G212, Architecture-Led Incremental Planning
Full guide
Incremental planning techniques that depend on readiness findings to sequence work packages.
You now understand readiness as a sequencing input rather than a training afterthought, and you can apply the full C220 readiness technique to the London work packages. The next module brings all of Stage 6 together in the London transformation roadmap with evidence gates. That is Module 51.
Module 50 of 64 · Migration and Delivery