First-Principles Thinking
Core Statement
First-principles thinking means reducing a problem to fundamental truths, then rebuilding upward from what physics, math, and direct evidence allow.
It rejects analogy as the default. "This is how it is usually done" is not evidence that it is how it should be done.
Mental Stack
| Layer | Question |
|---|---|
| Physics | What is actually impossible? |
| Math | What is the theoretical limit? |
| Reality data | What does current evidence show? |
| Design necessity | Which parts/processes are truly required? |
| Execution | What can be tested immediately? |
Key Models
Reason From Fundamentals
Break the object, process, or business model into parts:
- What are the raw inputs?
- What functions must exist?
- What costs are intrinsic vs inherited from the current industry?
- Which constraints are social, contractual, or historical rather than physical?
Think in Limits
Look for the "magic-wand" version:
If reality had no inherited mess, what would the perfect version cost, weigh, produce, or do?
The theoretical limit becomes a north star. The actual design moves toward it.
Aspire to Be Less Wrong
Truth-seeking is a practice, not a personality trait:
- Assume your model is incomplete.
- Seek negative feedback early.
- Let reality correct ego.
- Change direction fast when the data is better than the belief.
Application Pattern
- State the goal in measurable terms.
- List all assumed constraints.
- Mark which constraints are physical laws.
- Mark which constraints are inherited practice.
- Delete or challenge the inherited constraints.
- Rebuild the solution from the minimum necessary functions.
- Test against reality as fast as possible.
Anti-Patterns
- Copying industry architecture because competitors use it.
- Optimizing a part before proving the part should exist.
- Treating expert consensus as final rather than as input.
- Protecting ego instead of updating the model.