AboutHow we built thisSponsorshipShop
SearchSubscribeDecision ToolsBusiness ModelsFrameworksReading Lists
Privacy PolicyTerms of UseCookie PolicyRefund PolicyAccessibilityDisclaimer

© 2026 Faster Than Normal. All rights reserved.

Faster Than Normal
DecisionsPeopleBusinessesNewsletterSubscribe
Start reading →
  1. Home
  2. Decision tools
  3. First Principles Thinking
Finding Root Causes

First Principles Thinking

Strip away assumptions and inherited wisdom to rebuild understanding from fundamental truths

Complexity
Time required60+ min
Tool #012Origin: Aristotle / popularised by Elon Musk25 min read

On this page

  • What This Tool Does
  • How to Use It — Step by Step
  • When It Works Best
  • When It Breaks Down
  • Visual Explanation
  • Pairs With
  • Real-World Application
  • Analyst's Take
  • Top Resources

Contents

  1. 1. What This Tool Does
  2. 2. How to Use It — Step by Step
  3. 3. When It Works Best
  4. 4. When It Breaks Down
  5. 5. Visual Explanation
  6. 6. Pairs With
  7. 7. Real-World Application
  8. 8. Analyst's Take
  9. 9. Top Resources
Use this when the conventional answer feels expensive, slow, or wrong — and you suspect the entire framing might be inherited rather than earned. First principles thinking strips a problem down to its foundational truths, discards every assumption layered on top, and rebuilds a solution from the ground up. It is the difference between optimising within a paradigm and questioning whether the paradigm should exist at all.
Section 1

What This Tool Does

Most decisions are made by analogy. You look at what others have done, adjust slightly for your context, and proceed. This is efficient. It is also the mechanism by which entire industries remain stuck in suboptimal equilibria for decades. Airlines priced tickets the way other airlines priced tickets. Banks structured loans the way other banks structured loans. Rocket companies bought rockets the way other rocket companies bought rockets — from established suppliers, at established prices, with established margins baked in. Analogy is fast because it borrows the thinking someone else already did. The problem is that the someone else may have been wrong, or operating under constraints that no longer apply, or optimising for objectives that aren't yours.
Aristotle called it "first principles" — the foundational propositions that cannot be deduced from any other proposition. In Metaphysics, he described them as the "first basis from which a thing is known." The concept sat in philosophy departments for two millennia, occasionally surfacing in scientific method, until Elon Musk dragged it into mainstream business discourse around 2012 by explaining how SpaceX approached rocket costs. The aerospace industry's consensus was that rockets cost what they cost — somewhere north of $60 million for a launch. Musk's team asked a different question: what are rockets actually made of? Aluminium alloys, titanium, copper, carbon fibre. What do those raw materials cost on the commodity market? Roughly 2% of the finished rocket price. The remaining 98% was design choices, manufacturing processes, supplier margins, and institutional inertia — all of which could be challenged. That gap between material cost and market price was the space where first principles thinking operates.
The tool works by forcing a specific cognitive sequence. First, identify your current assumptions about a problem. Second, break the problem down until you reach fundamental truths — things that are empirically true regardless of convention. Third, reason upward from those truths to construct a new solution. The core insight is that most "constraints" are actually conventions — and the difference between the two is the entire margin of innovation. A constraint is physics: you cannot make a rocket lighter than its fuel. A convention is procurement practice: you must buy engines from one of three established suppliers. First principles thinking is the discipline of telling them apart.
This sounds straightforward. It is not. The difficulty is psychological, not intellectual. Conventions feel like constraints because everyone around you treats them as such. Your industry, your board, your investors, your own experience — all reinforce the existing frame. Reasoning from first principles requires you to temporarily disbelieve the collective wisdom of your field, which feels arrogant and is socially expensive. The people who do it successfully aren't smarter than their peers. They're more willing to be wrong in public and more disciplined about distinguishing what they know from what they assume.
Section 2

How to Use It — Step by Step

Instructions on the left. Worked example — "Should our DTC food brand build its own last-mile delivery network or continue using third-party logistics?" — on the right.
Step 1 — Identify

Surface every assumption embedded in the current approach

Write down how the problem is currently framed and what everyone "knows" to be true. Be exhaustive. Include industry norms, internal beliefs, supplier claims, and anything prefaced with "that's just how it works." These are your assumption inventory. Don't evaluate them yet — just catalogue. The goal is to make the invisible visible. Most teams are shocked by how many unexamined beliefs underpin their current strategy.
Worked example

