Problem framing, analytics, and cadence vs. over‑templating and survivor bias.
Strategy consulting has supplied leaders with methods that clarify choices and impose discipline on execution. It has also propagated shortcuts that, when unexamined, obscure causality and encourage ritual. This chapter separates the enduring contributions—problem framing, analytics, and cadence—from the frequent errors—over‑templating, survivor bias, and related distortions. The aim is practical: to help organizations extract the signal while rejecting the noise.
I. What Consultants Get Right
1) Problem framing: from vague ambition to testable choices
The most reliable value consultants provide is structure. Good teams begin by restating a client’s broad ask (“grow faster,” “enter Asia,” “improve margins”) as a focal decision with explicit alternatives and criteria. Core elements:
Reframing and scoping. Clarify the unit of analysis (business, market, product, geography) and the degrees of freedom (price, channel, footprint, M&A). Identify constraints (regulation, balance sheet, brand promises).
Issue trees and hypotheses. Break the question into mutually exclusive, collectively exhaustive branches; attach hypotheses to each branch, which can be tested or refuted.
Decision early. Draft a provisional answer upfront to guide data collection and avoid aimless analysis. The provisional answer is a stake to be tested, not a conclusion.
This approach reduces ambiguity, defines what would change the decision, and shortens time to learning.
2) Analytics: disciplined comparison and unit economics
Consultants have normalized comparative analysis and the translation of strategy into unit economics (see Chapter 22). The strengths include:
External orientation. Benchmarking peers and substitutes; mapping industry structure; quantifying bargaining power and cost positions.
Economic logic. Linking choices to contribution margins, payback, and ROIC rather than to accounting artifacts.
Scenario thinking. Expressing uncertainty in ranges and exploring how alternative futures affect economics.
Decision hygiene. Making assumptions explicit; tracing every recommendation to a number that can be recalculated.
Analytics at this level substitute measurable claims for opinion and enable post‑decision review.
3) Cadence: a drumbeat of decisions and implementation
Consultants are effective at creating a rhythm that forces convergence: a calendar of milestones, routines for surfacing impediments, ownership for actions, and visible metrics. The best engagements leave behind:
A meeting architecture that mirrors time horizons (annual vector‑setting; quarterly portfolio reviews; monthly operating reviews).
Clear decision rights for recurrent choices (pricing, capital approval, vendor selection).
A portfolio discipline: stage gates, kill rules, and reallocation (Chapters 20–21).
Cadence turns analysis into allocation, preventing the “we’ll decide next quarter” drift that erodes strategy.
II. Where Consultants Go Wrong
1) Over‑templating: when the framework uses you
Frameworks are scaffolds, not answers. Over‑templating occurs when teams apply tools because they are available, not because the economics demand them.
Form over mechanism. Forcing a two‑by‑two on a problem whose drivers are continuous or multi‑dimensional; assuming portfolio matrices reveal capital priorities when interdependencies dominate.
Category myopia. Treating SIC/NAICS segmentations as strategic truth; ignoring jobs‑to‑be‑done, occasions, or ecosystem roles.
Template drift. Recycling exhibits and workplans from superficially similar situations without re‑deriving causal logic.
The correction is to begin with the specific mechanism of advantage in the client’s context (scale curve, learning, network effects, switching costs, regulatory bottlenecks) and to select tools that interrogate that mechanism.
2) Survivor bias: mistaking patterns in winners for proven causes
“Best practices” often reflect what successful firms did, not what made them succeed. Pitfalls include:
Selective samples. Studying only winners (or a skewed set of survivors) and drawing causal conclusions; ignoring failures that used the same practices.
Reverse causality. Attributing success to a practice that was a consequence of advantage (e.g., high NPS in firms that already have dominant economics).
Context blindness. Exporting a practice from a firm whose moat (regulation, scarcity, network position) cannot be replicated.
The proper antidote is causal discipline: natural experiments, difference‑in‑differences where applicable, triangulation with negative cases, and explicit priors. When causal identification is impossible, recommendations should be framed as hypotheses with tests and leading indicators.
3) False precision and spreadsheet theater
Sophisticated models can camouflage weak logic. Typical signs:
Thin data, thick decimals. Forecasts to basis points with scant historical evidence; neglect of error bands.
Averages that hide distributions. Using means where heavy tails dominate; ignoring cohort dynamics in subscription businesses.
One scenario presented as fact. Budget decks with point estimates, no ranges, and no options (Chapter 23).
The countermeasure is to present ranges, sensitivity, and decision thresholds with clear triggers. Precision should track the quality of information, not presentation standards.
4) Implementation displacement
When consultants run the PMO indefinitely, the client’s managers can become dependent on external coordination. Additionally:
Shadow governance. Real decisions migrate to off‑calendar steering meetings chaired by consultants; line ownership weakens.
Template compliance over outcomes. RAG dashboards and “on track” status reports that mask the absence of material choices.
The mitigation is to design for capability transfer: time‑boxed PMO support, internal leads from day one, and explicit “sunset” criteria tied to decision competence, not deck completion.
5) Incentive misalignment
Fee structures can create principal–agent tensions:
Time and materials bias. Subtle incentives to expand scope or prolong analysis.
Success fees without causality. Paying for outcomes driven primarily by exogenous factors (market cycles) or by client action independent of advice.
Better practice links fees to deliverables and capability build (e.g., decision frameworks, data pipelines, team training) and reserves outcome‑based elements for situations where the adviser’s contribution is identifiable and material.
III. Problem Framing: What “Good” Looks Like
A robust framing process often determines whether an engagement creates durable value. The elements:
Re‑state the decision. Translate ambition into a choice with mutually exclusive options.
Specify the mechanism. For each option, write a few sentences on how it creates advantage. Choose the lens (positioning, RBV, game theory, ecosystems, complexity) that fits the mechanism (Parts III–IV).
Define degrees of freedom. Identify what can be changed within horizon (price levels, channel mix, service levels, capital envelope) and what is fixed (debt covenants, regulatory constraints).
Name disconfirming evidence. For each hypothesis, ask what would prove it wrong. Commit to search for that evidence early.
Bound the value of information. Estimate what a given analysis could change (a pricing study that could shift margins by X; a regulatory probe that could eliminate an option). Avoid analyses whose results will not change allocation.
This discipline prevents analysis tourism and aligns effort with decisions.
Common framing failures—and fixes
Treating symptoms as problems. “Our growth is slow” is a symptom; the problem may be weak segment fit, channel conflict, or capacity constraints. Fix: ladder from symptoms to causal theories; test spanning trees with data.
Boundary error. Ignoring substitutes or complements; optimizing the firm while the ecosystem shifts. Fix: include substitutes, complements, and standards in the initial map.
Over‑breadth. Framing a multi‑year transformation in one sweep. Fix: decompose into sequenced choices with option gates.
IV. Analytics: From Benchmarking to Causality
1) Benchmarks as priors
Benchmarks set reasonable ranges and reveal outliers worth explaining. They are starting points, not verdicts. Effective use:
Clarify comparability (mix, scale, accounting policies).
Show dispersion, not only averages.
Pair with hypotheses about why differences exist (process, model, position).
2) Unit economics and cohorts
The most robust analyses descend to units and cohorts:
For subscriptions: retention curves, expansion paths, LTV/CAC by cohort; payback windows; marginal CAC by channel.
For retail/CPG: basket analysis, price elasticity by segment and occasion; promotion ROI with cannibalization; contribution by store archetype.
For manufacturing: yield curves, learning rates, downtime drivers; cost‑to‑serve by SKU and channel.
These analyses connect directly to resource allocation and can be re‑run post‑decision.
3) Causal inference where possible
Move beyond correlation:
Quasi‑experiments (before–after with controls; difference‑in‑differences).
Instrumental variables or regression discontinuities where natural thresholds exist.
A/B tests in digital channels; pilot geographies in physical contexts.
When causal identification is infeasible, be explicit: “Based on pattern and mechanism plausibility, we recommend a probe with thresholds,” not “The model proves X.”
4) Measurement hygiene
Document data lineage and definitions; publish a data dictionary for key metrics.
Report confidence intervals and sensitivity; show what happens under alternative reasonable assumptions.
Avoid composite indices that conceal trade‑offs; show the underlying components.
V. Cadence: Routines That Convert Analysis into Action
A consulting team’s timebox can galvanize an organization. The value persists only if those rhythms are institutionalized.
Elements of a durable cadence
Quarterly portfolio reviews: assess option portfolios, move bets up or down stages, and reallocate funds (Chapter 21).
Monthly operating reviews: focus on driver metrics and blockers; resolve cross‑team issues.
Decision logs: record choices, thresholds, and review dates; enable post‑decision learning.
Owner directories: publish who owns each critical decision or process.
Stop lists: make exits visible each quarter to normalize pruning.
Cadence failure modes
Ritual without authority. Meetings that cannot move resources or change policies. Remedy: pre‑delegated authority and defined envelopes.
Metric theater. Dashboards with no default actions. Remedy: pair each metric with a threshold and response.
Consultant‑dependent muscle. Rhythm collapses after exit. Remedy: internal chairs, documented playbooks, and training before handover.
VI. Recognizing Context: When Advice Travels—and When It Doesn’t
A central error is assuming transferability without adjustment.
Capital‑intensive vs. asset‑light. Learning curves and capacity economics dominate in one; network effects or distribution access in the other. Tools shift accordingly.
Regulated vs. discretionary demand. Strategy is often license management where political/regulatory forces dominate; analyses must include stakeholder coalitions and policy sequencing.
Ecosystem vs. pipeline models. Pricing and governance are central on platforms; portfolio matrices for stand‑alone businesses mislead.
The remedy is a context fit check at the outset: identify decisive constraints and choose lenses (Parts III–IV) accordingly.
VII. Being a Smart Client: Extracting Value, Avoiding Traps
Leaders can tilt engagements toward value with a handful of practices.
Write the one‑page charter. State the decision to be informed, options to compare, constraints, desired artifacts (e.g., unit‑economics model, decision map), and the adoption plan.
Demand mechanisms. Insist that recommendations articulate the causal path (how exactly will margin expand?) and the evidence.
Time‑box and gate. Approve work in stages; require go/stop/pivot recommendations with each tranche; avoid multi‑month “analysis cruises.”
Co‑own the analytics. Put internal analysts on the team; require reproducible models; retain data and code.
Design for transfer. Define the leave‑behind (playbooks, decision rights, dashboards) and who will own them.
Set red teams. Assign internal challengers to test the external team’s assumptions and survivorship risks.
Align incentives. Tie fees to milestones and capability transfer; use outcome components only where causal contribution is clear.
Plan the exit. Specify who takes over cadence and PMO; set a “no‑consultant” checkpoint to test self‑sufficiency.
VIII. Case Patterns: Signals of Quality and Red Flags
Signals of quality
The first week produces a decision map and a unit‑economics scaffold.
The team names disconfirming evidence it is seeking and shows how a finding would change the recommendation.
Benchmarks are used as ranges, not as commands; negative cases are discussed.
The client’s line leaders present at synthesis meetings; recommendations are tied to allocation and decision rights.
The leave‑behind includes models, data dictionaries, and owner assignments.
Red flags
Workstreams mirror past decks more than current context; heavy recycling of exhibits.
Causal claims rest on winner narratives and stylized facts; failures never appear.
“One slide says it all” claims without sensitivity, ranges, or error bars.
PMO replaces line leadership; decisions are deferred to the next “steerco.”
Recommendations lack stop conditions and triggers; everything is “phase two.”
IX. Ethics, Legitimacy, and the Boundaries of Advice
The strategy industry sits in a trust economy. Missteps erode legitimacy:
Conflicts of interest. Serving rivals or regulators in ways that impair independence; unclear disclosure.
Data governance. Using client data to benchmark others without consent; sloppy anonymization.
Public consequences. Recommendations with significant social externalities (labor impacts, privacy) made without due consideration.
Professionalization implies not only method but norms: informed consent for data use, conflict walls, and attention to responsible strategy (safety, sustainability, compliance) as part of advantage, not as afterthought.
X. Integrating Consultants into the Strategy Operating System
Consultants create the most value when embedded in a clear operating model (Part V):
Use them to stand up the cadence, prototype decision frameworks, and build economic models.
Keep ownership of choices and metrics; ensure line managers, not consultants, deliver the narrative to the board.
Arrange engagements so that internal capability crosses the learning curve before consultants exit.
In short, position consulting as a sparring partner and capacity accelerator, not as a substitute for leadership.
