# Executive Briefing Readout

The agenda, capture sheet and one-page readout for the Day 1 executive briefing, ending in agreed priorities and named owners.

## What this is for

The executive briefing is where the engagement stops being a contract and becomes a shared plan. Leaders see a live Clone working on their own material, learn the five-level autonomy ladder, and each brings their top operational pain points. The readout records what was agreed, so the next eleven months are measured against decisions the leadership team actually made, not against what someone remembers from the room.

## When to use it

Use the agenda to plan the session in Mobilize, the capture sheet during the session, and the readout within two working days after it. Revisit the readout at the first steering committee and at the 90-day review.

## Who's involved

- **Executive sponsor:** opens the session, states the "why," owns the readout.
- **Steering committee and department heads:** each brings three pain points.
- **InfoSec lead:** attends the autonomy and governance segment.
- **Solutions Partner and Change & Enablement Lead:** facilitate.
- **Project Clone:** captures notes and drafts the readout.

## How to fill it in

1. Two weeks before, send each attendee the pre-work prompt (below) and collect pain points in advance.
2. Pick one real workflow for the live demo using the pre-read answers. Get the data owner's permission to use it.
3. Run the session using the agenda. Capture pain points live in the capture sheet so the room can see them.
4. Close the session with three decisions: top priorities, first-department candidates, and the date for the problem-statement deep dives.
5. Draft the readout within 48 hours. Circulate to attendees for corrections, then have the sponsor approve it.

## The template

### Pre-work prompt (send to each attendee)

> Bring the three operational problems that cost your team the most time, money or risk today. For each one, tell us: what happens, how often, who does it, and what it costs if it goes wrong. Don't bring solutions. Bring problems.

### Agenda (half-day version)

| Time | Segment | Lead | Output |
|---|---|---|---|
| 0:00–0:15 | Why we're here: sponsor's opening | Executive sponsor | The "why" in the sponsor's words |
| 0:15–0:45 | The agentic AI landscape: what is real, what is hype, where pilots stall | Solutions Partner | Shared vocabulary |
| 0:45–1:30 | Live Clone demo on your actual work | Implementation Engineer | One workflow seen end to end |
| 1:30–2:00 | The autonomy ladder and how autonomy is earned | Solutions Partner, InfoSec lead | Agreement on the control model |
| 2:00–2:15 | Break | | |
| 2:15–3:30 | Problem-statement session: each leader presents three pain points | Change & Enablement Lead | Raw problem list |
| 3:30–3:50 | Clustering and quick prioritization (dot vote) | Solutions Partner | Top priorities |
| 3:50–4:00 | Decisions, owners and next steps | Executive sponsor | Readout decisions |

The full-day version adds a 90-minute working block where each department head drafts problem statements using the [Problem Statement Worksheet](/playbook/templates/problem-statement-worksheet).

### The autonomy ladder (shown in the session)

| Level | The Clone | The person |
|---|---|---|
| 1. Assist | Drafts, summarizes, researches | Does everything else |
| 2. Recommend | Prioritizes and proposes, with reasoning | Decides and acts |
| 3. Execute with approval | Acts after a named person approves | Approves, edits or rejects |
| 4. Execute within limits | Acts within set thresholds, escalates exceptions | Owns thresholds, reviews exceptions |
| 5. Orchestrate | Coordinates workflows and Clones under monitoring | Sets goals, can override at any time |

Promotion between levels requires evidence and sign-off from InfoSec and the business owner.

### Capture sheet

| # | Leader | Department | Pain point (one line) | Frequency / volume | Current cost or risk | Votes |
|---|---|---|---|---|---|---|
| 1 | | | | | | |
| _e.g._ | _VP Finance_ | _Finance_ | _Invoice-to-PO matching is manual across ERP and email_ | _~2,400 invoices / month_ | _3 FTE; late-payment fees; month-end crunch_ | _6_ |

### Readout (one page)

**Engagement:** _Organization name_ · **Session date:** _date_ · **Attendees:** _names and titles_

**1. Why we are doing this (sponsor's words)**
_Two or three sentences._

**2. What we saw in the demo**
_Workflow demonstrated, what the Clone did, what people asked._

**3. Top priorities agreed**

| Rank | Problem | Department | Executive owner | Next step |
|---|---|---|---|---|
| 1 | | | | Problem statement deep dive by _date_ |
| 2 | | | | |
| 3 | | | | |

**4. First-department candidates:** _two or three departments, with the reason for each._

**5. Control model:** _Confirmation that the autonomy ladder is accepted, and any constraint stated by InfoSec or Legal._

**6. Concerns raised:** _Fears, objections and open questions, each with an owner._

**7. Decisions and dates**
- [ ] Problem-statement deep dives scheduled by _date_
- [ ] InfoSec kickoff scheduled by _date_
- [ ] Department heads nominate interviewees for the diagnostic
- [ ] First steering committee date set

## Good looks like

- **The demo used their data,** with permission, not a generic script. Leaders remember what they saw on their own work.
- **Pain points are problems, not solution requests.** "We need a chatbot" gets rewritten as the problem it would solve.
- **Every priority has one executive owner.** Not a committee, not "IT."
- **Concerns are written down.** Fear of replacement is named and answered: Clones add capacity, and people stay accountable for decisions.
- **Common mistake:** letting the session run as a product tour. Keep the demo to 45 minutes and spend the most time on problems.

## How Clone helps

The **Project Clone** takes live notes, fills the capture sheet, and drafts the readout the same day. The **Solutions Architect Clone** groups related pain points and links each to systems from the pre-read. In the portal, the readout is the Executive Briefing Readout deliverable in the Foundation stage; the sponsor's approval is recorded against it, and the agreed priorities seed the Problem Statement Register.

## Sign-off

| Role | Name | Date | Decision |
|---|---|---|---|
| Executive sponsor | | | Approved / Approved with changes |
| Solutions Partner | | | Readout issued |

## Related

- [Pre-read Questionnaire](/playbook/templates/pre-read-questionnaire)
- [Problem Statement Worksheet](/playbook/templates/problem-statement-worksheet)
- [Opportunity Scoring Rubric](/playbook/templates/opportunity-scoring-rubric)
- [Steering Pack](/playbook/templates/steering-pack)
- [Clone Solutions: Executive Briefing](https://clone.org/solutions/executive-briefing)

---
From the Clone Solutions Playbook: https://solutions.clone.org/playbook/templates/executive-briefing
