Deliverables
Purpose
Deliverables translate the sprint into decision-ready artifacts.
They are designed to:
- Stand on their own
- Be shared internally without explanation
- Support both executives and operators
Everything is intentional.
Deliverable Set
The sprint produces three core deliverables.
| Deliverable | Audience | Role |
|---|---|---|
| Executive Summary (1-pager) | C-suite, Board | Fast alignment |
| Executive Readout Deck | Leadership team | Decision-making |
| Raw Source Package | Internal teams | Depth and continuity |
1. Executive Summary (One-Pager)
Purpose: provide a crisp, high-signal overview that can be read in under 5 minutes.
What It Answers
- Why this was done
- What was learned
- What to do next
Canonical Structure
| Section | Content |
|---|---|
| Why Now | Business context and urgency |
| What We Heard | Key themes from interviews |
| Where AI Helps | 3–5 programs/themes |
| Value at Stake | Directional ROI |
| Recommended Next Steps | Concrete actions |
This document should be printable and email-forwardable.
2. Executive Readout Deck
Purpose: walk leadership from reality to insight to roadmap.
This is the primary discussion artifact.
Typical Flow
| Section | Goal |
|---|---|
| Framing & scope | Set expectations |
| What we did | Build credibility |
| What we heard | Evidence-backed insight |
| Opportunity landscape | Breadth and prioritization |
| Themes & programs | Strategic focus |
| Roadmap | Sequencing |
| ROI & impact | Justification |
| Next steps | Momentum |
The deck references evidence but does not overwhelm with detail.
Appendix slides may include:
- System landscape
- Scoring methodology
- Example quotes
3. Raw Source Package
Purpose: preserve institutional knowledge and support execution.
This is the most valuable artifact long-term.
Contents
| Artifact | Description |
|---|---|
| Opportunity log | All raw observations |
| Scoring sheets | Effort, value, risk |
| Theme mapping | How rows rolled up |
| System inventory | Data & systems landscape |
| Interview notes | Normalized notes |
| Transcripts | Verbatim records |
This package is typically delivered as:
- Excel workbook
- Shared folder
- Read-only by default
Delivery Principles
| Principle | Why |
|---|---|
| Evidence-backed | Builds trust |
| Consistent language | Reduces confusion |
| Tool-agnostic | Avoids bias |
| Executable | Enables action |
No artifact should require the sprint team present to explain it.
What Is Explicitly Not Delivered
| Not Included | Reason |
|---|---|
| Detailed solution designs | Post-sprint work |
| Vendor recommendations | Avoid lock-in |
| Implementation plans | Separate engagement |
| Change management | Requires ownership |
Handoff & Ownership
At delivery:
- Walk through findings live
- Answer challenges directly
- Confirm owners for next steps
- Clarify what happens after the sprint
The sprint ends when leadership can say: "We know what to do first, and why."
Success Signal
Deliverables are successful if:
- Executives read them
- Teams reference them weeks later
- The raw package is reused
- The roadmap survives scrutiny
This is the moment the sprint either creates momentum or fades.