Start by role

Not every page is equally relevant to every seat. These four paths route through the seven disciplines in the order that builds understanding fastest for the decisions you actually own. Each path ends where the next conversation starts: the board pack, the architecture review, the portfolio review, the risk committee.

If you have five minutes, run the Readiness Diagnostic first. It names the focus area and points at the pages that address it.

CEO and board: own the bet

You approve the budget, set the priorities, and carry the outcome. You need to know why most programmes stall, where value concentrates, what to fund, what to stop, and what to ask for each quarter.

1. The Problem (Diagnose): why the spending has not converted into results, and why the gap is organizational, not technical.
2. Seven Failure Modes (Diagnose): the patterns to recognize before they recur.
3. Value Concentration (Prepare): where the returns actually sit.
4. The CAIO Mandate (Organize): what the role has to own, where it should report, and the authority it needs.
5. Financial Linkage (Operate): how AI reaches the income statement, and how to tell when it has not.
6. Board Reporting (Operate): what a board should see, and how often.
7. Case Studies (Proof): four anonymized composites, and what changed in each.
8. 12-Month Roadmap (Sustain): the sequence, and the gates that keep it honest.

CIO and CTO: build the system

You own the technology organization and the platform. You are building the capability stack, the control architecture, and the production bar that agents have to clear before they touch the business.

1. Structural Models (Organize): choose the structure before the tools.
2. Capability Stack (Design): the seven layers and who owns each.
3. Control Architecture (Design): the seven control domains, from identity and entitlements to retention and observability.
4. Governance Architecture (Govern): governance that runs at deployment speed.
5. Reference Patterns (Design): four deployment patterns and the controls each needs.
6. The Agentic Shift (Design): what changes when software acts.
7. Measurement Design (Operate): prove value in business terms.
8. Phase Gates (Sustain): what has to be true before the next phase.

CDO and CAIO: run the portfolio

You own readiness, the portfolio, and the operating model that makes the programme coherent. You need the readiness picture, a prioritization method that survives contact with the business, and governance built into delivery.

1. AI Readiness (Prepare): the four dimensions and how to read them.
2. Data Readiness (Prepare): why good enough for reporting is not good enough for AI.
3. Use Case Prioritization (Prepare): concentrate investment where it compounds.
4. Pilot to Production (Prepare): the bar a pilot has to clear.
5. Governance Architecture (Govern): policy, process, and technical layers.
6. Decision Rights (Organize): who decides, who approves, who can stop.
7. Knowledge Architecture (Organize): what the organization knows, and how AI reaches it.
8. Operating Architecture (Design): teams, RACI, and the platform boundary.

CFO and CRO: hold the line

You hold the numbers and the risk. You need the unit economics, the linkage from AI activity to financial outcomes, the model-risk posture, and the regulatory map across the jurisdictions you operate in.

1. Financial Linkage (Operate): the chain from AI outcome to EBIT, and where it breaks.
2. FinOps for Agents (Operate): cost per outcome, not cost per call.
3. GenAI Model Risk (Govern): what model risk means when the model generates.
4. Agent Governance (Govern): six controls for agents that act rather than recommend.
5. Regulatory Readiness (Govern): obligations by jurisdiction, mapped and tracked.
6. Shadow AI (Govern): the exposure you do not see.
7. Decision Records (Proof): the decisions a risk committee should expect to see recorded.

After any path, the operating system on one page is the map back to the whole.