Use first principles thinking

Use first-principles thinking when you need to stop solving borrowed problems. Strip the situation down to facts, test the assumptions, and build the answer from what remains.

Use it when the stakes are high, the usual answer feels inherited, or someone brings you a solution disguised as a problem.

What first principles means

A first principle is a base fact that stays true after you remove assumptions, habits, and inherited answers. Aristotle called it "the first basis from which a thing is known." In practice, it means asking one question until the answer holds:

What do we know is true?

The method sounds simple. The work feels hard because your brain wants shortcuts. Analogy feels fast: "Company X did this, so we should too." Slow down long enough to ask whether the comparison fits.

Use it when the framing feels inherited

First-principles thinking earns its time when a decision can move the business, waste real money, or lock a team into the wrong path.

Good moments to use it:

• Someone states a solution as the problem: "We need better SEO," "We need more content," or "We need enterprise features."
• A competitor action becomes the reason to copy: "They launched this, so we need it too."
• A team cites a best practice without naming the evidence behind it.
• The current strategy solves last year's constraint.
• The decision is costly to reverse.

Pattern matching helps with small, reversible choices. Use first principles for the decisions where the obvious answer can be expensive.

Example: battery costs

In 2008, battery packs cost about $600 per kWh. At that price, electric cars struggled to compete with gas cars. The industry answer told companies to wait for battery technology to improve.

Elon Musk asked a different question: what are batteries made of? Cobalt, nickel, aluminum, carbon, polymers, and a steel can. On the commodity market, those materials cost about $80 per kWh.

Physics did not set the $600 price. Manufacturing, suppliers, and industry structure did. The materials suggested a much lower floor.

Turn statements into better questions

Most teams hand you the first column. Your job is to reach the last column before anyone starts solving.

The value comes from questioning the premise before solving the stated problem.

Apply it to strategy

Richard Rumelt describes good strategy as a diagnosis, a guiding policy, and coherent actions. First-principles thinking strengthens the diagnosis.

Start with what is happening. Use customer behavior, pipeline data, conversion data, retention data, and market evidence. Do not start with what the team wishes were true.

Find the constraint. Every system has a bottleneck. At one stage, the constraint might be pipeline. Later, it might be conversion, onboarding, delivery capacity, or management depth. If you solve the old constraint, you waste effort.

Build from truth, not precedent. "Companies at our stage usually do X" gives you a comparison. "Our data shows Y is the constraint, and Z addresses it with the least waste" gives you a strategy.

Use writing as the test

Clear writing reveals whether you have a first-principles argument. If you cannot explain the chain from fact to conclusion, you probably have a borrowed answer.

Before you recommend a path, write:

• The problem in one sentence.
• The assumptions inside that framing.
• The facts you can prove.
• The facts you still need.
• The answer that follows if those facts hold.

Writing those 5 lines turns vague confidence into something other people can inspect.

Avoid common traps

Confusing rigor with contrarianism

First-principles thinking can lead to a contrarian answer, but disagreement is not the goal. If the facts confirm the standard answer, use it. The value sits in the rigor.

Going too deep

You can decompose anything until the answer becomes useless. Stop when you reach truths you can act on. "Atoms exist" will not help you fix churn.

Rejecting useful analogies

Do not throw away what others have learned. Use analogies as tools to test, not answers to accept. A good comparison can speed up the work after you know the fundamentals.

Analyzing every decision from scratch

First-principles thinking takes effort. Save it for decisions where the cost of being wrong is high. For reversible choices, pattern matching can be good enough.

Pair it with other mental models

First principles decomposes the problem. Other mental models help you stress-test and reconnect the pieces.

• Inversion: Ask how the answer would fail. Attack your conclusion before the market does.
• Second-order thinking: Ask what happens next. Lowering price may win more customers and attract customers who churn faster.
• Systems thinking: Reconnect the parts. A true fact in isolation can still create bad results inside a system.

Practice the habit

You get better by using the method on real decisions.

Further reading

• Good Strategy/Bad Strategy by Richard Rumelt: the clearest strategy book on diagnosis, guiding policy, and coherent action.
• Poor Charlie's Almanack by Charlie Munger: the classic case for a latticework of mental models.
• The Great Mental Models by Shane Parrish: a practical guide to first principles, inversion, and second-order thinking.
• Thinking, Fast and Slow by Daniel Kahneman: the psychology behind shortcuts and deliberate reasoning.
• Farnam Street: First Principles: a useful public primer on the mental model.