All chapters
  1. Start hereEnterprise AI adoption strategy, stage by stage and role by role
  2. Chapter 1Why AI adoption stalls
  3. Chapter 2Governance is the first enabler
  4. Chapter 3Who decides, who runs it
  5. Chapter 4Finding the right use cases
  6. Chapter 5The adoption ladder
  7. Chapter 6Role tracks
  8. Chapter 7Reuse first, as code
  9. Chapter 8The worked example
  10. Chapter 9The enablement program
  11. Chapter 10Measuring adoption honestly
  12. Chapter 11Evaluating and mapping tools
  13. Chapter 12Hands-on labs
  14. Chapter 13Templates, each filled
  15. Chapter 14Glossary
  16. AboutAbout this site
About

About this site

What this is, who wrote it, and what it is not.

This is a knowledge site on adopting AI stage by stage, role by role. It is written for the hardest case, regulated teams, and it applies to any organization that wants AI to reach production safely. Treat it as a working version: a shape to tune to your own workflow, not a fixed standard. It is general guidance for engineering leaders, AI-enablement leads and team leads who must make AI useful without bypassing the controls they already answer to. It is built from practice: the patterns come from real delivery work, written up as one fictional organization and one worked example (the contractual payment due date and the payment cutoff).

What it is and is not

It isIt is not
Patterns for governance, adoption, reuse and measurementLegal, regulatory or compliance advice
Templates, each shown blank and filledA certified control framework
Labs that run in any approved coding agentA product pitch for one tool
One worked example, followed from Stage 0 to Stage 4A record of any real organization

Who wrote it

Written by Sam Muthu, engineer and architect.

Sibling sites

SiteWhat it covers
ask-to-release.sammuthu.comWhat delivery looks like at the top of the ladder: one ask, front-loaded artifacts, release
claude.sammuthu.comAn architect's study guide to building with Claude
scaling.sammuthu.comScaling agents: patterns for running many agents well

How it was built

StepWhat happened
Static sitePlain HTML generated from markdown and JSON; no accounts, no sign-in
Locked specThe structure, example world and terms were fixed before any page was written
Multi-model reviewEvery page was reviewed by multiple AI models for accuracy and gaps
Human reviewA human read and approved every page before publishing

Disclaimer

This site offers patterns, not legal or regulatory advice. Scope and terms, such as what counts as a "model", follow each organization's own policy and jurisdiction. The organization, teams, services and examples are fictional. Counts, durations and percentages are illustrative, not measured results.