DTC food delivery assumptions

The team lists: (1) Last-mile delivery requires a fleet of refrigerated vehicles. (2) Third-party logistics providers are cheaper because of scale. (3) Customers expect delivery within 2 days. (4) Cold chain integrity requires specialised infrastructure we can't build. (5) Our order density is too low to justify owned logistics. (6) Delivery is a cost centre, never a differentiator. (7) We'd need to hire 50+ drivers to cover our metro areas. Seven assumptions, all treated as facts. None have been tested.
Step 2 — Deconstruct

Break each assumption down to its fundamental truth

For every assumption, ask: "Is this a law of physics, a proven empirical fact, or a convention?" If it's a convention, ask what the underlying truth actually is. Keep decomposing until you hit bedrock — something measurable, testable, and true regardless of what your competitors do. This is the hardest step. Your brain will resist. It will insist that the assumption is the fundamental truth. Push through. Use "What do I know for certain?" as your filter.
Worked example

Decomposing assumption #2: 3PLs are cheaper at scale

Fundamental truth: transportation cost is a function of distance, weight, vehicle utilisation, and labour rate. That's physics and economics. The convention is that 3PLs achieve better utilisation because they aggregate multiple shippers. But is that true for our specific routes? The team pulls data: their 3PL's trucks run at 40% capacity on their routes because the 3PL optimises for its largest clients first. The "scale advantage" is real in aggregate but doesn't apply to this brand's delivery pattern. Fundamental truth ≠ industry assumption.
Step 3 — Establish

Define the irreducible truths that survive deconstruction

Write a clean list of what remains after you've stripped away conventions. These are your first principles — the non-negotiable realities you must design around. They should be specific and falsifiable. "Customers want fast delivery" is too vague. "Our customers in the three core metros place 85% of orders within a 12-mile radius of our fulfilment centre" is a first principle you can build on.
Worked example

First principles for the delivery decision

(1) 85% of orders ship within a 12-mile radius. (2) Product must stay below 40°F for a maximum of 4 hours in transit. (3) Current 3PL cost is $11.40 per delivery, of which ~$3.80 is the 3PL's margin and overhead. (4) Average order value is $62, making delivery 18.4% of revenue. (5) Customers who receive delivery within 24 hours reorder at 2.1× the rate of 48-hour recipients. (6) Insulated packaging maintains temperature for 6 hours without active refrigeration. Five truths. No opinions. No conventions.
Step 4 — Reconstruct

Build a new solution upward from the first principles only

Forget the existing options. Don't choose between "build fleet" and "keep 3PL." Instead, design the optimal solution that satisfies your first principles at the lowest cost or highest value. Let the principles dictate the architecture. The solution that emerges may not resemble either of the options you started with — and that's the point. You're not choosing between doors. You're building a new door.
Worked example

A solution nobody proposed

The first principles reveal that active refrigeration in transit is unnecessary (insulated packaging handles 6 hours; deliveries are under 90 minutes). The 12-mile radius means bicycle couriers or compact EVs, not refrigerated trucks. The 24-hour reorder multiplier means delivery speed is a revenue driver, not a cost centre. The reconstructed solution: a network of 8 gig-economy couriers using insulated bags on e-bikes, dispatched from the existing fulfilment centre, delivering within 3 hours of order placement. Projected cost: $5.20 per delivery — 54% less than the 3PL — with same-day speed that the 3PL cannot match. This option wasn't on the original decision menu. First principles created it.
Step 5 — Stress-Test

Validate the reconstructed solution against reality

First principles reasoning can produce elegant solutions that fail on contact with operational reality. Before committing, identify the assumptions within your new solution and test them. Run a pilot. Build a prototype. Talk to the people who would execute it. The reconstruction is a hypothesis — a better-informed hypothesis than the conventional approach, but a hypothesis nonetheless. Treat it accordingly.
Worked example

Pilot before commitment

The team runs a 4-week pilot in one metro with 3 couriers. Results: average delivery time is 2.4 hours, cost per delivery is $5.80 (slightly above projection due to idle time between orders), and reorder rate among pilot customers jumps 34%. Temperature logs confirm product stays below 40°F. The model works but needs order density above 15 deliveries per courier per day to hit the $5.20 target. The team now has a validated first-principles solution with a clear scaling threshold — a far better decision basis than the original binary choice.
Section 3

