Client Deliverables

Critical Disclaimer

All outputs require senior review and client editing before submission. This skill generates high-quality drafts but does not replace consultant judgment. Verify data accuracy, validate assumptions, ensure tone aligns with client relationship, and confirm commercial sensitivity before sharing externally.

---

Deliverable Types

Executive Summary / Readout

• When: Quick insights for busy executives, steering committee updates, phase conclusions
• Length: 2-4 pages maximum
• Structure: Situation, 3-5 key findings, 2-3 immediate actions, next steps
• Tone: Confident, action-oriented, no hedging

Full Assessment Report

• When: Comprehensive diagnosis after discovery phase, detailed client understanding needed
• Length: 20-40 pages
• Includes: Methodology, complete findings with evidence, detailed analysis, prioritized recommendations
• Audience: Business leaders, board-level review

Strategic Recommendations Document

• When: Solution-focused work, post-diagnosis phase, requires detailed rationale
• Length: 15-25 pages
• Focus: Recommendations, business case, change management implications, success metrics
• Structure: Problem restatement, options analysis, recommendation with rationale, implementation approach

Implementation Roadmap

• When: After recommendations approved, team needs execution clarity
• Length: 10-15 pages
• Includes: Phased timeline, dependencies, resource requirements, milestones, governance structure
• Format: Gantt charts, decision trees, workstream breakdown

Process Improvement Analysis

• When: Operational effectiveness focus, efficiency gains quantifiable
• Length: 12-20 pages
• Emphasis: Current-state mapping, bottleneck analysis, redesign options, ROI calculation

Organizational Assessment

• When: Structure, capability, culture evaluation needed
• Length: 15-25 pages
• Covers: Org design options, capability gaps, talent implications, governance model

Market Entry Strategy

• When: Expansion, new geography, new segment decisions
• Length: 20-30 pages
• Analysis: Market sizing, competitor landscape, go-to-market options, risk assessment

Operating Model Design

• When: Fundamental transformation required, aligns people, process, technology
• Length: 25-35 pages
• Scope: Target operating model, capability requirements, transition plan

---

Standard Report Structure

1. Executive Summary (0.5-1 page)

• Situation statement (1-2 sentences)
• 3-5 key findings with commercial impact
• 2-3 recommended actions with success metrics
• One "ask" of the reader (typically approval to proceed)

2. Methodology (0.5-1 page)

• Work approach, timeline, interviews/data sources
• Scope boundaries and what is/isn't covered
• Limitations (data gaps, assumptions)

3. Findings with Evidence (6-12 pages)

• Organized by theme, not by interview or source
• Lead with insight, then supporting evidence
• Mix of qualitative (quotes, case studies) and quantitative (metrics, benchmarks)
• Include client's own data prominently
• Every claim substantiated; no unsupported assertions

4. Analysis (4-8 pages)

• Why findings matter; connect dots across areas
• Quantify impact where possible (revenue at risk, cost opportunity, capability gap)
• Address root causes, not symptoms
• Use frameworks to structure thinking (but see framework section below)

5. Recommendations (2-4 pages)

• Prioritized by impact and ease (impact/effort matrix reference)
• Specific, not generic; avoid platitudes
• Include success metrics for each recommendation
• Address key risks and dependencies
• "Quick wins" separated from strategic moves

6. Implementation Roadmap (1-2 pages)

• Phased approach with clear sequencing
• Key milestones and decision gates
• Stakeholder roles and governance
• High-level resource and budget estimate

7. Appendices

• Detailed methodology and data sources
• Complete benchmarking data
• Organizational charts, process maps
• Bibliography and interview list

---

Presentation / Deck Structure

Slide-by-Slide Approach

Slide 1: Title Slide

• Project name, date, audience, presenter

Slides 2-3: Situation Overview

• Client's competitive context, market dynamics, challenge statement
• Why this matters now (urgency)

Slides 4-7: Key Findings (1 finding per 1-2 slides)

• State finding clearly in headline
• 2-3 support elements: metric, anecdote, or visual
• Each slide must answer the "so what"

Slide 8: Finding Synthesis

• How findings connect; implications for the business
• Avoid listing; show relationships

Slide 9-10: Recommendations

