| name | strategic-analysis |
| description | Apply hypothesis-driven MECE problem solving and named strategic analysis frameworks (Five Forces, PESTLE, 7S, VRIO, SWOT, Ansoff, Growth-Share Matrix, Value Chain, Business Model Canvas, Strategy Canvas, and others). Use when structuring complex problems, building issue trees, developing testable hypotheses, designing analytical workplans, applying framework-based analysis, competitive positioning, market assessment, organizational alignment review, growth strategy, or portfolio decisions. For broad or high-stakes strategic questions, apply two or more frameworks and synthesize across them. For specific, well-defined questions, one framework applied rigorously is better than two applied superficially. |
Strategic Analysis
Apply hypothesis-driven methodology and established strategic frameworks to structure complex problems, develop testable hypotheses, and guide systematic analysis to actionable recommendations. Select appropriate frameworks based on the problem, apply them rigorously with substantive reasoning, and synthesize insights across multiple lenses.
The Consulting Problem-Solving Process
Step 1: Define the Problem
Before any analysis, rigorously define the problem. Get outcome clarity and constraints upfront.
A good problem definition covers:
- The Question: What exactly are we trying to solve? State in one sentence.
- The Context: Industry dynamics, company position, timeframe, technology landscape.
- Success Criteria: What does a successful solution look like? How will we measure it? What are the constraints? What is the decision timeline?
- Out of Scope: What are we NOT solving for? What boundaries exist?
Problem framing techniques to sharpen the definition:
- Jobs-to-be-Done: What job is the client hiring this solution to do?
- Pain-Priority Matrix: Rate pain points by frequency x impact
- Is/Is Not: Clarify what the problem is and isn't
Key questions to pressure-test the definition:
- Is this the right problem to solve?
- Is the problem statement specific enough?
- Are we solving symptoms or root causes?
- What would happen if we did nothing?
- What data and analytics capabilities exist to support the analysis?
Step 2: Structure the Problem
Apply MECE decomposition (Mutually Exclusive, Collectively Exhaustive) to break the problem into non-overlapping, complete branches.
Common problem structures:
| Problem Type | Recommended Structure |
|---|
| Profitability decline | Revenue (price x volume) + Cost structure |
| Market entry | Market size x Achievable share + Entry requirements |
| Operational inefficiency | Throughput x Yield + Cycle time |
| Customer churn | Acquisition x Retention x Lifetime value |
| Growth strategy | Core business + Adjacent opportunities + Transformational bets |
| Digital transformation | Current state + Capability gaps + Technology options |
MECE in practice:
NOT MECE (overlapping):
- North America, Europe, Emerging markets, Developed markets
MECE:
- North America, Europe, Asia-Pacific, Latin America, Middle East & Africa
NOT MECE (inconsistent categories):
- Product revenue, Service revenue, License revenue, Software
MECE:
- Product revenue, Service revenue, License revenue, Other revenue
For digital businesses, consider alternative MECE cuts:
- Recurring revenue (subscriptions, SaaS), Transaction revenue (usage-based, marketplace), Professional services, Ecosystem/partner revenue
Step 3: Prioritize Issues
Not all branches deserve equal attention. Use value-effort analysis combined with hypothesis importance:
Decision criteria:
- Where is the biggest lever?
- Where is the data available?
- What will have the greatest impact?
- What is the time sensitivity?
- What can we test quickly with minimum viable analysis?
Step 4: Develop Hypotheses
Form testable hypotheses early. This focuses fact-finding and prevents boiling-the-ocean data collection.
A good hypothesis:
- Is specific and concrete
- Is testable with available data
- Implies a recommended action if proven true
- States "we believe X because Y"
- Has a quick validation path
For each hypothesis, define:
- Current belief: What we think is true
- Evidence needed: What would prove or disprove it
- Data source: Where to find the evidence
- Quick test: Fastest way to validate or invalidate
- If true, then: What we'd recommend
Step 5: Conduct Analysis
Structure analysis to test hypotheses, not to generate data for its own sake.
For each analysis workstream, define:
- Which hypothesis it tests
- The analytical method
- Data inputs required
- Expected output and what it tells us
Analytical approaches by situation:
| Situation | Recommended Analysis |
|---|
| Profit driver identification | Bridge analysis, variance analysis |
| Market sizing | Top-down, bottom-up, triangulated |
| Competitive assessment | Relative positioning, scenario analysis |
| Financial projections | Scenario modeling, sensitivity analysis |
| Process optimization | Time studies, root cause analysis, process mining |
| Customer insights | Segmentation, journey mapping, behavioral analysis |
Step 6: Synthesize Findings
Draw conclusions that answer the original question. Synthesis is not summary. It follows the structure:
- What We Learned: Findings that directly test hypotheses
- So What?: Implications of each finding
- The Answer: Direct answer to the problem question
Step 7: Develop Recommendations
Translate findings into action. Each recommendation needs:
- Rationale: Why this addresses the problem
- Impact: Expected outcome, quantified
- Effort: Resources required
- Timing: When to act
- Implementation approach: How to execute
Issue Trees
Hypothesis Tree
[Ultimate Question]
+---------------+---------------+
v v v
[Hypothesis 1] [Hypothesis 2] [Hypothesis 3]
| | |
+----+----+ +----+----+ +----+----+
v v v v v v
[Proof 1] [Proof 2] [Proof 1] [Proof 2] [Proof 1] [Proof 2]
| | |
[Quick Test] [Quick Test] [Quick Test]
Start with the ultimate question. Branch into competing hypotheses. Under each hypothesis, identify the proof points needed and the quickest way to test them.
Logic Tree
[Problem Statement]
+---------------+---------------+
v v v
[Driver A] [Driver B] [Driver C]
| |
+----+----+ +----+----+
v v v v
[Factor 1] [Factor 2] [Factor 3] [Factor 4]
| |
[Root Cause] [Root Cause]
Decompose the problem into its causal drivers. Keep branching until you reach actionable root causes.
Fact-Finding Best Practices
Data Collection
- Start with existing sources: Internal databases, published reports, prior analyses
- Validate data quality: Check for completeness, accuracy, relevance
- Triangulate: Use multiple sources to confirm findings
- Document assumptions: Note any extrapolations or estimates
Interviews
- Prepare questions: Align with hypotheses
- Listen more, talk less: 80% listen, 20% ask follow-ups
- Take notes: Capture direct quotes and observations
- Verify understanding: Summarize back to confirm
Analysis
- Show your work: Document methodology
- Check math: Verify calculations
- Test sensitivity: Understand which inputs matter most
- Consider alternatives: Stress-test conclusions
Common Problem-Solving Pitfalls
| Pitfall | Why It's Problematic | Solution |
|---|
| Defining the problem too broadly | Diffuses analysis | Narrow scope iteratively |
| Jumping to solutions | Misses root causes | Follow the process |
| Collecting all data | Wastes time | Prioritize by hypothesis |
| Confirming existing beliefs | Biases analysis | Actively seek disconfirming evidence |
| Presenting findings without recommendations | Leaves client without action | Always translate to action |
| Over-complicating the analysis | Delays insights | Apply 80/20 principle |
Framework Selection Guide
| Question | Primary Framework | Complementary Pairing |
|---|
| How attractive is our industry? | Five Forces Analysis | PESTLE, Value Chain |
| How should we compete? | Competitive Positioning | Strategy Canvas, VRIO |
| How is our organization aligned? | 7S Framework | Balanced Scorecard |
| What is our competitive advantage? | VRIO | Value Chain, Five Forces |
| How should we grow? | Ansoff Matrix | Growth-Share Matrix, Three Horizons |
| What external factors affect us? | PESTLE | Five Forces, SWOT |
| What are our strengths and weaknesses? | SWOT Analysis | PESTLE (external), VRIO (internal) |
| How should we enter a new market? | Market Entry Framework | Five Forces, PESTLE |
| What is our business model? | Business Model Canvas | Value Chain, Platform Strategy |
| How do we create value? | Value Chain | Business Model Canvas, Competitive Positioning |
| How do we measure performance? | Balanced Scorecard | 7S Framework |
| How should we allocate resources? | Growth-Share Matrix | Nine-Box, Three Horizons |
| What are our strategic options? | Strategy Canvas | Three Horizons, Ansoff Matrix |
| How do we build a platform? | Platform Strategy | Business Model Canvas, Five Forces |
External Analysis Frameworks
Five Forces Analysis
Purpose: Assess industry attractiveness and competitive intensity.
For each of the five forces (New Entrants, Buyer Power, Supplier Power, Substitutes, Competitive Rivalry):
- Rate the force as High/Medium/Low with a 1-2 sentence justification
- Create a table with columns: Factor | Assessment | Implication
- Include 4-6 factors per force, including digital/platform dimensions (network effects as entry barrier, digital switching costs, platform supplier power, digital substitutes, winner-takes-all dynamics)
- After all five forces, provide an Industry Attractiveness Summary (overall profit potential) and Strategic Implications (how to compete, where to position, how to mitigate unfavorable forces)
PESTLE Analysis
Purpose: Analyze external macro-environmental factors.
For each dimension (Political, Economic, Social, Technological, Legal, Environmental):
- Create a table with columns: Factor | Trend | Impact (H/M/L) | Timeframe (S/M/L) | Strategic Response
- Include 2-4 factors per dimension
- Conclude with Key Trends Summary: the top 3 most significant trends ranked by strategic impact
SWOT Analysis
Purpose: Assess strategic position through internal strengths/weaknesses and external opportunities/threats.
Create four tables (Strengths, Weaknesses, Opportunities, Threats) with columns: Factor | Evidence | Strategic Significance (H/M/L). Include 3-5 factors per quadrant, grounded in evidence rather than generic claims. After the four quadrants, generate a Cross-Quadrant Strategy Matrix:
- SO strategies: Use strengths to capture opportunities
- WO strategies: Address weaknesses to capture opportunities
- ST strategies: Use strengths to counter threats
- WT strategies: Mitigate weaknesses against threats
Conclude with the 2-3 highest-priority strategic actions.
Internal Analysis Frameworks
7S Framework
Purpose: Assess organizational alignment and capability.
Create two summary tables:
- Hard Elements (Strategy, Structure, Systems) with columns: Element | Current State | Target State | Gap | Priority
- Soft Elements (Shared Values, Style, Staff, Skills) with the same columns
For each of the 7 elements, provide 2-3 current-state observations and key gaps identified.
Conclude with:
- Alignment Assessment: Which elements are aligned, which have gaps, implications of misalignment
- Recommendations: 3-5 prioritized actions to close gaps
VRIO Framework
Purpose: Assess competitive advantage and resource sustainability.
Create a VRIO table with columns: Resource/Capability | Valuable? | Rare? | Costly to Imitate? | Organized to Capture? | Competitive Implication.
Map implications:
- Not Valuable = Competitive Disadvantage
- V only = Competitive Parity
- V+R = Temporary Advantage
- V+R+I+O = Sustained Advantage
Conclude with which resources provide sustained advantage, which need development, and what the imitation barriers are.
Balanced Scorecard
Purpose: Translate strategy into measurable objectives across four perspectives.
For each perspective (Financial, Customer, Internal Process, Learning & Growth), create a table with columns: Objective | Measure | Target | Initiative | Status. Include 3-4 objectives per perspective. Ensure objectives cascade logically: Learning & Growth capabilities enable Internal Process excellence, which drives Customer outcomes, which deliver Financial results.
Conclude with a Strategy Map narrative showing cause-effect linkages and identifying any broken links in the strategy logic.
Strategy Formulation Frameworks
Growth-Share Matrix
Purpose: Analyze business portfolio and resource allocation.
Create a portfolio table with columns: Business Unit | Market Growth Rate (%) | Relative Market Share | Quadrant (Star/Question Mark/Cash Cow/Dog) | Strategy (Invest/Hold/Harvest/Divest).
Conclude with Portfolio Implications (cash flow dynamics, investment requirements, rebalancing needs) and 3-4 prioritized recommendations.
Ansoff Matrix
Purpose: Analyze growth strategies across four paths.
Start with the current position (products, markets, revenue). Then create a summary table with columns: Strategy | Risk Level | Opportunity | Key Consideration.
For each of the four strategies (Market Penetration, Product Development, Market Development, Diversification), assess: approach, opportunity size, risk level, and investment required.
Conclude with Recommended Strategy: primary choice with rationale, secondary option, and investment requirements.
Nine-Box Matrix
Purpose: Multi-business portfolio prioritization.
Plot business units on a 3x3 matrix (Market Attractiveness vs. Competitive Position). Create a table with columns: Business Unit | Market Attractiveness (H/M/L) | Competitive Position (H/M/L) | Strategy (Invest/Select/Harvest/Divest). Conclude with investment allocation implications.
Three Horizons Model
Purpose: Balance short-term and long-term growth.
For each horizon, create an initiative table:
- H1 (0-12 months): Defend and grow core. Columns: Initiative | Impact | Investment | Timeline
- H2 (1-3 years): Nurture emerging businesses. Columns: Initiative | Market Size | Investment | Timeline
- H3 (3-7+ years): Create future options. Columns: Option | Potential | Risk | Investment
Conclude with Investment Allocation (% split across horizons) and Key Risks per horizon.
Competitive Strategy Frameworks
Competitive Positioning
Purpose: Define competitive positioning.
Assess current position across three dimensions (Target Scope, Cost Advantage, Differentiation). Then evaluate each generic strategy (Cost Leadership, Differentiation, Focus) covering: suitability conditions, required capabilities, and key risks.
Conclude with Recommended Strategy: chosen position, rationale, how to achieve, and how to defend.
Strategy Canvas
Purpose: Visualize competitive differentiation by comparing value curves across key factors.
Identify 6-10 factors the industry competes on (price, quality, features, service, brand, convenience, etc.). Create a table with columns: Competing Factor | Our Company (1-5) | Competitor A (1-5) | Competitor B (1-5) | Industry Average (1-5).
Identify where your curve diverges from competitors (differentiation) and where it converges (parity). Apply blue ocean logic: which factors can be eliminated, reduced, raised, or created?
Conclude with Differentiation Assessment and a recommended Target Value Curve.
Value Chain Analysis
Purpose: Understand how value is created in the business.
Create two tables:
- Primary Activities (Inbound Logistics, Operations, Outbound Logistics, Marketing & Sales, Service) with columns: Activity | Description | Value Created | Cost | Competitive Advantage (H/M/L)
- Support Activities (Procurement, Technology, HR, Infrastructure) with the same columns
Conclude with Value Chain Linkages (how activities reinforce each other), Cost Analysis, and Differentiation Sources.
Additional Frameworks
Business Model Canvas
Purpose: Map and evaluate the complete business model.
Analyze all nine building blocks in a table with columns: Block | Current State | Strengths | Vulnerabilities. The blocks: Customer Segments, Value Propositions, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partnerships, Cost Structure.
Assess how the blocks reinforce each other. Conclude with:
- Model Coherence: Where blocks align vs. conflict
- Sustainability: Which blocks are hardest for competitors to replicate
- Evolution Opportunities: Where shifts could transform the model
Market Entry Framework
Purpose: Evaluate and select market entry strategies for new geographies or segments.
Assess market attractiveness in a table with columns: Factor | Assessment | Data Source | Implication (covering market size, growth rate, competitive intensity, regulatory barriers, cultural factors).
Evaluate entry modes (organic build, acquisition, joint venture, partnership, licensing, export) in a table with columns: Entry Mode | Investment Required | Risk Level | Speed to Market | Control Level | Recommendation.
Conclude with Recommended Entry Strategy, sequencing, and key success factors.
Platform Strategy
Purpose: Assess and design platform-based business models.
Identify the platform type (marketplace, innovation platform, social platform, hybrid). Map the ecosystem with columns: Participant Type | Role | Value Created | Value Captured | Incentive to Join.
Assess network effects (same-side, cross-side, data) and their strength. Evaluate platform economics: subsidized side vs. monetized side, multi-homing risk, winner-takes-all dynamics.
Conclude with Platform Design (governance, openness, monetization), Growth Strategy (solving chicken-and-egg, building liquidity), and Defensibility.
Market and Competitive Analysis
When conducting market analysis, structure the work in layers:
Market Sizing
- Use TAM (Total Addressable Market), SAM (Serviceable Addressable Market), SOM (Serviceable Obtainable Market)
- Triangulate using both top-down and bottom-up approaches
- Distinguish between market size and addressable opportunity
- Document growth rates (historical CAGR and forecast) with drivers
Competitive Landscape
- Map competitors by market share, revenue, growth rate, and positioning
- Profile key competitors on strengths, weaknesses, strategy, and threats
- Assess competitive positioning across dimensions that matter to customers (price, quality, reach, innovation)
- Look for emerging competitors and adjacent-market entrants, not just established players
Synthesis
- Identify market opportunities with sizing, timing, and strategic fit
- Identify market threats with likelihood, impact, and mitigation
- Assess which competitive advantages are sustainable and why
- Quantify findings wherever possible. Specificity builds credibility.
Framework Synthesis
The synthesis is where the real consulting value lies. Individual frameworks provide structure, but the connections between them drive insight.
When analyzing a complex situation with multiple frameworks, structure the synthesis as:
External Landscape
- Industry attractiveness (Five Forces assessment, overall profit potential)
- Key external trends (PESTLE top 3 trends with timeline and impact)
- Competitive dynamics (where is power shifting?)
Internal Position
- Organizational alignment (7S assessment, where are the gaps?)
- Competitive advantage (VRIO assessment, what's truly sustainable?)
- Value creation (Value Chain insights, where do we win?)
Growth Options
- Current portfolio (Growth-Share assessment)
- Growth strategy (Ansoff recommendation with risk-adjusted view)
- Future pipeline (Three Horizons view, are we investing enough in H2/H3?)
Cross-Framework Synthesis
- Converging findings: Where 2+ frameworks agree (high confidence insights)
- Contradictions: Where frameworks disagree (requires judgment call, often reveals the most important insight)
- Blind spots: What none of the frameworks capture (qualitative factors, culture, timing)
- Highest-leverage insight: The single most important finding across all analyses
Implementation Priorities
- Phase 1 (0-6 months): Quick wins that build momentum and prove the thesis
- Phase 2 (6-18 months): Medium-term capability building
- Phase 3 (18+ months): Long-term strategic positioning
Key Principles
- The hypothesis-driven approach saves time by focusing fact-finding
- MECE problem trees are reusable. Build a library of common decompositions
- Always return to the original question. Don't let analysis drift
- Recommendations must be actionable. Vague advice helps no one
- Quality of problem definition determines quality of solution
- Iterate, validate, adapt. The first structure is rarely the final one
- For broad or high-stakes strategic questions, apply at least 2 frameworks and synthesize across them. For specific, well-defined questions, one framework applied rigorously is better than two applied superficially
- Provide substantive analysis, not empty templates. For each cell, give 2-3 sentences of reasoning with evidence
- Quantify wherever possible. "High" is less useful than "High... represents ~$15M revenue risk."
- Synthesize across frameworks. Call out where frameworks agree, disagree, and what none of them capture
- Customize to context. Adapt framework dimensions to the specific industry and situation
- When frameworks conflict, explore the contradiction. It often reveals the most important insight
