Bulletproof Problem Solving
Charles Conn & Robert McLean · 2019
Editorial rating
- Evidence
- 8/10
- Actionability
- 9/10
- Originality
- 7/10
The thesis
Complex problems become manageable when teams define the decision precisely, break it into logical parts, prioritize the critical branches, and repeatedly connect analysis back to action.
Who this is for
Consultants, analysts, managers, founders, and public-sector leaders facing ambiguous problems where the available time, evidence, and stakeholder attention are all limited.
My favorite quote
Good problem solvers are made not born.
Why it matters
Structured problem solving is a trainable process rather than a personality trait reserved for unusually clever people.
Do this
Write one current problem as a measurable question with an outcome, deadline, decision-maker, and explicit constraints.
Start here
Do not begin with analysis. Begin with a problem statement that names the desired outcome, decision-maker, time frame, constraints, and required accuracy. Then break that question into a logic tree and prioritize the branches most likely to change the answer.
Critical summary
Charles Conn and Robert McLean distilled decades of McKinsey problem-solving experience into a seven-step process designed for business decisions, public policy, environmental challenges, and personal choices. Step one defines the problem through a precise statement of the decision, success criteria, scope, constraints, stakeholders, time frame, and required accuracy. Step two disaggregates the problem into a logic tree so a large question becomes a set of smaller, answerable questions. Step three prioritizes branches according to impact, uncertainty, and the team's ability to influence the outcome. Step four converts priorities into a workplan with owners, milestones, and hypotheses. Step five performs the analysis, beginning with simple heuristics, orders of magnitude, and summary statistics before reaching for advanced models. Step six synthesizes findings into conclusions rather than presenting disconnected outputs. Step seven communicates a storyline that links the original problem to a recommendation and action. Throughout the cycle, the authors recommend iteration, team diversity, bias checks, one-day answers, and "porpoising" between the emerging big picture and detailed evidence.
What it gets right
- Connects problem definition, analysis, synthesis, and communication instead of treating them as separate professional skills
- Uses logic trees and prioritization to prevent teams from spending equal effort on every possible branch
- Shows that simple heuristics and early hypotheses can improve speed without eliminating later analytical rigor
What it overstates or misses
- The orderly seven-step sequence understates how political incentives, weak ownership, and organizational resistance can block an analytically sound answer
- Many cases are compressed into clean teaching examples that make data access and implementation appear easier than they usually are
- Logic trees can create false confidence when a problem is dynamic, categories interact, or the important variable has not yet been imagined
The evidence comes from numerous real-world cases, consulting practice, decision science, and established analytical tools, though the book does not experimentally compare its complete method with alternatives. Its strongest claim is practical rather than scientific: teams improve when they make assumptions visible and direct scarce effort toward the questions that matter. This is the clearest general-purpose operating manual for analytical problem solving, provided you remember that a clean tree is not the same as a solved organization.
Key concepts
Problem Statement
Define the desired outcome, decision-maker, scope, constraints, deadline, and accuracy before deciding what analysis to run.
Logic Tree
Break a complex question into non-overlapping branches that expose drivers, causes, choices, or hypotheses.
Prioritization
Focus effort on branches with the greatest likely impact, uncertainty, and influence instead of analyzing everything equally.
One-Day Answer
Draft an early provisional answer and supporting logic so the team can expose gaps before investing heavily in analysis.
Porpoising
Move repeatedly between detailed evidence and the overall conclusion to keep analysis relevant as understanding changes.
Core insights
-
Framing Determines the Search Space
A vague or solution-biased problem statement can produce excellent analysis of the wrong question.
-
Disaggregation Makes Complexity Visible
A logic tree turns anxiety about a large problem into a finite set of questions that can be assigned and tested.
-
Priorities Beat Completeness
The goal is not to analyze every branch but to identify which answers could materially change the decision.
-
Simple Analysis Comes First
Rough calculations and heuristics often reveal whether a sophisticated model is necessary or merely impressive.
-
Synthesis Creates Value
Stakeholders need a coherent conclusion and action, not a tour through every spreadsheet the team produced.
Implementation steps
Today
- Rewrite one current challenge as a question containing the decision, desired outcome, deadline, and key constraints.
- Draw a first logic tree with no more than four top-level branches and mark the two branches most likely to change the answer.
This week
- Create a one-day answer for the problem, including a provisional recommendation, supporting reasons, and the evidence still missing.
- Run one short team session to challenge the framing, identify hidden assumptions, and assign owners to the priority analyses.
This month
- Use the full seven-step process on one live client or internal problem and document how the problem statement changes during the work.
- Build a reusable workplan template linking each analysis to a hypothesis, owner, deadline, output, and decision consequence.
Ongoing
- Start with simple heuristics and orders of magnitude before committing time to complex models or broad data collection.
- End every analysis by stating what the result means, what decision it changes, and what action should happen next.
Suggested 30-day practice plan
An editorial application plan created by Monolithic Vault - an interpretation of the book's ideas, not part of the original book.
- Day 1
Select a real ambiguous problem and complete a written problem statement with outcome, scope, constraints, and deadline.
- Day 3
Build a logic tree and ask two colleagues to identify overlaps, omissions, and alternative framings.
- Day 7
Prioritize the tree, create a one-day answer, and convert the critical branches into a workplan.
- Day 14
Complete the first analyses using simple heuristics before adding more advanced methods where necessary.
- Day 21
Synthesize the findings into a provisional storyline and test whether each claim answers the original problem.
- Day 30
Present the recommendation, record stakeholder objections, and update your problem-solving template with the lessons learned.
Free PDF summary
Take this analysis with you: a designed two-page field-notes sheet with the thesis, my favorite quote, the key concepts and core insights, and the full 30-day checklist. Print it or keep it - free, no signup.
Go deeper
If this analysis earned your attention, the full book goes further than any summary can. The original is always the primary source.
