# First Principles Thinking, Explained

> First principles thinking explained: the Aristotle origin, how it differs from reasoning by analogy, when to use it, and a version you can play.

Source: https://www.wavetable.net/frameworks/first-principles

[Frameworks](https://www.wavetable.net/frameworks)

Structuring thinkingAlso called First-principles reasoning

# First Principles Thinking

Break a problem down to the facts you can check, then reason up from those instead of from what's usually done.

## In one look

1.  1Strip the assumptions.
2.  2Keep only what's verifiably true.
3.  3Reason up from there.

Aristotle used "first principles" for the starting truths a subject rests on. Mathematicians and physicists kept the habit: when a problem resists, go back to what the laws say instead of what the textbook examples did.

The problem it solves

## It's always taken six weeks.

Ask why something takes as long as it does and you often get a shrug. Most reasoning at work goes by analogy: we did it this way last time, and competitors do it this way. That's fast and usually fine. First principles are for when the inherited answer is the thing in the way.

## Try it yourself

No sign-up, a few minutes. Everyone agrees what a battery pack costs. You pick the move that tests it.

## Six weeks, taken apart

Client onboarding, described as the industry standard and faster than most.

-   The plan saysKickoff and paperwork: two weeksbecomes Identity checks: two days, and regulated
-   The plan saysData migration: two weeksbecomes Data migration: three days
-   The plan saysTraining and go-live: two weeksbecomes Training: one day. The rest is handoffs and queues left over from an old team structure.

## Good times to run it

-   Cost and pricing reviews where the number "can't" move
-   Redesigning a process, to separate the rules from the habits
-   Strategy work when a whole market shares an assumption
-   Build-or-buy choices inherited from an older version of the company

## When to skip it

-   Cheap, reversible choices. Not everything deserves the effort.
-   Where the convention holds hard-won safety, like checklists and aviation.
-   When speed matters more than the best answer.

Teams we've run sessions with:

-   ![Publicis Groupe](https://www.wavetable.net/logos/publicis-groupe.svg)
-   ![SoundCloud](https://www.wavetable.net/logos/soundcloud.svg)
-   ![WeTransfer](https://www.wavetable.net/logos/wetransfer.svg)
-   ![The New York Times](https://www.wavetable.net/logos/nyt.svg)
-   ![Columbia Business School](https://www.wavetable.net/logos/columbia.svg)
-   ![EY](https://www.wavetable.net/logos/ey.svg)
-   ![Havas](https://www.wavetable.net/logos/havas.svg)
-   ![NYC](https://www.wavetable.net/logos/nyc.svg)
-   ![MCI Group](https://www.wavetable.net/logos/mci-group.svg)
-   
-   
-   
-   
-   
-   
-   
-   
-   

## Run it with your team

That was someone else's battery pack. On your own process, with the people who built it in the meeting, it's harder. We run it as a live session on problems like yours, in small groups with a host.

[Strategy summits](https://www.wavetable.net/for/strategy-summits)[Change management](https://www.wavetable.net/for/change-management)

## More frameworks

-   [Structuring thinking**MECE**A test for any list: no item overlaps another, and nothing important is missing.](https://www.wavetable.net/frameworks/mece)
-   [Decision-making**Pre-Mortem**Before the work starts, the team imagines the project has already failed and explains why.](https://www.wavetable.net/frameworks/pre-mortem)
-   [Communication**Pyramid Principle**Put your answer first, then group the reasons that support it underneath.](https://www.wavetable.net/frameworks/pyramid-principle)
