deliverable-creation
npx machina-cli add skill abinauv/business-consulting/deliverable-creation --openclawDeliverable 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
-
Start with the answer: Lead with the recommendation or key finding. Then provide supporting evidence. Never "build up to the answer."
-
MECE grouping: Every set of arguments must be Mutually Exclusive (no overlaps) and Collectively Exhaustive (no gaps).
-
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.
-
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
-
"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:
- Action title (the conclusion — most important)
- Key visual (chart, framework, or table — the evidence)
- Supporting text (annotations, bullet points)
- 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:
- Write the action title for every slide in sequence
- Read the titles aloud — do they tell a coherent story?
- Rearrange until the flow is tight
- 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:
- Lead with the section's conclusion
- Present the evidence
- 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
- Market assessment (8-15 pages)
- Strategic options evaluation (10-20 pages)
- Due diligence report (15-25 pages)
- Operational improvement plan (10-15 pages)
- Business case (5-10 pages)
One-Pager Creation
Structure
- Headline: States the key message or recommendation
- Key visual: One chart, framework, or table carrying the core argument
- 3-5 supporting points: Brief bullets with evidence and context
- 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.
| Time | Activity | Method | Output |
|---|---|---|---|
| 0:00-0:10 | Opening & objectives | Facilitator presentation | Shared understanding of goals |
| 0:10-0:30 | Current state review | Present key data, Q&A | Fact base alignment |
| 0:30-0:55 | SWOT brainstorm | Silent writing (5 min) → Group discussion → Vote on top items | Prioritized SWOT |
| 0:55-1:05 | Break | ||
| 1:05-1:30 | Strategic option generation | Small groups (3-4 people), each group proposes 2-3 options | 6-9 strategic options |
| 1:30-1:50 | Option evaluation & prioritization | Dot voting or impact/effort scoring as a group | Ranked options |
| 1:50-2:00 | Wrap-up & next steps | Facilitator summary, assign owners | Action 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).
| Time | Activity |
|---|---|
| 0:00-0:10 | Review objectives, explain criteria (Impact and Feasibility, each 1-5) |
| 0:10-0:30 | Score each initiative individually (silent scoring on printed scorecards) |
| 0:30-0:50 | Reveal scores, discuss items with high variance (disagreement = discussion needed) |
| 0:50-1:10 | Calibrate and finalize scores as a group, plot on 2x2 matrix |
| 1:10-1:20 | Identify Quick Wins (high impact, high feasibility) — these start immediately |
| 1:20-1:30 | Assign owners and next steps for top priorities |
Stakeholder Alignment Meeting (60 minutes)
Purpose: Get sign-off on a recommendation or resolve a disagreement.
| Time | Activity |
|---|---|
| 0:00-0:05 | State the decision needed (one sentence) |
| 0:05-0:15 | Present the analysis and recommendation (10 min, no interruptions) |
| 0:15-0:35 | Structured discussion: go around the table, each person states position + rationale |
| 0:35-0:50 | Address concerns, negotiate modifications if needed |
| 0:50-0:55 | Call for decision: Do we agree? If not, what's the process to resolve? |
| 0:55-1:00 | Confirm 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.
Source
git clone https://github.com/abinauv/business-consulting/blob/main/skills/deliverable-creation/SKILL.mdView on GitHub Overview
Deliverable Creation specializes in turning insights into polished, consulting-quality outputs such as slide decks, reports, memos, and one-pagers. It applies the Pyramid Principle, MECE, vertical and horizontal logic, and strict slide-design rules to ensure clarity and impact for client engagements. The approach centers on leading with the answer, structuring content for executive readability, and storyboard-led content development.
How This Skill Works
Start with the answer using the Pyramid Principle, ensuring MECE grouping and vertical logic so each level is supported by the next. Apply horizontal logic through deductive or inductive reasoning, and run the So what test on every data point to clarify client implications. Use the SCR narrative and the Ghost Deck method to storyboard before building content, then craft slides with action titles, one message per slide, and a clear visual hierarchy.
When to Use It
- Create a deck or strategy presentation for a client
- Prepare a board presentation or steering committee briefing
- Write an executive summary, memo, or one-pager
- Develop a synthesis or storyboard with pyramid-based structure
- Design a client deliverable in PowerPoint with slide architecture
Quick Start
- Step 1: Define the client objective and the top-line recommendation
- Step 2: Draft the slide sequence using the Ghost Deck method and SCR arc
- Step 3: Build slides with an action title, one key visual, and MECE-aligned bullets
Best Practices
- Lead with the recommendation: start each deck with the answer and key finding
- Maintain MECE: ensure every set of arguments is mutually exclusive and exhaustively covers the point
- Enforce vertical and horizontal logic: connect levels and supporting evidence clearly
- Use One Message Per Slide and strong action titles for clarity
- Storyboard first with the Ghost Deck method and SCR narrative before building content
Example Use Cases
- Executive summary slide for a board packet using a concise set of bold leads
- Pyramid-driven strategy deck that links top recommendation to supporting data
- Recommendation memo paired with data slides that prove the impact
- Timeline/roadmap slide showing phases, milestones, and owners
- Data/Chart slide with a single chart, an action title, and a source note