• Lead with the recommendation (headline format)
• Business case on same or adjacent slide
• Avoid detailed implementation here; that's for roadmap conversation

Slide 11: Next Steps

• Immediate actions (next 30 days)
• Decision gates required from client
• Timeline for implementation phase

Slide 12: Appendix Roadmap

• If live presentation, offer: "We have detailed analysis on…" to manage Q&A

Design Principles

• One idea per slide
• Headlines are complete thoughts, not labels ("Revenue Growth Constrained by Capacity" not "Capacity Analysis")
• Charts must have clear takeaway; avoid decoration
• Ratio 60% visuals, 40% text
• Consistent color coding across decks (e.g., red=risk, green=opportunity)

---

Consulting Framework Selection Guide

MECE (Mutually Exclusive, Collectively Exhaustive)

• Use when: Categorizing data, segmenting markets, structuring analysis
• Value: Ensures complete coverage with no overlap; builds credibility
• Filler risk: High; often forced; validate that breaking down 3 ways is justified

Issue Trees (Problem Decomposition)

• Use when: Diagnosing root causes, framing large problems, client alignment on scope
• Value: Shows methodical thinking; aligns team on problem definition
• Application: Build top-down (problem → sub-problems → testable hypotheses)

Porter's Five Forces

• Use when: Competitive intensity analysis, industry attractiveness assessment
• Value: Standard framework; board-level credibility; identifies strategic leverage points
• Caution: Generic; may miss industry-specific dynamics

Value Chain Analysis

• Use when: Operational efficiency, cost structure, competitive differentiation by activity
• Value: Links activities to customer value; identifies cost/quality drivers
• Best for: Manufacturing, complex operations, outsourcing decisions

McKinsey 7S (Strategy, Structure, Systems, Skills, Staff, Style, Shared Values)

• Use when: Organization design, capability assessment, culture-strategy alignment
• Value: Holistic; prevents overlooking capability or cultural gaps
• Risk: Can be generic; apply only if all 7S are truly relevant

BCG Matrix (Growth-Share)

• Use when: Portfolio prioritization, resource allocation across business units
• Value: Simple, memorable, guides investment decisions
• Limitation: Oversimplifies; use with caution in mature portfolios

SWOT (Strengths, Weaknesses, Opportunities, Threats)

• Use when: Strategic planning, competitive positioning
• Value: Familiar; easily understood
• Filler risk: Extremely high; most SWOT analyses add little; avoid unless driving specific decisions

PESTLE (Political, Economic, Social, Technological, Legal, Environmental)

• Use when: Macro environment assessment, scenario planning, market entry risk
• Value: Comprehensive external scan
• Application: Focus on factors material to your specific decision (not all six equally)

When Frameworks Are Filler

• If the framework doesn't change your answer, drop it
• If you're applying a framework because it's "consulting-like," skip it
• If the client doesn't know what it means and you must explain it, reconsider

---

Data Visualization in Deliverables

The "So What" Test

Every chart must answer: "What should the reader DO with this information?" If the answer is "nothing," delete the chart.

Chart Selection

• Trend over time: Line chart (multiple lines acceptable if ≤4)
• Comparison across categories: Bar chart (horizontal for long labels)
• Part-to-whole: Waterfall (better than pie for understanding contribution) or stacked bar
• Correlation or density: Scatter plot
• Process or hierarchy: Flowchart or org chart

Design Rules

• Label axes clearly with units
• Include data source
• Use a single color for most elements; highlight only what's important
• Remove gridlines unless critical for reading
• Annotations on the chart itself beat legend boxes
• Never use 3D, rainbow palettes, or decorative chart types

Context & Comparison

• Include benchmarks or prior-year data when available
• Show client how they compare to peers
• Highlight gaps or opportunities visually through color

---

Quality Checklist

Narrative & Logic

• [ ] Pyramid Principle: Key conclusion stated first; supporting points layered below
• [ ] Logical flow: Each section leads naturally to the next
• [ ] No orphan data: Every chart/statistic advances a claim
• [ ] One story: All recommendations trace back to diagnosis

Structure (MECE & Completeness)

