Playbook

Playbook From the archive

First Principles Thinking

Reasoning from fundamental truths rather than copying what others do

Christian Blank 7 min read

From the archive. This preserves an earlier position; its claims and assumptions may differ from my current thinking.

On this page 12 sections
  1. What Are First Principles?
  2. Reasoning by Analogy vs. First Principles
  3. Why First Principles Matter
  4. How to Think From First Principles
  5. Examples of First Principles Thinking
  6. First Principles Applies Everywhere
  7. When to Use First Principles
  8. The Balance: Principles and Patterns
  9. Common Traps
  10. How to Develop This Skill
  11. The Meta Point
  12. The Questions to Always Ask

Most people reason by analogy. They look at what others do and copy it. They accept "best practices" without questioning them. They do things "because that's how it's always been done."

First principles thinking is different. It's reasoning from the ground up—breaking things down to fundamental truths and building from there.

What Are First Principles?

First principles are the foundational truths that cannot be broken down further. They're the axioms—the self-evident starting points.

In physics, first principles might be:

  • Objects in motion stay in motion unless acted upon
  • Energy cannot be created or destroyed
  • Matter is made of atoms

In life, first principles might be:

  • Time is finite
  • Resources are constrained
  • People act based on incentives
  • Everything has trade-offs

These are truths you can build reasoning on top of, but cannot derive from anything more fundamental.

Reasoning by Analogy vs. First Principles

Reasoning by analogy: "Everyone else does X, so we should do X" "This is how it's always been done" "Industry best practice is Y" "Successful Company Z does it this way"

This is how most people think most of the time. It's fast, often works, and requires less effort.

Reasoning from first principles: "What are we actually trying to achieve?" "What must be true for this to work?" "What are the fundamental constraints?" "If we started from scratch, what would we build?"

This is slower, harder, and requires real thinking. But it leads to breakthrough insights and solutions that others miss.

Why First Principles Matter

Reasoning by analogy has limits:

  • You're constrained by what already exists
  • You copy others' solutions to their problems, not yours
  • You inherit their assumptions and mistakes
  • You can't innovate beyond incremental improvements
  • You don't understand why things work

Reasoning from first principles enables:

  • Solutions tailored to your actual problem
  • Innovation beyond what currently exists
  • Deep understanding of why things work
  • Ability to adapt when circumstances change
  • Confidence in your decisions

Analogy is fine for most decisions. But for important problems, first principles thinking is essential.

How to Think From First Principles

1. Question Everything

Don't accept assumptions just because they're common:

  • "Why do we do it this way?"
  • "What problem is this actually solving?"
  • "Is this still true in our context?"
  • "Who says this is the only way?"

Most "rules" are just conventions. Conventions can be changed.

2. Break It Down to Fundamentals

Strip away assumptions until you reach bedrock truths:

  • What are we actually trying to achieve?
  • What are the real constraints?
  • What must be true for this to work?
  • What cannot be changed?

Keep asking "why?" until you hit something that cannot be reduced further.

3. Rebuild From the Ground Up

Once you understand the fundamentals, reconstruct:

  • Given these truths, what follows?
  • What's the simplest solution that could work?
  • What assumptions can we discard?
  • What new possibilities emerge?

You're not bound by how things are currently done. You're only bound by reality.

Examples of First Principles Thinking

Example 1: SpaceX and Rocket Costs

Reasoning by analogy: "Rockets cost $65 million to launch because that's what they've always cost. Space is expensive."

First principles: "What is a rocket actually made of? Aluminum, titanium, copper, carbon fiber. What do those materials cost on the commodity market? About 2% of the typical rocket price. So why does the rocket cost so much?"

Result: SpaceX builds rockets for a fraction of traditional costs by questioning why aerospace had to be so expensive.

Example 2: Meeting Culture

Reasoning by analogy: "We should have daily standups because that's what agile teams do."

First principles: "What are we trying to achieve? Alignment and unblocking. What's the minimum necessary for that? Do we need everyone? Every day? In person? What's the actual constraint?"

Result: Different teams need different meeting structures. Copy the principle, not the practice.

Example 3: Hiring Process

Reasoning by analogy: "We need 5 interview rounds because that's what Google does."

First principles: "What are we trying to learn about candidates? Can we learn it another way? What's the cost of our process? What's the cost of a bad hire vs. a missed good hire? What actually predicts success here?"

Result: Hiring process optimized for your context, not borrowed from someone else's.