When It Works Best

✓

Ideal Conditions for First Principles Thinking

DimensionBest fit
Problem typeProblems where the conventional solution is expensive, slow, or produces mediocre results — and where you suspect the constraints are inherited rather than real. Cost structures that "everyone knows" can't be changed. Markets where all competitors have converged on the same approach. Any situation where the question "why do we do it this way?" is answered with "because that's how it's done."
Stakes and reversibilityHighest value on irreversible, high-stakes decisions where the cost of following convention is measured in years and millions. Choosing a manufacturing approach, designing a business model, entering a market. The cognitive overhead of first principles reasoning isn't justified for routine operational choices — save it for decisions that lock in architecture.
Knowledge availabilityYou need access to the fundamental data — material costs, physics constraints, customer behaviour metrics, unit economics. First principles thinking without empirical grounding is just speculation with extra steps. The method works when you can actually verify what's true at the foundational level, not merely assert it.
Competitive contextMost powerful in industries with high conformity — where incumbents have optimised within a shared paradigm for so long that the paradigm itself has become invisible. The more uniform the competitive landscape, the larger the potential gap between convention and fundamental truth.
Organisational cultureRequires a team (or at minimum a decision-maker) willing to tolerate the social cost of questioning industry wisdom. First principles conclusions often sound naive or arrogant to domain experts. If your organisation punishes unconventional thinking or requires consensus before action, the tool will be neutralised by the culture before it produces results.
Time horizonThe payoff is typically medium-to-long term. Rebuilding from fundamentals takes longer than copying a competitor. But the solutions tend to be structurally superior — harder to replicate, better unit economics, more defensible positioning. First principles thinking trades speed of decision for quality of outcome.
Section 4

When It Breaks Down

⚠

Failure Modes

Failure patternWhat goes wrongWhat to use instead
False fundamentalsThe thinker mistakes a deeply held belief for a first principle. "People won't pay more than $X for Y" feels like bedrock but is actually a market convention that changes with context, framing, and value delivery. If your "fundamental truths" include any claim about human preferences or market behaviour, they're probably assumptions in disguise.Ladder of Inference to trace beliefs back to their evidential source; validate with data before treating as foundational
Ignoring accumulated wisdomConventions exist for reasons. Many encode hard-won lessons from failures you haven't experienced yet. First principles thinking that dismisses all industry practice as "mere convention" is as dangerous as blindly following it. The pharmaceutical industry's clinical trial protocols aren't arbitrary — they encode decades of lethal mistakes. Stripping them away from "first principles" would be catastrophic.Second-Order Thinking to model the downstream consequences of discarding established practices
Analysis paralysis from infinite decompositionEvery assumption can be decomposed further. Materials are made of molecules. Molecules are made of atoms. At some point you have to stop decomposing and start building. Teams without a clear stopping rule can spend months in the deconstruction phase, producing elegant analyses and zero decisions.Set a time-box; use Confidence Determines Speed vs Quality to calibrate depth of analysis to decision stakes
Solo genius syndromeFirst principles thinking is often romanticised as the province of lone visionaries — Musk, Jobs, Bezos. This framing encourages founders to dismiss expert input as "conventional thinking" and trust their own decomposition, even when they lack the domain knowledge to identify true fundamentals. Confidence without competence, dressed up as rigour.Delphi Method to incorporate expert knowledge; Six Thinking Hats to ensure critical perspectives aren't suppressed
Misapplication to social/political problemsFirst principles thinking assumes that problems have objective, decomposable truths at their base. Many important decisions — organisational culture, stakeholder negotiations, brand positioning — are fundamentally social. There is no "physics" of human motivation. Treating subjective, context-dependent realities as if they can be reduced to axioms produces solutions that are technically elegant and humanly tone-deaf.Cynefin Framework to classify the problem domain; Reframing to explore alternative problem definitions
Survivorship bias in exemplarsWe hear about first principles thinking when it works spectacularly (SpaceX, Tesla). We don't hear about the hundreds of founders who "reasoned from first principles," ignored industry wisdom, and failed because the conventions they discarded were load-bearing. The method's track record is far less clean than its mythology suggests.Pre-Mortem to imagine how the first-principles solution could fail; Inversion to identify what you might be dangerously wrong about
The most dangerous failure mode is false fundamentals — and it's dangerous precisely because it's invisible from the inside. When you believe you've reached bedrock, you stop digging. If what you've actually reached is a deeply embedded assumption that feels like a truth, your entire reconstruction sits on a false foundation. The classic tell: your "first principle" is a generalisation about human behaviour or market dynamics rather than a measurable physical or economic fact. "People want convenience" is not a first principle. "Our average customer lives 8.3 miles from our fulfilment centre and places 2.4 orders per month" is. The protection is simple but uncomfortable: have someone outside your team — ideally someone with deep domain expertise — challenge every item on your first principles list. If they can provide a counterexample, it's not a first principle. It's a hypothesis.
Section 5

