Clone Solutions
Template

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)

TimeSegmentLeadOutput
0:00–0:15Why we're here: sponsor's openingExecutive sponsorThe "why" in the sponsor's words
0:15–0:45The agentic AI landscape: what is real, what is hype, where pilots stallSolutions PartnerShared vocabulary
0:45–1:30Live Clone demo on your actual workImplementation EngineerOne workflow seen end to end
1:30–2:00The autonomy ladder and how autonomy is earnedSolutions Partner, InfoSec leadAgreement on the control model
2:00–2:15Break
2:15–3:30Problem-statement session: each leader presents three pain pointsChange & Enablement LeadRaw problem list
3:30–3:50Clustering and quick prioritization (dot vote)Solutions PartnerTop priorities
3:50–4:00Decisions, owners and next stepsExecutive sponsorReadout decisions

The full-day version adds a 90-minute working block where each department head drafts problem statements using the Problem Statement Worksheet.

The autonomy ladder (shown in the session)

LevelThe CloneThe person
1. AssistDrafts, summarizes, researchesDoes everything else
2. RecommendPrioritizes and proposes, with reasoningDecides and acts
3. Execute with approvalActs after a named person approvesApproves, edits or rejects
4. Execute within limitsActs within set thresholds, escalates exceptionsOwns thresholds, reviews exceptions
5. OrchestrateCoordinates workflows and Clones under monitoringSets goals, can override at any time

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

Capture sheet

#LeaderDepartmentPain point (one line)Frequency / volumeCurrent cost or riskVotes
1
e.g.VP FinanceFinanceInvoice-to-PO matching is manual across ERP and email~2,400 invoices / month3 FTE; late-payment fees; month-end crunch6

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

RankProblemDepartmentExecutive ownerNext step
1Problem 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

RoleNameDateDecision
Executive sponsorApproved / Approved with changes
Solutions PartnerReadout issued