Establish the baseline
Use the directional diagnostic with the people accountable for the workflow. Record disagreements instead of averaging them away.
Implementation Guide
Turn your current maturity phase into one accountable 30-day move.
Start with the weakest foundation, improve one consequential workflow, and require operating evidence before moving to the next phase.
This is a starting sequence, not a promise that every organization will follow the same calendar. The diagnostic is directional and the weakest foundation limits the next safe move.
One Action Sequence
Use the result. Choose a workflow. Build proof.
The sequence keeps the maturity model, implementation work, and diagnostic in distinct roles: the diagnostic supplies direction, maturity locates the constraint, and implementation changes a real workflow.
1 2 Confirm the current maturity phase
Compare the weakest foundation with the five canonical phases. Start at the earliest phase whose operating conditions are not yet reliable.
3 Choose one consequential workflow
Select a real workflow with a visible outcome, named participants, and a decision that regularly stalls, reverses, or creates risk.
4 Build the missing operating proof
Complete the action for the current phase. Do not start a broad transformation program or advance automation while the proof is absent.
5 Review after 30 days
Inspect the decisions, exceptions, and evidence created by the workflow. Keep, revise, or stop the change before choosing the next phase.
Interactive Implementation Roadmap
Four rings. Twelve stations. Three gates before AI scales.
Once the immediate action path is clear, use this deeper map to see how implementation expands from the CRI baseline. Select the center, any station, or a checkpoint to inspect the work and the proof required to move forward.
OwnStructureGovernAutomate
Leaders Model the System
Select the heartwood, a station, or a checkpoint to see what leaders must prove before the next ring opens.
Maturity Phase 1: Decision Clarity
Own
Leadership commits, ownership is named, and decision rights become explicit before the operating model is redesigned.
Maturity Phase 2: Communication Discipline
Structure
Communication, information, and platforms are structured so people and machines can operate from the same substrate.
Maturity Phase 3: Governance Embedding
Govern
Controls move into workflows, confidence gates are owned, and agent deployment is prepared before automation scales.
Maturity Phases 4 and 5: AI Amplification and Human-Machine Orchestration
Automate
Governed agents deploy at earned autonomy levels while leaders manage supervisory capacity and continuous recalibration.
Action by Maturity Phase
Work on the earliest condition that does not hold.
Do not select the most ambitious phase. Use the phase identified by the weakest foundation, make its operating condition real in one workflow, and review the evidence.
Phase 1
Decision Clarity
Define who owns what and how decisions are made.
First move
Name one owner for the workflow outcome and one decider for its highest-consequence decision.
Evidence after 30 days
The owner, decision right, rationale, and escalation path appear in the record of real work.
Phase 2
Communication Discipline
Structure how information flows and build information governance.
First move
Choose where the workflow decision, supporting context, and source information must live.
Evidence after 30 days
Participants can find the current decision and trusted source without reconstructing them from meetings or chat.
Phase 3
Governance Embedding
Move controls from documents into the workflows where work happens.
First move
Put the workflow's approval, evidence, exception, and escalation rules into the place where the work occurs.
Evidence after 30 days
The workflow produces evidence that the control ran, including who reviewed exceptions and what happened next.
Phase 4
AI Amplification
Scale AI across governed decision types.
First move
Define one governed automation corridor, its human-review boundary, and the owner-set confidence threshold.
Evidence after 30 days
The owner can inspect quality, overrides, exceptions, and the evidence used to retain, narrow, or expand autonomy.
Phase 5
Human-Machine Orchestration
The architecture self-maintains through continuous optimization.
First move
Review human and agent responsibilities together, including supervisory capacity, lineage, and recalibration triggers.
Evidence after 30 days
The operating record shows who supervised what, where boundaries changed, and how feedback altered the workflow.
Illustrative example — not a customer case study
A customer-affecting exception keeps bouncing between teams.
Operations, product, compliance, and support all contribute, but no one owns the outcome and the approval is repeatedly reconstructed in meetings.
Day 1
Select the exception workflow and name the operations leader accountable for its customer outcome.
Day 7
Document the decider, required evidence, escalation threshold, and one place where the decision record lives.
Day 30
Review actual exceptions: which stalled, which were reversed, what evidence was missing, and whether the ownership rule held.
Next move
Only after the ownership proof holds, improve the information path or embed a control. Automation is not the first intervention.
Your Next Move
Find the constraint, then change one real workflow.
Use the diagnostic for direction, the maturity path for phase-specific boundaries, and this sequence to create one dated operating proof.
Need More Context?
Keep the supporting material in its proper role.
Use these references when the work requires more depth. They are not additional implementation stages.