How Mental Models for Decision-Making Cut Through the Noise
A project I was managing. It started well, then things went sideways. A client kept adding “small” requests that weren’t small. My team got frustrated. Deadlines slipped. I felt like I was drowning in details, unable to see a clear path forward. Every morning, I’d stare at my to-do list, feeling the weight of it, and just… freeze. That’s when I had to pull out some of the mental models for decision-making I keep in my back pocket.
This isn’t about some airy-fairy philosophy. It’s about practical tools you can use when your brain feels like a tangled ball of yarn. When you’re stuck, these thinking frameworks give you a way to untangle it. They’re not magic, but they sure feel like it sometimes.
First Principles Thinking: A Core Mental Model for Decision-Making
When that project was spiraling, I felt like I was just reacting, patching holes. My first instinct was to try to find another project management tool, or maybe hire a new freelancer to pick up the slack. But those are surface-level fixes. They don’t get to the root of the problem. That’s where First Principles Thinking comes in.
It’s simple, really: break down a problem to its absolute fundamental truths. Don’t assume anything. Don’t rely on “how it’s always been done.” Ask “why?” until you can’t ask it anymore.
For my project, I stopped thinking about “missing deadlines” or “client demands.” I asked: What is the core purpose of this project? What value are we actually supposed to deliver? Why are these specific tasks necessary? Why is the client asking for X, and what problem are they truly trying to solve?
What I found was that the client’s “small requests” weren’t random. They were trying to get to a specific outcome that we hadn’t fully understood at the start. Our initial brief, which we thought was solid, only addressed part of their need. We’d assumed too much about their internal processes. By breaking it down, I realized we needed a complete reset on the scope, not just more hours on the clock. It meant a tough conversation with the client (which, let’s be honest, no one enjoys), but it was a necessary one. We rebuilt the project plan from the ground up, focusing on those core needs. It wasn’t easy, but it worked.
Avoiding Disaster: The Power of Inversion
Sometimes, knowing what not to do is more useful than knowing what to do. That’s Inversion. Instead of asking, “How do I make this project successful?”, ask, “How do I make this project a complete disaster?” What would guarantee failure?
The Mental Models Deck
50 high-leverage thinking tools from philosophy, economics, and psychology. Print-ready flashcard deck.
Get the Deck → $16
When I was facing that client mess, I sat down and made a list of ways I could absolutely wreck the project.
- Ignore the client’s new requests, hoping they’d go away.
- Blame my team for the missed deadlines.
- Promise impossible delivery dates to make everyone happy in the short term.
- Avoid difficult conversations about scope and budget.
- Burn out my team by forcing endless overtime.
Looking at that list, it became painfully clear that many of my initial reactions—like just trying to “work harder” or “keep the client happy” without addressing the core issues—were actually pathways to disaster. It clarified my priorities. I needed to have those hard conversations. I needed to protect my team. I needed to re-evaluate the budget honestly. It sounds counter-intuitive, but thinking about failure often illuminates the path to success with surprising clarity. It’s a fantastic thinking framework.