For a while, my first response to a problem was to work harder. With simple problems, that sometimes worked. When a decision involved many variables, I would spend energy before properly understanding the problem.
When I became a father and a manager, those decisions carried more weight. More people were affected by what I decided. That was when I started looking for a better way to think before acting.
What mental models are
A mental model is a simplified way of understanding part of reality. Since we cannot consider every variable at once, we use models to organize information and make decisions.
Inversion helps me imagine how a plan could go wrong. First principles make me examine rules I accepted without asking why. Incentives help explain behavior; systems thinking helps me see effects that only emerge later.
Each model explains part of the situation. Using more than one makes me less likely to force a problem into my first interpretation of it.
How I found the subject
I came across the concept in 2022, in a talk by Charlie Munger. The idea that stayed with me was simple: when we have few frames of reference, we try to fit every problem to the tools we already know.
I then looked into Farnam Street’s material and Shane Parrish’s book Pensamento eficaz. I found ways to examine assumptions, observe incentives, and think through the consequences before making a decision.
Two quotes from Munger capture this well:
“You’ve got to have multiple models, because if you have just one or two, you’ll torture reality until it fits your models.”
“I don’t think you can get worldly wisdom without 80 or 90 important models in your head.”
Start with what could go wrong
Inversion means looking at the outcome I want to avoid before putting a plan together. Alongside thinking about how to reach the goal, I ask:
- What could make this plan fail?
- What assumption am I taking for granted?
- What cost or constraint have I left out?
- What decision would make the situation worse?
Doing this before implementation often reveals risks I would otherwise have discovered too late.
An example from work
A client kept data in several spreadsheets and wanted to automate the creation of dashboards for their own customers.
Our first solution was to consolidate the files with Python, clean the data, and connect everything to Power BI. Before implementing it, I listed what might get in the way:
- The spreadsheets had an unstable structure.
- Columns, formats, and file paths changed frequently.
- The dashboards could become too rigid.
- Each change might require work from the consultancy.
- The volume of data would keep growing.
That list changed the conversation about the architecture. We began looking for a solution that would let the client create charts and expand its use without calling the consultancy for every change.
The result was a system less dependent on the original spreadsheets and greater independence for the client. Examining the first proposal before writing code made a difference.
Ask why the rule exists
First principles help break a problem down and examine the rules already in place. I usually start with these questions:
- Why does this rule exist?
- What problem did it solve?
- Are the circumstances that led to it still the same?
- What is a technical constraint, and what is a process choice?
This is useful when a team keeps an old process without revisiting the reason for it. Sometimes the rule still makes sense. Sometimes the circumstances have changed and nobody has gone back to look.
How I use this today
In management, I use these models to assess priorities, incentives, bottlenecks, and operational risks. They also help me notice when a quick decision is merely pushing a problem into the future.
Outside work, I use the same questions to examine my reactions, expectations, and personal decisions. The method has limits: it makes my assumptions clearer, but I still make bad decisions.
What changed was the habit of revisiting the first solution. I now look for foreseeable risks and question rules that have lost their purpose more often. When I make a mistake, I have clearer criteria for understanding what happened and reconsidering the decision.
References
Books (links to the editions referenced in the original post):
Blog: