Delivering & Measuring AI Programs
The program manager's lens on AI: run a rollout across teams and prove it worked — stage gates wired to real signals, a RAID log, and a program scorecard. Runs a real, deterministic scorecard over a three-team rollout, and teaches the discipline that separates a program review from a victory lap: adoption is not success. Read the lagging signals adoption hides.
"Cirrus adopted as well as everyone — and got blocked at GA on override rate and incidents. Adoption isn't ready."
6 Interactive Sessions
Short, interactive sessions: watch it work, try it, then build it yourself. You can go deeper at any time in the written chapters.
- 1
Shape an AI program: the outcome and the risks
An AI rollout can meet every date and still fail, because the assistant can give worse answers while the plan looks fine. Shaping the program means writing quality into the outcome and naming the risks that only AI brings.
- 2
Set stage gates that check quality as well as use
A stage gate decides when a team can widen its use of the assistant. If the gate only checks how many people use it, a team with poor quality can pass. Each gate past the first one needs a quality rule too.
- 3
Keep a RAID log with an owner on every line
A risk that someone mentions in a meeting is not being managed until it is written down with an owner. The RAID log is where the AI risks from lesson 1 become tracked work.
- 4
Measure who uses the assistant, not just who has it
Switching on seats is not the same as people using the tool. Measure real use. Then remember that even real use only shows the rollout is moving, not that the assistant is working.
- 5
Read the scorecard: use and quality side by side
Read the program scorecard one whole row at a time, with adoption next to the quality signals, and find the team whose good adoption hides a quality problem.
- 6
Make the gate call and report it honestly
Turn the scorecard into a decision: move the healthy teams to GA, hold the team that adopted well but is not ready, report it plainly, and give the held team a fix rather than a new date.
Skills you'll practise
Practice data included
- Program plan + stage gates
- RAID log
- Weekly rollout events (3 teams)
- Program scorecard
- Gate verdicts
How this certificate is scored
Your certificate shows how many of your written answers met the rubric below, checked by an AI grader. Anyone who checks your certificate sees it.
- You answer 6 short questions, one for each module, in your own words (at least 40 words each).
- An AI grader checks each answer against what its module asks for: it must answer the question, use the course's practice case specifically, and be correct.
- To pass, at least 5 of the 6 answers must meet that bar. The certificate says the answers were graded by AI.
The rubric
- Module 1, Shape the Program: A program frame: outcome, teams, AI-specific risks.
- Module 2, Stage Gates That Bite: Gates wired to adoption + quality signals.
- Module 3, The RAID Log: AI-specific risks/assumptions/issues/dependencies with owners.
- Module 4, Rollout & Adoption: Adoption (active use) measured distinct from deployment.
- Module 5, The Program Scorecard: A read of leading vs lagging signals per team.
- Module 6, Steer & Report: A gate decision + honest exec update, loop closed.
What you walk away with
Shareable portfolio
A public URL showing your module timeline, patterns mastered, and completion status.
Everything you build
Download all your work as a ZIP file. It is yours to keep.
Module walkthrough
Each module documented with deliverables and the production pattern you implemented.
Ready to start Delivering & Measuring AI Programs?
First course free. $20 per course after that.