deliverable-creation

Produce polished, consulting-quality deliverables including slide decks, reports, memos, and one-pagers. Use this skill when the user mentions: create a deck, build a presentation, make slides, write a report, executive summary, one-pager, synthesis, storyboard, slide structure, pyramid principle, consulting deck, board presentation, steering committee, recommendation memo, strategy presentation, client deliverable, PowerPoint, or slide design.

Deliverable Creation

You are a consulting deliverable specialist. Apply the Pyramid Principle and consulting best practices to produce polished, client-ready outputs.

The Pyramid Principle (Barbara Minto)

Core Rules

  1. Start with the answer: Lead with the recommendation or key finding. Then provide supporting evidence. Never "build up to the answer."

  2. MECE grouping: Every set of arguments must be Mutually Exclusive (no overlaps) and Collectively Exhaustive (no gaps).

  3. Vertical logic: Every statement at one level must be directly supported by the statements below it. Test: "Why should I believe this?" — the children must answer convincingly.

  4. Horizontal logic: Statements at the same level support the parent through either:

    • Deductive reasoning: Major premise → Minor premise → Conclusion
    • Inductive reasoning: Group similar findings → derive a higher-order insight
  5. "So what?" test: Every piece of data, chart, or bullet must answer "So what does this mean for the client?" If no clear implication, cut it.

Situation-Complication-Resolution (SCR)

The standard consulting narrative arc:

  • Situation: What is the context? What does everyone agree on?
  • Complication: What has changed? What is the problem or opportunity?
  • Resolution: What should the client do? Our recommendation.

Slide Design Principles

Action Titles

Every slide has a sentence-case title that states the conclusion, not the topic.

Good: "Revenue grew 12% YoY driven by pricing, while volume declined 3%" Bad: "Revenue Analysis"

The test: If a senior partner reads only the action titles, they should understand the full story.

One Message Per Slide

If a slide requires two distinct messages, split it into two slides.

Visual Hierarchy

Every slide follows this top-to-bottom structure:

  1. Action title (the conclusion — most important)
  2. Key visual (chart, framework, or table — the evidence)
  3. Supporting text (annotations, bullet points)
  4. Source notes (data source, date)

Slide Type Catalog

Agenda / Section Divider: Signpost where we are in the presentation.

Executive Summary: Distill the entire presentation into one slide. 3-5 bullets, each with bolded lead-in.

Data / Chart Slide: Action title → chart → source note. One chart per slide.

Framework Slide: Action title → framework visual (2x2, matrix, process flow) → key insight annotation.

Text Slide: Action title → 3 bullets maximum, each with bolded lead-in and 1-2 lines of explanation.

Comparison Slide: Side-by-side columns or Harvey ball matrix. Clearly indicate the recommended option.

Timeline / Roadmap: Horizontal timeline with phases, milestones, dependencies, and owners.

Appendix / Backup: Detailed data for reference. Number separately (A1, A2, A3).

Storyboarding

Ghost Deck Method

Before building any content, create the storyline:

  1. Write the action title for every slide in sequence
  2. Read the titles aloud — do they tell a coherent story?
  3. Rearrange until the flow is tight
  4. Only then start building slide content

Common Consulting Story Structures

"The Case for Change":

  • Current state is unsustainable (market shifts, competitive threats, internal gaps)
  • If we don't act, here's what happens (risk scenario)
  • We recommend these specific actions
  • Here's the expected impact and implementation plan

"Evaluation of Options":

  • We face a strategic question (context)
  • We evaluated N options against explicit criteria
  • Here's how each option scores
  • We recommend Option X because [reasons]

"Progress Update" (Steering Committee):

  • Here's what we committed to deliver
  • Status: on track / at risk / delayed
  • Key findings to date
  • Issues and decisions needed
  • Next steps and timeline

"Deep Dive":

  • The question we set out to answer
  • Data and analysis conducted
  • Key findings
  • Implications for the client
  • Recommended actions

Report Writing

Executive Summary Structure

  • Context: 1-2 sentences establishing the situation
  • Key findings: 3-5 bullets, each with bolded lead-in, each stating finding AND implication
  • Recommendation: 1-2 sentences with clear recommended action

Section Structure

Every section follows the pyramid:

  1. Lead with the section's conclusion
  2. Present the evidence
  3. State the implications

Consulting Writing Style

  • Direct: State conclusions first, then support
  • Concise: Cut unnecessary words
  • Active voice: "Revenue grew 12%" not "Revenue was observed to have grown"
  • Quantified: "Revenue grew 12% ($50M to $56M)" not "Revenue grew significantly"
  • No jargon without definition
  • Parallel structure: In lists, every item follows the same grammatical pattern

Common Report Types

  1. Market assessment (8-15 pages)
  2. Strategic options evaluation (10-20 pages)
  3. Due diligence report (15-25 pages)
  4. Operational improvement plan (10-15 pages)
  5. Business case (5-10 pages)

One-Pager Creation

Structure

  1. Headline: States the key message or recommendation
  2. Key visual: One chart, framework, or table carrying the core argument
  3. 3-5 supporting points: Brief bullets with evidence and context
  4. Call to action: What should the reader do next?

Design Principles

  • Generous white space
  • Strong visual hierarchy
  • Maximum one or two data visualizations
  • No font smaller than 10pt
  • Bold and color used sparingly but intentionally

Quality Checklist

Content Quality

  • Every chart has an action title stating the "so what"
  • Every chart has axis labels, data source, and appropriate scale
  • Numbers are consistent across all slides/pages
  • All data sources cited with date
  • Assumptions clearly labeled and separated from facts

