Executive Meeting Playbook

Introduction

Executives decide quickly when the storyline is clear and the risk is controlled. They disengage when a meeting meanders or when the ask is hidden under features and jargon. Your job is to compress the decision: make the outcome attractive, the path credible and the next step obvious.

This playbook helps you structure a 30-minute executive conversation that leads to action. You will pre-wire stakeholders, come with a short narrative supported by evidence, and state two or three specific asks that unblock progress. You will finish with a recap in the executive’s language and a calendar hold for the next step.

We design for mixed contexts: in-person, video, and hybrid. In all cases, clarity beats slides. Expect to spend more time on setup—who is in the room, how they decide, what they care about—than on polishing visuals. Executives prefer documents that help them think, not performances.

Finally, we protect the relationship. We will avoid cornering the executive into yes/no traps and instead present options with trade-offs. This preserves credibility and often accelerates sponsorship because the decision feels owned, not sold.

What good looks like

• Storyline in 90 seconds: context → problem cost → proposed path → asks.
• Evidence first: customer proof, benchmarks, pilot data.
• Two or three asks: time, people, data, or funding—never a vague “support”.
• Visible decisions: options with trade-offs and a default recommendation.

Prep & pre-wire

• Map decision style (data-first, people-first, risk-first); tailor narrative.
• Brief chief of staff/EA; confirm agenda and decisions required.
• Share a 1-page pre-read: problem cost, options, recommendation, asks.

30-minute script

• 0–2: open and confirm outcomes for the meeting.
• 2–5: 90-second storyline; show the math on problem cost.
• 5–12: evidence pack; 1–2 slides max or a one-pager.
• 12–20: options with trade-offs; address likely objections.
• 20–25: the asks; confirm feasibility and owners.
• 25–30: recap in executive’s words; lock next milestone and date.

Objection handling

• “This looks expensive” → TCO vs. status quo; cost of delay in months.
• “Not enough capacity” → propose a bounded pilot; show resource profile.
• “Security risk” → pre-wire with security; present controls and prior approvals.

Worked examples

Example A — Retail COO

Storyline: shrink up 18 bps; proposal reduces by 10 bps in 90 days via analytics + process change.

Asks: 2 store pilots, ops lead 30% for 6 weeks, data extract approval.

Result: Pilot green-lit; CFO looped for savings validation in Week 4.

Example B — Bank CIO

Storyline: time-to-change too slow; branch changes miss windows.

Asks: sandbox access; joint security review; 14-day build challenge.

Result: CIO sponsors challenge; incumbent exposed; path to phase-in.

Example C — Manufacturing CFO

Storyline: overtime costs; plan cuts 12% with better scheduling.

Asks: ops SME time; 2-week trial; finance partner for ROI model.

Result: CFO issues conditional go pending trial success.

Metrics

Leading: executive meeting rate, pre-read open rate, decision rate per meeting.

Lagging: sponsor creation, pilot approvals, deal cycle time reduction.

Decisions accelerate when evidence arrives before the ask.

Implementation checklist

• Publish a 1-page pre-read template and 90-sec storyline guide; store examples.
• Stand up a proof library (references, pilots, benchmarks) with owner and freshness date.
• Define pre-wire steps with EA/chief of staff; add a simple “decision required” field to invites.
• Create objection scripts for cost, capacity and security with links to evidence.
• Block monthly dry-runs for strategic meetings; assign a facilitator and timekeeper role.

Measurement

Team level: decision rate per exec meeting, pre-read open rate, time-to-next-step (≤48h), sponsor creation, pilot approval rate.

Individual level: storyline quality (90s), ask clarity (2–3, specific), evidence-first compliance, follow-up speed, meeting outcomes logged.

Team buy-in

• Position the playbook as decision support, not theater—clarity beats slides.
• Practice short: run 10-minute drills on storyline + asks; coach with recordings.
• Celebrate meetings where options + trade-offs led to a fast, owned decision.

90-day rollout

Weeks 1–2 — Stand up the system

• Owners: Sales Leadership (lead), Enablement, PMM.
• Artifacts: pre-read template, storyline guide, proof library, objection scripts.
• Actions: define pre-wire checklist; create “decision required” + “owners” fields in invites; publish follow-up email snippet.
• Exit: templates live; 10 proof assets curated with owners and expiry dates.

Weeks 3–4 — Pilot five executive meetings

• Run dry-runs; assign facilitator/timekeeper; record outcomes and next steps.
• KPIs: decision rate ≥60%; next step scheduled ≤48h; pre-read open rate ≥70%.

Weeks 5–6 — Instrument & coach

• Dashboard: meetings held, decision rate, time-to-next-step, proof usage, sponsor creation.
• Coaching: 90-sec storyline drills; objection handling roleplays with evidence.

Weeks 7–8 — Roll out

• Standardize pre-read and recap; require options + recommendation in all exec forums.
• Create fast lane for references and security pre-checks tied to exec meetings.

Weeks 9–10 — Tighten cross-functional path

• Finance provides quick TCO model; Legal drafts pilot LOA; Security publishes pre-check intake form.
• PMM refreshes three benchmark packs most used in exec conversations.

Weeks 11–12 — Bake into rhythm

• Add “exec meeting health” to monthly review: decision rate, proof freshness, time-to-next-step.
• Target state: decision rate ≥65%; next step ≤48h in ≥80% of meetings; pilot approvals up 20% vs. baseline.

Companion template

Use the template to craft your 90-sec storyline, pre-read and clear asks.

Open companion template