Visual Explanation

ASSUMPTIONSFIRST PRINCIPLESRECONSTRUCTION"Need refrigerated trucks"Convention — not physics"3PLs are cheaper at scale"Convention — not true for our routes"Customers expect 2-day delivery"Convention — faster is better"Need 50+ drivers for coverage"Convention — assumes truck model"Delivery is a cost centre"Convention — data says otherwiseInsulated packaging holds <40°Ffor 6 hours — no active cooling needed3PL trucks run 40% capacity on our routes$11.40/delivery — $3.80 is margin/overhead85% of orders within 12-mile radiusShort distances — light vehicles viable24-hr delivery → 2.1× reorder rateSpeed is a revenue driver, not a costAOV $62 — delivery is 18.4% of revenueHalving delivery cost adds ~$3.10 margin/orderNEW SOLUTION8 gig-economy e-bike couriersInsulated bags, no refrigerated fleetSame-day delivery (avg 2.4 hrs)vs. 48-hour 3PL standard$5.20/delivery (target)54% reduction from $11.40+34% reorder rate in pilotDelivery as growth leverThe solution that emerged was not on the original decision menu.First principles didn't choose between "build fleet" and "keep 3PL" — it created a third optionthat was cheaper, faster, and revenue-positive.STRIPGROUNDBUILD
First principles thinking applied to the DTC delivery decision — from inherited assumptions through deconstruction to reconstructed solution.
Section 6

Pairs With

First principles thinking is a reasoning method, not a complete decision system. It tells you how to think about a problem. It doesn't tell you which problems deserve this level of effort, and it doesn't protect you from the blind spots inherent in building from scratch.
Use before
Reframing
Before you decompose a problem into first principles, make sure you're decomposing the right problem. Reframing challenges the problem statement itself — which is, in a sense, the zeroth first principle. If you're asking "how do we reduce delivery costs?" when the real question is "how do we increase order frequency?", even perfect first-principles reasoning will optimise the wrong variable.
Use before
Reversible vs. Irreversible Decisions
First principles thinking is expensive — cognitively, temporally, socially. Don't deploy it on reversible decisions where the cost of being wrong is low. Use the reversibility filter first. If you can easily undo the decision, reasoning by analogy is fine. Save first principles for the architectural choices that lock in for years.
Use after
Pre-Mortem
Your reconstructed solution feels elegant. It emerged from fundamentals. It's probably better than the conventional approach. It might also fail in ways you haven't imagined because you lack the pattern recognition that comes from operating within the convention you just discarded. A pre-mortem forces you to imagine the failure before you commit.
Use after
Second-Order Thinking
First principles reasoning tends to produce direct, mechanistic solutions. Second-order thinking asks what happens after the solution works. You built a cheaper delivery network — great. What happens when competitors copy it? When couriers demand higher pay? When order volume exceeds courier capacity? The reconstruction is step one. Second-order thinking is step two.
Mental model
Inversion
Inversion is first principles thinking's natural complement. Instead of asking "what's fundamentally true about this problem?", ask "what would guarantee failure?" The answers often reveal assumptions you didn't know you were making — the ones so deep they didn't show up in your assumption inventory because you couldn't see them.
Mental model
[Abstraction](/mental-models/abstraction) Laddering
Abstraction laddering moves between "why" (going up to purpose) and "how" (going down to implementation). First principles thinking is essentially a disciplined descent down the abstraction ladder — from convention to mechanism to fundamental truth. Using both tools together ensures you're decomposing at the right level and not stopping too early.
Section 7

Real-World Application

SpaceX — rethinking rocket economics from raw materials up