Example 4: Working Hours

Reasoning by analogy: "Everyone works 9-5 in an office because that's standard."

First principles: "What actually requires synchronous time? What needs deep focus? What are people's constraints? What outcomes matter? Does location affect any of this?"

Result: Flexible work policies based on actual needs, not tradition.

First Principles Applies Everywhere

This isn't just for business or technology. It's a way of thinking about any problem:

Personal life:

  • "Why do I want this career/relationship/lifestyle?"
  • "What actually makes me happy?"
  • "What constraints are real vs. assumed?"

Learning:

  • "What are the foundational concepts I must understand?"
  • "Why does this technique work?"
  • "What can I derive vs. what must I memorize?"

Problem-solving:

  • "What's the actual problem, not the symptom?"
  • "What must be true for a solution to work?"
  • "What am I assuming that might not be true?"

Planning:

  • "What's the goal, really?"
  • "What constraints are real vs. imagined?"
  • "What's the simplest path to the outcome?"

Once you develop the habit, you see opportunities everywhere.

When to Use First Principles

Use first principles for:

  • Important decisions with lasting impact
  • Problems where current solutions aren't working
  • Innovation opportunities
  • Type A decisions (hard to reverse)
  • When designing new systems
  • When you need deep understanding

Don't use first principles for:

  • Trivial decisions
  • Well-solved problems
  • Time-sensitive situations
  • Type B decisions (easy to reverse)
  • When analogy is working fine

First principles thinking is powerful but expensive. Use it where it matters.

The Balance: Principles and Patterns

You can't rethink everything from scratch every time. That would be paralysis.

The goal is to:

  1. Understand the first principles behind what works
  2. Develop good patterns based on those principles
  3. Apply patterns in most situations
  4. Return to first principles when patterns fail or context changes

Good patterns are derived from first principles. Bad patterns are cargo-culted from others without understanding why.

Common Traps

Trap 1: Assuming you've reached bedrock when you haven't "We need to maximize profit" might feel fundamental, but why? For shareholders? Why do they want profit? To do what? Keep digging.

Trap 2: Ignoring practical constraints First principles thinking isn't about ignoring reality. "In theory this would work" isn't enough if it requires infinite resources or time.

Trap 3: Using first principles as an excuse to ignore all experience Others' solutions might not be right for you, but they contain information. Don't dismiss everything just to "think from first principles."

Trap 4: Over-applying it Not every decision needs first principles analysis. Sometimes "this works fine" is the right answer.

How to Develop This Skill

Practice asking:

  • "What are we actually trying to achieve?"
  • "What assumptions am I making?"
  • "What must be true?"
  • "Why is this done this way?"
  • "If I started from zero, what would I do?"

Study examples:

  • Look for cases where someone questioned conventional wisdom successfully
  • Understand what they saw that others missed
  • Notice the pattern of breaking down and rebuilding

Test it:

  • Pick a current problem
  • List all the assumptions
  • Challenge each one
  • Rebuild without the false assumptions
  • Compare to the conventional approach

Be patient: This kind of thinking is hard. It takes time. It's uncomfortable. That discomfort is the point—you're actually thinking, not just copying.

The Meta Point

This entire onboarding series is built on first principles:

  • Scaling — derived from first principles about how costs grow
  • Trade-offs — derived from first principles about constrained resources
  • Decision types — derived from first principles about reversibility costs
  • Decision records — derived from first principles about clear thinking
  • DRI principle — derived from first principles about accountability
  • Invariants — derived from first principles about identity and consistency

None of these are "best practices" we copied from elsewhere. They're patterns derived from thinking about fundamental truths.

The frameworks work because they're built on reality, not convention.

The Questions to Always Ask

"What am I assuming?" "What must be true?" "Why is it done this way?" "If I started from scratch, what would I build?" "Am I reasoning from fundamentals or just copying?"

Your goal isn't to always think from first principles. It's to know when you are and when you aren't—and to choose consciously.


Once you learn to think from first principles, you see the world differently. You stop accepting things just because they exist. You start building from truth.


Christian Blank
San Francisco · Updated May 2026
christian@blank.dev | www.blank.dev
Co-written and formatted with AI

About this edition

Published September 19, 2026. Historical article preserved from the previous website. This migration does not revalidate every earlier claim.

This page presents a released edition. Later changes to the work appear here when a new edition is published.

Share an observation or a question ↗