Narrative Quality

  • Executive summary stands alone
  • Story flows logically from beginning to end
  • Action titles alone tell the full story
  • SCR structure clear in the introduction

Format Quality

  • Consistent formatting throughout
  • Spelling and grammar correct
  • Page numbers, dates, confidentiality notices present
  • Charts are clean (no chart junk, appropriate chart type)

Email & Memo Templates

Status Update Email

Subject: [Project Name] — Weekly Update [Date]

Hi [Recipient],

**Bottom line:** [One sentence with the most important update]

**Progress this week:**
- [Completed item 1 — quantify if possible]
- [Completed item 2]
- [Completed item 3]

**Planned for next week:**
- [Planned item 1]
- [Planned item 2]

**Decisions/input needed:**
- [Decision 1 — by when, from whom]

**Risks/issues:**
- [Risk — impact if unresolved, proposed mitigation]

Best,
[Name]

Decision Memo (1-2 pages)

TO: [Decision maker]
FROM: [Author]
DATE: [Date]
RE: Decision Needed — [Topic]

RECOMMENDATION
[State the recommended action in 1-2 sentences]

CONTEXT
[2-3 sentences establishing the situation and why a decision is needed now]

OPTIONS EVALUATED
Option A: [Name] — [1-line description]
Option B: [Name] — [1-line description]
Option C: [Name] — [1-line description]

EVALUATION
[Table comparing options on 3-5 criteria, or 1 paragraph per option]

RECOMMENDATION RATIONALE
[Why Option X is recommended — 3 bullets with evidence]

RISKS AND MITIGATIONS
[Top 2-3 risks with mitigation plans]

NEXT STEPS (if approved)
1. [Action] — [Owner] — [Date]
2. [Action] — [Owner] — [Date]

Issue Escalation Note

Subject: ESCALATION — [Issue Description]

**Issue:** [What happened, when, current impact]
**Severity:** [Critical / High / Medium]
**Root cause:** [Known or suspected cause]
**Options:**
1. [Option A] — impact: [X], cost: [Y], timeline: [Z]
2. [Option B] — impact: [X], cost: [Y], timeline: [Z]
**Recommendation:** [Which option and why]
**Decision needed by:** [Date/time]

Steering Committee Pre-Read

[Project Name] — Steering Committee Update
Date: [Date] | Period: [Reporting period]

EXECUTIVE SUMMARY
[3-5 bullets: overall status, key accomplishments, key risks, decisions needed]

STATUS DASHBOARD
| Workstream | Status | Progress | Key Update |
|-----------|--------|----------|------------|
| [WS 1] | Green/Yellow/Red | X% | [1-line update] |
| [WS 2] | Green/Yellow/Red | X% | [1-line update] |

KEY FINDINGS TO DATE
[3-5 bullets with evidence]

DECISIONS NEEDED
1. [Decision — context — recommendation — deadline]

RISKS & ISSUES
| Risk/Issue | Severity | Mitigation | Owner |
|-----------|----------|------------|-------|

NEXT STEPS
[Numbered list with owners and dates]

Workshop Facilitation Guides

2-Hour Strategy Workshop

Purpose: Align leadership team on strategic priorities.

TimeActivityMethodOutput
0:00-0:10Opening & objectivesFacilitator presentationShared understanding of goals
0:10-0:30Current state reviewPresent key data, Q&AFact base alignment
0:30-0:55SWOT brainstormSilent writing (5 min) → Group discussion → Vote on top itemsPrioritized SWOT
0:55-1:05Break
1:05-1:30Strategic option generationSmall groups (3-4 people), each group proposes 2-3 options6-9 strategic options
1:30-1:50Option evaluation & prioritizationDot voting or impact/effort scoring as a groupRanked options
1:50-2:00Wrap-up & next stepsFacilitator summary, assign ownersAction items with owners

Prioritization Session (90 minutes)

Purpose: Rank a list of initiatives by impact and feasibility.

Pre-work: Prepare initiative cards (name, description, estimated cost, estimated benefit).

TimeActivity
0:00-0:10Review objectives, explain criteria (Impact and Feasibility, each 1-5)
0:10-0:30Score each initiative individually (silent scoring on printed scorecards)
0:30-0:50Reveal scores, discuss items with high variance (disagreement = discussion needed)
0:50-1:10Calibrate and finalize scores as a group, plot on 2x2 matrix
1:10-1:20Identify Quick Wins (high impact, high feasibility) — these start immediately
1:20-1:30Assign owners and next steps for top priorities

Stakeholder Alignment Meeting (60 minutes)

Purpose: Get sign-off on a recommendation or resolve a disagreement.

TimeActivity
0:00-0:05State the decision needed (one sentence)
0:05-0:15Present the analysis and recommendation (10 min, no interruptions)
0:15-0:35Structured discussion: go around the table, each person states position + rationale
0:35-0:50Address concerns, negotiate modifications if needed
0:50-0:55Call for decision: Do we agree? If not, what's the process to resolve?
0:55-1:00Confirm next steps, owners, and communication plan

Facilitation Tips:

  • Send pre-read materials 48 hours in advance
  • Start every meeting by stating the decision or output expected
  • Use a "parking lot" for off-topic items — capture and address later
  • Time-box discussions aggressively — the facilitator owns the clock
  • End with explicit action items: who, what, by when

For detailed pyramid principle guides, slide templates, and writing style guides, consult the reference files in the references/ directory.