The scenario
In 2002, Elon Musk wanted to buy a refurbished ICBM from Russia to launch a small payload to Mars as a publicity stunt for space exploration. The Russians quoted him $8 million per rocket. On the flight home from Moscow — reportedly furious — Musk opened a spreadsheet and started listing the raw materials in a rocket: aerospace-grade aluminium alloys, titanium, copper, carbon fibre composites, RP-1 kerosene fuel. He calculated the commodity cost of those materials. It came to roughly 2% of the price of a typical orbital rocket. The question shifted from "where can I buy a cheaper rocket?" to "why does a rocket cost 50 times its material inputs?"
How the tool applied
Musk and his early team — including Tom Mueller, who had designed the TR-106 engine at TRW — decomposed every major cost driver in rocket manufacturing. The conventional aerospace supply chain involved layers of subcontractors, each adding margin, each building to military specifications that often exceeded what commercial spaceflight required. Engines were the most expensive component, and the industry's assumption was that rocket engines required exotic manufacturing processes available only from a handful of suppliers. The first principle: an engine is a combustion chamber, a turbopump, injectors, and a nozzle. The physics of combustion and thrust are well understood. The question was whether those components could be manufactured in-house, using modern techniques, at a fraction of the subcontractor price. SpaceX chose vertical integration — building roughly 80% of the Falcon 1 (and later Falcon 9) in-house, including the Merlin engines. They used friction stir welding instead of traditional aerospace welding. They used commodity-grade alloys where military specifications weren't structurally necessary. They designed for manufacturing simplicity rather than theoretical performance optimisation.
What it surfaced
The decomposition revealed that the majority of rocket cost was not driven by physics or materials but by procurement structure, specification inheritance, and risk-averse institutional culture. NASA and the Department of Defense had spent decades building a supply chain optimised for reliability at any cost — appropriate for their missions, but not the only viable approach. SpaceX's Falcon 9 eventually achieved a launch cost of approximately $2,720 per kilogram to low Earth orbit, compared to roughly $54,500 per kilogram for the Space Shuttle. The reusable first stage — itself a first-principles insight (why throw away a $30 million booster after one use when aircraft don't discard their fuselage after each flight?) — reduced costs further.
The non-obvious factor
What's often missed in the SpaceX narrative is that first principles thinking didn't eliminate risk — it relocated it. By vertically integrating and rejecting established supplier relationships, SpaceX took on enormous execution risk. The first three Falcon 1 launches failed. The company came within weeks of bankruptcy in 2008. The conventional approach — buying proven components from proven suppliers — existed because it reduced the probability of catastrophic failure. Musk's first-principles reconstruction accepted a higher failure rate in exchange for a fundamentally different cost structure. That trade-off is the part most imitators miss. First principles thinking doesn't just change what you build. It changes what risks you're willing to absorb. And the willingness to absorb those risks — financially, reputationally, personally — is not a thinking technique. It's a temperamental trait that the tool itself cannot provide.
Section 8

Analyst's Take

Faster Than Normal — Editorial View
First principles thinking is the most mythologised decision tool in the founder ecosystem, and the mythology is the problem. It has been reduced to a motivational slogan — "think from first principles!" — that strips away the actual difficulty of the method and replaces it with a vague injunction to be contrarian. The tool endures not because it's trendy but because the cognitive bias it corrects — anchoring to convention — is genuinely pervasive and genuinely costly. Every industry has load-bearing assumptions that stopped being true years ago. The value of first principles thinking is in identifying those specific assumptions, not in a generalised posture of questioning everything. The founders who use this tool well are surgical. They identify one or two conventions that are demonstrably disconnected from physical or economic reality, and they rebuild around that specific gap. The founders who use it badly question everything, rebuild nothing, and mistake contrarianism for insight.
The failure mode I see most often: founders who invoke "first principles" to justify ignoring domain expertise. They've read the SpaceX story, they've internalised the narrative of the lone genius who sees what the experts can't, and they use "I'm reasoning from first principles" as a shield against feedback. The tell is always the same — their "first principles" are suspiciously aligned with what they already wanted to do. Real first principles reasoning is uncomfortable. It frequently leads you to conclusions you don't like, because fundamental truths don't care about your preferences. If your first-principles analysis conveniently confirms your prior strategy, you probably haven't done it.
The highest-leverage modification: pair every first principle with its source of evidence. Don't just list "insulated packaging holds temperature for 6 hours." Write down how you know that — the test you ran, the data sheet you verified, the experiment you conducted. This single discipline eliminates false fundamentals, which are the tool's most dangerous failure mode. It also forces you to distinguish between principles you've validated and principles you've assumed. The ratio between those two categories tells you how much confidence your reconstruction deserves. In my experience, teams that enforce this evidence requirement cut their list of "first principles" by half — and the half that survives is worth building on.
Section 9

