Purpose

A 2-page portfolio-level readout to the Executive Sponsor at the end of every quarter. Demonstrates the program is working with numbers, not anecdotes. Drives budget renewal, scope expansion, and exec air cover.

This is portfolio-level, not per-agent. Per-agent quarterly reviews happen separately (within the same M17 cadence). The exec readout is the synthesis.

• When you use it: Within 10 business days of every quarter end.
• Who fills it: CoE Lead drives. Builder + Finance provide data.
• Audience: Executive Sponsor (primary). CFO + Department Heads + CISO (CC).
• Length: 2 pages. Anything longer means the headline got buried.
• Output: Slide deck (Google Slides / Keynote) or PDF, distributed before the monthly 1:1 with the sponsor.

Worked example (ACME Corp Q2 2026 — 5 quarters into the program)

ACME Corp — AI Adoption Program — Q2 2026 Exec Readout

Period: April–June 2026 Author: Morteza Moradi (AI Implementation Lead) Distributed: 2026-07-08 Audience: Jane Doe (CEO + sponsor) · Bob Lin (CFO) · Pat Lee (CISO) · Department Heads · cc John Smith (GC)

Page 1 — Headline + Portfolio

Headline

The program shipped 2 new production agents this quarter (total 5 in production). Total annualized ROI now ~$96K with zero Sev-1 incidents to date. EU AI Act readiness 60%. Q3 ask: budget for AI Gateway and CoE evolution to Hybrid.

Portfolio snapshot (as of 2026-06-30)

Quarterly metrics

Five monitoring signals — portfolio rollup

Page 2 — Risks, lessons, asks

Q2 incidents

1 Sev-2 incident this quarter: sales-lead-qualification HITL rate fell below 70% week 5.

• Root cause: prompt drift after a manual edit not run through eval.
• Mitigation: enforced eval-on-prompt-change in CI/CD (now blocks merge without eval pass).
• Post-mortem: templates/10-post-mortem--sales-lead-qualification--2026-05-19.md
• Action items: all 4 closed within 14 days.

Risk and compliance status

Lessons fed back to the framework

• Eval-on-prompt-change must be mandatory CI/CD gate. Q2 Sev-2 root cause. Framework v1.1 updated.
• Drift detector false-positive rate matters. Need to tune sensitivity to avoid alarm fatigue. Q3 work item.
• First Champion network handoff in Q2 (Ops Champion onboarded). Framework's "Hybrid CoE" evolution is starting to show — Ops Champion will build their first agent in Q3 without CoE doing the build.

Q3 plan + asks

Plan:

• 2 new production agents (marketing-content-draft finishing pilot; ops-vendor-onboard completes intake → build → pilot)
• First quarter where a Champion (Ops) builds an agent without CoE directly building it — proves Hybrid CoE works
• Continue NIST AI RMF self-assessment (target 90% by end of Q3)
• Sector overlay: pilot the EU AI Act overlay (we have EU customers; want compliance signal for enterprise deals)

Asks of the sponsor:

1. Budget: $25K for AI Gateway adoption (Portkey or LiteLLM). Centralizes LLM routing, cost controls, policy enforcement across all agents. ROI: prevents future LLM cost overruns + simplifies vendor switching. Pays back in ~6 months on cost-control alone.
2. Hiring: approval to add 1 FTE Data Engineer to support the data foundation (golden sets, drift detection). Currently borrowing time from Analytics team. As portfolio grows, this becomes a constraint.
3. Decision: should we pursue ISO/IEC 42001 certification? Initial gap analysis shows ~12-month path. Costs ~$60K. Value: signal to enterprise customers. Need exec view before scoping further.

Open invitations

• Next portfolio readout: 2026-10-08 (Q3 2026)
• Sponsor 1:1: weekly cadence continues
• Open invitation to any department head to walk through the framework with me — 60 min, on request

Distributed

Blank template (copy below for your quarter)

# [Company] — AI Adoption Program — [Quarter] [Year] Exec Readout

**Period:** [Quarter date range]
**Author:** [CoE Lead]
**Distributed:** [YYYY-MM-DD]
**Audience:** [Sponsor name + role] · [CFO] · [CISO] · [Department Heads] · cc [General Counsel]

---

## Page 1 — Headline + Portfolio

### Headline

> [2–3 sentence headline. Lead with the most important number. End with the ask.]

### Portfolio snapshot (as of [end of quarter date])

| Agent | Status | Tier | Launch | YTD ROI | YTD incidents |
|---|---|---|---|---|---|
| | | | | | |

### Quarterly metrics

| Metric | [Prev Q] | [This Q] | Trend |
|---|---|---|---|
| Production agents | | | |
| Quarterly ROI | | | |
| Sev-1 incidents | | | |
| Sev-2 incidents | | | |
| Avg agent HITL acceptance | | | |
| Vendor-AI catalog refreshes completed | | | |
| Department Champions active | | | |

### Five monitoring signals — portfolio rollup

| Signal | Portfolio status |
|---|---|
| Output distribution shift | |
| HITL escalation rate | |
| Decision audit trails | |
| Cost per execution (step level) | |
| Exception routing | |

---

## Page 2 — Risks, lessons, asks

### This quarter's incidents

[List Sev-1 and Sev-2 incidents with root cause + mitigation + post-mortem link. If zero, say so.]

### Risk and compliance status

| Area | Status | Notes |
|---|---|---|
| EU AI Act readiness | [%] | |
| NIST AI RMF self-assessment | [%] | |
| ISO/IEC 42001 readiness | [%] | |
| Vendor-AI inventory | [Current / Stale] | |
| Shadow AI surface | [Low / Medium / High risk] | |

### Lessons fed back to the framework

- [Lesson 1]
- [Lesson 2]

### [Next quarter] plan + asks

**Plan:**

- [Concrete items for next quarter]

**Asks of the sponsor:**

1. **Budget:** [specific number + what it buys + payback]
2. **Hiring:** [specific role + justification]
3. **Decision:** [strategic question requiring exec input]

### Open invitations

- Next portfolio readout: [date]
- [Other standing invitations]

---

### Distributed

| Recipient | Role | Distribution date |
|---|---|---|
| | | |

Usage notes

• 2 pages is the cap. If you can't fit the program's state on 2 pages, the program is either too sprawling to summarize or you're including the wrong things. Either way, force the discipline.
• Lead with the headline. Sponsor reads the first paragraph. Everything else is reference. If the first paragraph doesn't convey "the program is delivering," rewrite it.
• Always include the ask. Even if the ask is "no asks this quarter, but here's what I'm watching." Don't waste the cycle.
• Distribute before the 1:1, not at it. Sponsor reads it on their own time, comes to the meeting with questions.
• Tie incidents to action items closed. "We had 1 Sev-2; all 4 action items closed within 14 days" is what an exec wants to hear, not just "we had 1 Sev-2."
• Compliance readiness shown as percentages. EU AI Act + NIST AI RMF + ISO 42001 are long-running mappings. Show progress, not just status.
• The shadow-AI line matters. It demonstrates the vendor-AI inventory is working as designed.

Common pitfalls

Framework cross-references

• framework.md §11.2 (quarterly review at portfolio level)
• framework.md §29 (ROI tracking — feeds Portfolio snapshot)
• framework.md §21 (5 monitoring signals — portfolio rollup)
• framework.md §15 (Registry — source of portfolio data)
• framework.md §22.1 EU AI Act Article 72 (post-market monitoring at portfolio level)
• framework.md §22.3 ISO/IEC 42001 Clause 9.3 (management review)
• workflows.md Step 15 (Quarterly review)
• workflows.html → In Action view → node M17 (Quarterly review)