---
title: "Build #119 – First principles and second-order thinking"
url: https://www.simonwakeman.com/blog/2026/11/18/build-119-first-principles-and-second-order-thinking/
description: "First principles thinking works back to what’s true. Second-order thinking asks what happens next. How I use both to unpick the problems founders bring me."
published: 2026-11-18T07:00:00+00:00
modified: 2026-11-18T07:00:00+00:00
author: Simon Wakeman
---
# Build #119 – First principles and second-order thinking

![Parts of a watch laid out on a workbench beside the open movement](https://www.simonwakeman.com/wp-content/uploads/2026/11/sqYhwhKA3uA.jpg)

## Build #119 – First principles and second-order thinking

A lot of the problems I’m asked to look at in my fractional and consulting work are presented to me by a founder who thinks they’ve got a good idea what the solution needs to be. For example:

“We need a head of operations.”

“We need a new CRM.”

“We need to restructure the leadership team.”

Sometimes that’s exactly right.

But more often though the answer has been reached quickly and under pressure by people who are too close to the problem to see it clearly. And if I just go along with it I end up helping someone do the wrong thing well. It makes me complicit in the supposed solution not actually making the difference that’s needed.

Since working independently two thinking tools have become my default way of slowing that moment down: first principles thinking and second-order thinking.

One works backwards from the problem to what’s actually true while the other works forwards from the fix to what it will actually cause.

Neither’s new or revolutionary, but that doesn’t devalue them. Shane Parrish’s Farnam Street has good primers on [first principles](https://fs.blog/first-principles/) and [second-order thinking](https://fs.blog/second-order-thinking/) that are well worth a read.

But I find they’re talked about far more than they’re properly used, so this week I want to explain them in a bit more detail and explain how I actually use them in my work.

**First principles thinking: working backwards**

The idea goes back to Aristotle, who described a first principle as the first basis from which a thing is known. In plain terms it means breaking a problem down until you separate what you know to be true from what you’re assuming, then building your thinking back up from the true bits only.

The opposite is reasoning by analogy. That’s doing something because it’s how it’s done elsewhere or because it’s how it’s always been done here (I also hear those things a lot). Analogy is quick and usually good enough which is why we rely on it so much. The trouble is it only ever gives you a slightly better version of what already exists.

The example lots of people quote on this is Elon Musk asking what a rocket is actually made of and what those materials cost, rather than accepting what rockets had always cost. Whatever you think of him, the method is the useful bit.

There are two techniques I use most:

-   **The five whys.** Ask why something is happening, then ask why again of the answer, around five times. It sounds childish and that’s rather the point. Most of us give up after two or three rounds, usually just before we get to anything uncomfortable.
-   **Socratic questioning.** A more structured set of questions: what exactly do we mean, what are we assuming, what’s the evidence, how would someone else see this, what follows if we’re right and is this even the right question?

In a founder-led business the assumptions are usually hiding inside the words I hear. “We need a head of operations” contains at least three of them: that the problem is an operations problem, that it needs a person rather than a change in how decisions get made and that the person needs to be senior. Each one might be true. But then again they might not be. They’re definitely worth checking before you write a job description.

**Second-order thinking: working forwards**

First-order thinking asks what happens if we do this… while second-order thinking asks what happens next and then what happens after that.

Howard Marks describes this as second-level thinking in his book The Most Important Thing. His point is that first-level thinking is simple and obvious and because everyone can do it, it rarely gives you an edge. The ecologist Garrett Hardin boiled it down to three words that I use all the time as a coach: “and then what?”

An everyday example is your favourite chocolate bar. You’re hungry, you eat one and then the hunger goes away. That’s the first-order effect and it’s a nice thing. Do it every time you’re hungry and the second-order effects look quite different.

In a scaling business it tends to look like this:

-   founder hires a senior leader to take the pressure off
-   first-order effect is relief and the founder’s happy
-   second-order effects can include the existing team routing around the new person because they’re used to going to the founder, a couple of long-serving managers feeling overlooked and then the founder stepping back in because nothing seems to have changed.

None of that is inevitable but a good deal of it is predictable if you ask “and then what?” a few times before the hire rather than after it.

A few ways to make second-order thinking practical:

-   **Ask “and then what?” at least twice.** Out loud, in the meeting where the decision is being made. The first answer is usually the one everyone already agrees on.
-   **Look across time.** Suzy Welch’s 10-10-10 rule is a simple way in: how will this look in ten minutes, ten months and ten years?
-   **Map who will respond.** Your team, your customers, your competitors and your suppliers will all react to what you do. Most of the time the reaction is small but once in a while that reaction is the real thing to pay attention to.
-   **Look for things that hurt now and help later.** Plenty of good decisions are first-order negative and second-order positive. For example writing down how decisions get made is slow and a bit tedious right now but saves you hours a week over the next six months.

**Using them together**

On their own each tool can present a bit of a blind spot.

First principles thinking can get you to a bold answer with no sense of what it will set off. Second-order thinking can tell you all the ways an answer might go wrong without ever checking it was the right answer to begin with.

That’s why I like using them together so they “cover” each other. First principles to make sure you’re solving the right problem. Second-order thinking ensures the fix doesn’t create a bigger issue.

In practice that’s usually how I work with a leadership team on a gnarly problem. We spend the first part of the session stripping the problem back: what do we actually know, what are we assuming and what would we have to believe for the obvious answer to be right. Only then do we look at options for solving. And for each option we walk forward a few steps and ask who it affects and what happens next.

**Where they go wrong**

I want to share a couple of warnings from my experience of doing this a lot.

First principles thinking is not a licence to tear everything up. G.K. Chesterton made the point with a fence (think of it as a roadworks barrier across a road): don’t take it down until you know why someone put it there. A lot of what looks like pointless convention in a growing business can be there for a reason that’s genuine but never got written down.

And second-order thinking can turn into an excuse never to decide anything. You can always find another consequence to worry about. At some point the useful question becomes which consequences you’re prepared to live with. Don’t get stuck in a second-order thinking infinite cycle.

So one last thought this week. If an adviser, coach or fractional COO (yes, me included) tells you a definitive answer with confidence in your first meeting, be suspicious. I suspect that’s first-order thinking being deployed without the reflection that second-order gives you.

Have a good week.
