See It Work · Book 12 · The Agentic Enterprise · Chapter 6
12 months, quarter by quarter — with decision gates
The readiness score says where you are; the investment framework says how much; this chapter says when — a quarter-by-quarter, 12-month timeline. The crucial mechanism is the decision gate: at the end of each quarter, the executive committee reviews three metrics before proceeding — portfolio ROI (is it delivering value?), agent fleet health (are agents reliable?), and organizational adoption (are people using them?).
The full detailed chart. Condensed for print legibility in the book; shown here at full size.
The most common failure in scaling is going faster than the organization can absorb — past what people can adopt and govern. Decision gates are the brake: you only proceed past a quarter if the metrics say the organization kept up.
Enterprise map · 12-month timelineready
What this means for you
Quarterly decision gates pace the 12-month rollout to what the organization can absorb. What this means for you: you get an ambitious but safe timeline — fast where you're ready, paused where you're not — so the transformation lands instead of stalling from being pushed faster than people and governance can keep up.
The 12-month plan is paced by quarterly decision gates:
Implementation Timeline
planquarter by quarter, 12 months
each quartera decision gate
3 metricsROI · fleet health · adoption
effectscale only as fast as you absorb
The most common failure is scaling faster than the organization can absorb — decision gates prevent it.
For the technical reader — the command, and how to verify it yourself
# one line · you do not need to run this see walkthrough
see walkthrough # -> a gated 12-month timeline paced to organizational absorption
Full step-by-step is in Appendix RX: Hands-On Demonstrations in the book.
ⓘDeterministic demonstration. The conversation is a faithful dramatization of the exercise; the receipt is the artifact it produces — the same every time, because the system is receipted. (Representative of the demo's structure; the production page renders the captured run.) No output here is fabricated. A live "run it yourself" mode is coming.