• [ ] Findings non-overlapping and collectively exhaustive
• [ ] Recommendations prioritized (quick wins vs. strategic)
• [ ] Implementation roadmap includes dependencies and sequencing
• [ ] No gaps left unanswered (if a question arose, it's addressed)

Evidence & Fact-Base

• [ ] All claims have source citations
• [ ] Client's own data featured prominently (validates relevance)
• [ ] Benchmarks included where applicable
• [ ] Assumptions documented (especially in financial models)
• [ ] No hedging language ("possibly," "maybe," "might")

Client Readiness

• [ ] Formatting consistent (fonts, spacing, numbering)
• [ ] Jargon explained or eliminated
• [ ] Tone appropriate to client culture (formal vs. conversational)
• [ ] Length justified (concise = respected; bloated = ignored)
• [ ] Editable version delivered (never PDF-locked)

---

Narrative Arc: The Consulting Story

Structure

1. Situation: The context the client operates in (external and internal)
2. Complication: The problem or opportunity emerging from that situation
3. Resolution: What must happen (recommendation) and how (implementation)

Principles

• Situation and complication establish why the work matters now
• Every finding should resolve a piece of the complication
• Recommendations flow naturally from findings; avoid non-sequiturs
• Use analogies and concrete examples to humanize insights
• Quantify impact: "This opportunity is worth $50M annually" beats "This is significant"

Tone

• Confident in recommendations; humble about unknowns
• Authoritative without arrogance
• Active voice; strong verbs
• Client-centric language ("Your market is shifting" not "The market is shifting")

---

Workflow

1. Gather Inputs

• Existing client data, reports, prior analyses
• Interview findings and transcripts
• External data: market, benchmarks, case studies
• Competitive intelligence
• Output: Information map showing what you have, what gaps remain

2. Outline

• Draft executive summary (3-5 points)
• Map findings to recommendations (one-to-one traceability)
• Sequence logically; test narrative arc
• Deliverable: Outline for client/senior review before drafting

3. Draft Sections

• Findings first (hardest thinking; builds credibility)
• Then analysis (connects dots)
• Then recommendations (flow naturally from analysis)
• Finally, executive summary (summarize, don't re-write)

4. Review

• Internal: Fact-check, logic test, competitor sensitivity
• Client stakeholder: Accuracy of findings, tone appropriateness
• Senior consultant: Commercial viability, risk assessment
• Checklist: Use quality checklist above

5. Polish

• Copyedit; eliminate jargon and redundancy
• Ensure consistency in terminology
• Verify all page breaks, figure captions, appendix references
• Create final presentation version if needed
• Final step: Print or PDF and read aloud once; catches awkward phrasing

---

Key Principles

1. Simplify. Complex ideas deserve clear expression. Jargon clouds, not clarifies.
2. Show, don't tell. Let data and stories carry the argument.
3. Make it actionable. Generic recommendations are useless. "Improve efficiency" is not a recommendation.
4. Respect the reader's time. Every page, every section must earn its place.
5. Stand behind it. Before submission, ask: "Would I stake my reputation on this?" If no, revise.

---

Common Deliverable Pitfalls

Avoid these patterns that make deliverables land flat and undermine your credibility:

Data Dumps Without Insight

The Problem: Deliverable includes extensive tables, metrics, or research findings with no accompanying interpretation. Charts have no headlines explaining the implication.

Why It Fails: Reader is left to derive their own conclusions. Client questions: "Why are you showing me this? What should I do?" Appears like heavy lifting was shifted to the client.

Fix: For every data element, include a one-sentence takeaway. Replace "Customer satisfaction score: 72%" with "Our NPS (72) lags competitors (82), costing us an estimated 8-10% churn annually." Data earns its place only when interpretation is explicit.

Recommendations Not Tied to Findings

The Problem: Recommendations appear disconnected from findings. Client can't trace logic from diagnosis to recommendation. Feels like you generated recommendations separately from analysis.

Why It Fails: Client doubts the recommendation and questions the consulting work. "How do we know this is right?" becomes the dominant conversation.

Fix: Build explicit traceability. Reference findings in the recommendation section: "Given Finding 3 (inadequate inventory visibility), we recommend implementing [specific system]. This directly addresses the root cause identified in our analysis."

Slide Decks That Read as Documents

The Problem: Deck has 50+ slides, each with 200+ words. Paragraphs appear in text boxes. Looks like a report converted to PowerPoint.

Why It Fails: Client skips to appendix during presentation. Deck is unreadable on screen. Not usable as a standalone deck for client to cascade internally.

Fix: Apply the "one idea per slide" rule strictly. Decks for presentation: 12-15 slides max, headlines are complete thoughts, text is spartan. Create a separate "slide pack" for circulation (20-25 slides) with more detail but still visual-heavy.

Missing "So What" on Every Page

The Problem: Pages contain analysis or findings without explicitly stating business implication. Reader must infer why this matters.

Why It Fails: Senior executives skim; they lose context and stop reading. Deliverable feels academic or exploratory rather than actionable.

Fix: Add a "Business Implication" or "What This Means" box to each page. After presenting a finding, state: "This represents a $3.5M annual opportunity if addressed" or "This is a critical risk requiring board-level attention."

Inconsistent Formatting and Styling

The Problem: Fonts, spacing, colors, chart styles, and numbering vary throughout. Page layouts are inconsistent (some have headers, some don't; some are landscape, some portrait).

Why It Fails: Signals rushed or careless work. Client questions quality of underlying analysis.

Fix: Create a style guide before drafting: font (e.g., Calibri, 11pt body), colors (e.g., 3-color palette), header hierarchy (e.g., Title in 18pt bold, headers in 14pt bold), chart style (e.g., no 3D, consistent axis formatting). Apply consistently throughout. Spend 30 minutes on formatting polish before final submission.

Burying the Lead

The Problem: Most important insight or recommendation appears on page 25 rather than in the executive summary. Readers don't see the critical takeaway.

Why It Fails: If busy executives read only the executive summary, they miss the main point. Entire engagement feels unfocused.

Fix: Apply the Pyramid Principle rigidly. State your key conclusion in the executive summary and within the first 2 slides of any presentation. Build supporting logic beneath. Client should understand the main message in the first 90 seconds of reading.

---

Adapting Deliverables to Client Culture

The same recommendation landed poorly at a Fortune 500 pharmaceutical company but resonated perfectly at a PE-backed software startup. Calibrate tone, format, and depth for your client's culture and expectations.

Fortune 500 / Large Established Companies

Characteristics: Formal, risk-averse, consensus-driven, high process burden. Multiple reviewers; extensive approval cycles. Board-level audit required.

Deliverable Adaptations:

• Format: Full written reports (20-40 pages) with executive summary. Presentations are structured with formal agendas and Q&A format.
• Tone: Formal, measured, hedging language acceptable ("We believe," "Based on available data"). Risks and limitations are explicitly called out.
• Evidence Standards: Multiple sources required per major claim. Benchmarking against industry standards. Citations and methodology appendices.
• Recommendations: Prioritized by risk (quick wins separated from strategic changes). Implementation includes governance, change management, and risk mitigation plans.
• Visuals: Professional, polished, conservative color schemes. Avoid trendy or creative designs; traditional formats preferred (bar charts, line charts, org charts).
• Approval Path: Assume 3-4 rounds of review by different stakeholders. Build in buffer for feedback cycles.

Private Equity-Backed / Growth Companies

Characteristics: Fast-moving, metrics-obsessed, focused on growth and profitability. Decisions are made quickly; execution velocity is valued.

Deliverable Adaptations:

• Format: Executive summary (2-3 pages) with "financial impact" section front and center. Detailed appendices for deep dives, but keep main deck short (8-10 slides).
• Tone: Confident, direct, no hedging. Use strong verbs ("We recommend," "This will," not "might" or "could potentially").
• Evidence Standards: Focus on quantifiable impact. Benchmarking against growth/profitability peers, not industry averages. Data-driven but pragmatic (don't spend 2 weeks validating a $200K opportunity).
• Recommendations: Lead with financial impact: "This recommendation will improve EBITDA by $2M annually." Sequenced by priority and speed to implement.
• Visuals: Modern, clean, fast to scan. Numbers and charts dominate. Use one-page "tear sheets" for each recommendation showing financials, timeline, and risks.
• Approval Path: Assume 1 round of review by CFO/COO. Move to implementation quickly after approval.

Family-Owned or Founder-Led Companies

Characteristics: Relationship-oriented, values-driven, sometimes resistant to external advice. Decisions reflect owner's vision, not pure economics.

Deliverable Adaptations:

• Format: Mix of written narrative and visual presentations. Storytelling matters as much as data.
• Tone: Respectful of company history and founder vision. Frame recommendations as "strengthening" not "fixing." Acknowledge what's working before recommending changes.
• Evidence Standards: Local knowledge and company history are valued. Benchmarking is less important than understanding "why we do it our way." Include examples from similar family businesses.
• Recommendations: Connect to company values. Example: "Your founding principle of 'customer-first service' is being undermined by [issue]. We recommend [change] to restore that principle." Include people implications (owner often resists recommendations with workforce reductions).
• Visuals: Personal touch. Include photos, quotes from founder/long-time employees. Avoid overly corporate or generic designs.
• Approval Path: Assume deep conversations with founder/owner; decision-making may be slow but durable once made.

Government / Public Sector

Characteristics: Compliance-heavy, risk-averse, process-driven, accountability to multiple stakeholders. Procurement and approval rules are strict.

Deliverable Adaptations:

• Format: Detailed reports (30-50 pages) with appendices covering methodology, data sources, regulatory considerations. Presentations are formal with structured Q&A.
• Tone: Formal, objective, legally defensible. Include regulatory references and compliance citations.
• Evidence Standards: High bar for evidence. Internal government studies and audits are valued as source material. Caution is preferred to aggressive claims.
• Recommendations: Structured by compliance requirement and stakeholder impact (public, employees, leadership). Include implementation checklist with approval authorities and sign-off requirements.
• Visuals: Conservative, professional. Charts should be publication-ready. Accessibility considerations (readable by colorblind readers, large fonts for aging populations).
• Approval Path: Assume 5+ approval gates. Build in contingency for required inter-agency coordination. Prepare for public comment periods or legislative review.

---

Revision Management

Client feedback loops are inevitable. Manage them efficiently to avoid endless cycles while remaining responsive to legitimate concerns.

Version Control & Tracking

• Naming convention: Use date-based versioning (e.g., "Report_v1_Jan15" not "Report_Final_FINAL_v2").
• Change tracking: Use Word "Track Changes" feature religiously. Set clear expectations: "We'll track all edits and highlight changes for your review."
• Master version: Maintain a master "approved" version in shared folder. Clients should not edit multiple versions in parallel.
• Limit circulation: Provide draft to core approvers first (2-3 people). Once approved, circulate widely. Avoids conflicting feedback from multiple reviewers.

Handling Client Feedback

• Categorize feedback: As you receive comments, bucket them into three categories:

  • Factual corrections: Errors in data, dates, names. Implement immediately.
  • Clarification requests: Client doesn't understand a section. Rewrite for clarity.
  • Preference/style: Client prefers different color, different recommendation sequencing. Implement if client is the final approver; otherwise, push back respectfully.

• Consolidate comments: If multiple clients provide feedback, consolidate into a single "comment log." Identify conflicting feedback and escalate to project sponsor for tiebreaker decision.

When to Push Back on Client Edits

• Defend analytical integrity. If client wants to downplay a finding or soften a recommendation without supporting evidence, push back: "We believe this finding is material and should be included. If you disagree, let's discuss the evidence."
• Protect the narrative. If edits fragment the story or contradict earlier sections, flag it: "This edit conflicts with Section 3. Let's align before finalizing."
• Quality gate. If edits introduce errors or weaken logic, escalate to project sponsor: "We're concerned this change could undermine the credibility of our analysis. Can we discuss?"

How to Push Back Gracefully: "We hear you. We're committed to a deliverable you're proud of. Let's discuss the concern behind the edit—there might be a way to address it that preserves the analytical integrity."

Managing Multiple Reviewers

• Designate a single approver: Identify one person (usually project sponsor) with final sign-off authority. Others provide input but sponsor makes final calls.
• Review cycles: Announce upfront: "We'll do 2 rounds of revisions included in the fee. Additional rounds will be billed at daily rate." This prevents infinite feedback loops.
• Escalation path: If two sponsors disagree on a recommendation, facilitate a working session to resolve rather than attempting to satisfy both.
• Approval signoff: Require written approval ("This version is approved") before moving to next phase. Prevents claims later that deliverable wasn't approved.