Top Resources

01
Zero to One — Peter Thiel (2014)
Book
The closest thing to a business philosophy built on first principles reasoning. Thiel's central argument — that the most valuable companies create something new rather than copying what exists — is first principles thinking applied to entrepreneurial strategy. Chapter 2 on "party like it's 1999" is a masterclass in identifying which lessons from the past are conventions masquerading as truths. Read this for the mindset, not the method.
02
Thinking, Fast and Slow — Daniel Kahneman (2011)
Book
The scientific foundation for why first principles thinking is necessary and why it's so difficult. Kahneman's work on anchoring, the availability heuristic, and System 1 vs. System 2 thinking explains the exact cognitive mechanisms that cause people to reason by analogy when they should be reasoning from fundamentals. Essential for understanding the enemy — your own brain's preference for fast, convention-based answers over slow, ground-up analysis.
03
The Hard Thing About Hard Things — Ben Horowitz (2014)
Book
Horowitz doesn't use the phrase "first principles" much, but the book is a sustained argument for the practice. His core thesis — that the hardest decisions in business have no formula and no precedent — is a description of exactly when first principles thinking is required. The chapter on "the struggle" captures the emotional cost of abandoning conventional wisdom better than any strategy textbook.
04
Only the Paranoid Survive — Andrew Grove (1996)
Book
Grove's account of Intel's pivot from memory chips to microprocessors is first principles thinking under existential pressure. The entire industry — including Intel's own management — assumed Intel was a memory company. Grove asked what Intel was actually best at (process technology and design) and what the market fundamentally needed (computing power, not storage). The reconstruction that followed created one of the most valuable companies in history. Read Chapter 5 for the decision mechanics.
05
Posterior Analytics — Aristotle (c. 350 BCE)
Primary source
The original source. Aristotle's treatment of first principles as the foundation of demonstrative knowledge — propositions that are true, primary, and better known than the conclusions derived from them — remains the philosophical bedrock of the method. Dense, but surprisingly readable in modern translations. If you want to understand what "first principles" actually means rather than what Silicon Valley has turned it into, start here. The Mure or Barnes translations are most accessible.
Decision Tools Library — Browse by phase
FramingHard Choice ModelCynefin FrameworkReversibility TestReframingAbstraction LadderingSWOT Analysis
Root Causes5 WhysIshikawa DiagramIceberg ModelPareto AnalysisIssue TreesFirst Principles
GeneratingInversionSCAMPERZwicky BoxProductive Thinking
EvaluatingDecision MatrixSix Thinking HatsCost-Benefit AnalysisDecision TreeScenario Planning
Stress-TestingPre-MortemSecond-Order ThinkingLadder of InferenceConflict Resolution
PrioritisingEisenhower MatrixImpact-Effort MatrixSpeed vs. Quality
UncertaintyOODA LoopRegret Minimisation

Why this matters next

mental modelsSurvivorship Bias

Reframing applied the Survivorship Bias mental model

mental modelsSecond-Order Thinking

Reframing applied the Second-Order Thinking mental model

mental modelsFirst Principles Thinking

Reframing applied the First Principles Thinking mental model

mental modelsLeverage

Reframing applied the Leverage mental model

mental modelsScientific Method

Reframing applied the Scientific Method mental model

mental modelsInertia

Reframing applied the Inertia mental model

Continue exploring

5W

Decision tool

5 Whys

Drill vertically into a single causal chain by asking why repeatedly until you h

ID

Decision tool

Ishikawa Diagram

Map all potential causes of a problem across categories to see the full landscap

IM

Decision tool

Iceberg Model

Look beneath surface events to find the patterns, structures, and mental models

PA

Decision tool

Pareto Analysis

Identify the 20% of causes responsible for 80% of the impact — know where to foc

IT

Decision tool

Issue Trees

Break a complex problem into smaller, mutually exclusive, collectively exhaustiv

More like this, in your inbox

I send a newsletter every week — free, no spam, unsubscribe anytime.

Or open the full subscribe page.

On this page

  • What This Tool Does
  • How to Use It — Step by Step
  • When It Works Best
  • When It Breaks Down
  • Visual Explanation
  • Pairs With
  • Real-World Application
  • Analyst's Take
  • Top Resources