First Principles Thinking
Break a problem into its most defensible facts and real constraints. Then rebuild the solution without treating convention as necessity.
Reason from foundations instead of copying the assumptions built into existing answers.
What must be true here, and what are we merely assuming?
Hard problems, entrenched practices, product design, strategy, cost structures and innovation.
Fast overview
Many decisions begin with analogy: “How is this usually done?” First Principles Thinking begins one level deeper: “What do we actually know, what constraints are real and what have we simply inherited?”
Expose assumptions
Keep defensible facts
Create options from the foundation
This does not mean ignoring experience. Analogy is efficient and often useful. First-principles reasoning is especially useful when inherited assumptions are blocking better options.
Mental Model Compass
Learn it progressively
State the problem precisely
Define the outcome, boundary and decision. Vague problems produce vague foundations.
Surface assumptions
Write down the rules, beliefs and constraints you are currently treating as given.
Classify each claim
Separate hard facts and constraints from evidence-based uncertainties, conventions and assumptions.
Strip away what is optional
Challenge inherited practices. Keep only what survives evidence, logic or genuine constraints.
Rebuild and test
Create options from the remaining foundation. Then test feasibility, incentives, costs, downstream effects and the assumptions that still need evidence.
Assumption classifier
Paste one claim that shapes your problem. Classifying it correctly matters more than sounding certain.
See it in practice
Education
Instead of assuming a course needs fixed seat time, begin with the learning outcomes, evidence of mastery, learner constraints and feedback needed. Then design the delivery method.
Business cost
Instead of asking how to negotiate a 10% cheaper process, separate the required outcome from the current process. Some steps may be conventions rather than necessary costs.
Product design
Instead of copying competitor features, start with the user's job, real constraints and evidence of what creates value. Rebuild the smallest solution that satisfies them.
Worked application
Problem: “We need to hire five more people to handle growth.”
Current assumption: More customer volume requires roughly proportional headcount.
Deconstruct: The real requirement is timely, accurate handling of additional customer work. Headcount is one method, not the requirement itself.
Facts to establish: Volume by task, handling time, error rate, peak demand, service target and which work requires human judgment.
Rebuild: Options may include removing unnecessary steps, changing the workflow, automating repetitive tasks, improving self-service, shifting capacity or hiring selectively.
Test: Measure whether the redesigned process meets service and quality thresholds before assuming that hiring is unnecessary.
First principle or just a deeper assumption?
A useful discipline is to keep asking what supports the claim. In formal reasoning, first principles are starting points rather than conclusions derived from still more fundamental premises. In practical decisions, many supposed “fundamentals” are empirical claims, so they should remain open to evidence and revision.
Use the label carefully. The aim is not philosophical certainty. The aim is to expose assumptions and ground the decision in the strongest available foundation.
Common mistakes
Reinventing everything
Existing solutions often contain accumulated learning. Rebuild only where the value of challenging assumptions justifies the effort.
Calling preferences facts
“Customers want this” is an empirical claim, not a foundational truth. Ask what evidence supports it.
Ignoring constraints you dislike
Regulation, physics, contracts, budgets and human limits do not disappear because a new design is attractive.
Stopping after decomposition
The value comes from rebuilding a better option and testing it, not merely questioning the old one.
When not to use it
Do not rebuild routine solutions from scratch when the established approach is inexpensive, well tested and good enough. First Principles Thinking costs time and attention. Use it where assumptions may be creating a meaningful ceiling, where the stakes justify deeper reasoning or where conventional answers repeatedly fail.
Related mental models
Inversion
After rebuilding an option, invert it to expose how the new design could fail.
Second-Order Thinking
Trace how people and systems may respond after the rebuilt solution is introduced.
Opportunity Cost
Compare the rebuilt option with the best alternative use of the same scarce resources.
Try It Yourself prompt builder
Save as Skill
Make First Principles Thinking reusable in your AI workflow
This skill separates facts, uncertain claims and inherited assumptions, then rebuilds options from the strongest available foundation.