Have you ever found yourself staring at the screen late at night, your mind a tangled mess, even though you know what problem needs solving but can’t find a starting point? That anxiety of being overwhelmed by endless information isn’t due to lack of effort, but to lacking a thinking approach that can unravel complex situations.
We’re often told to read more and practice more, but few tell us that real breakthroughs often come from using the right model at the right moment. Just as a martial arts master doesn’t rely on brute force but leverages momentum, Super Thinking is the inner skill of ‘leveraging the situation’.
When you learn to face a dilemma by first asking yourself, ‘What framework am I using to view this problem?’ this simple self‑question can often pull you back from blind flailing onto a clear course.

The first model is first‑principles thinking. It asks you to break a problem down to its most basic facts, stripping away all assumptions and conventions—just like taking apart a clock into gears, springs, and mainsprings, keeping only the indivisible elements.
Imagine you want to reduce energy consumption. The usual approach might be to buy more efficient appliances, but first‑principles thinking prompts you to ask: How is energy actually being used? Is it for lighting, air conditioning, or standby power? Only after quantifying each component can you uncover the real leaks.
This isn’t just talk—Silicon Valley entrepreneurs often use it to disrupt industries. Tesla didn’t simply improve the gasoline engine; instead, starting from the fundamentals of energy storage and electric drive, it redefined what a car is.

The third model is systems thinking. It teaches you not to fixate on isolated events, but to view a problem as a network of interacting parts. Picture a city’s traffic jam: merely widening roads often just shifts the bottleneck to the next intersection.
Systems thinking calls for drawing causal loop diagrams: population growth drives up travel demand, while insufficient parking leads to roadside illegal parking, which further worsens congestion. Only when you identify leverage points in these links—such as implementing congestion pricing or expanding public transit—can you truly change overall behavior.
This mindset is extremely useful in public policy, corporate strategy, and even personal finance. When you see spending spiraling out of control in a budget, try listing income, fixed expenses, variable expenses, and unexpected events, and observe how they influence one another to find the most effective adjustment point.

—— END ——

I really liked how the piece breaks down mental models into actionable steps. The examples were clear and I could apply them to my workflow today.
Really liked the breakdown of using mental models—tried applying the ‘first principles + analogy’ combo to debug a bug at work yesterday and it cut my troubleshooting time in half. Feels like a practical toolkit for everyday coding.
Really enjoyed the section on applying multiple mental models—tried the first‑principles approach on a coding bug today and it cut my debugging time in half. Thanks for the practical tips!
Really liked how the article breaks down using mental models to tackle quick decisions; I tried the ‘first principles’ approach on my work project yesterday and it helped cut down analysis paralysis. Good read.
Really liked the part about using mental models to break down complex problems—felt like a fresh take on the usual advice. I tried applying the ‘inversion’ trick at work today and it actually helped untangle a messy bug. Thanks for the practical examples!
Really liked how the article breaks down using multiple mental models; the examples made it click for me. Will try applying the ‘inversion’ trick in my next project.
I liked how the article breaks down using multiple mental models to tackle a problem step by step. The example about debugging code was especially relatable—reminded me of a time I was stuck on a bug and tried switching perspectives. Good read!
I’ve been trying to apply multiple models to my workflow lately, and this piece really clarified how to switch between them without getting stuck. The examples about combining first‑principles thinking with analogical reasoning were especially useful. Thanks for the practical tips!
Really liked the concrete examples of switching between models—makes the abstract idea feel actionable. I’ve started applying the ‘reverse engineering’ trick to my daily workflow and it’s cutting down decision time.
Really liked the breakdown of using multiple mental models. I tried the ‘first principles + analogy’ combo on a tricky bug yesterday and it cut my debugging time in half. Thanks for the practical tips!
Thanks Jordan! Models halved your debug time.
Really liked the idea of using multiple mental models to crack tough problems. I tried applying it to a work bug yesterday and it helped me see the issue from a different angle. Thanks for the practical tips!
Really liked the breakdown of using multiple mental models; it reminded me how I juggle work and side projects. Thanks for the practical tips!
Really liked the bit about switching mental models when stuck; I tried the ‘outside-in’ approach on a work bug yesterday and it helped me see the gap faster.
Really liked the breakdown of using multiple mental models; the examples on decision fatigue hit home after a long workday. Thanks for the practical tips!
Really enjoyed the breakdown of using multiple mental models—especially the part about switching between first‑principles and analogy when stuck on a coding bug. Felt like a quick refresher I could apply today at work.
I liked how the article breaks down mental models into actionable steps; tried the inversion trick on my work task today and it cut down planning time. Would love to see more examples from creative fields.
Really liked the breakdown of using mental models to speed up decision-making. Tried applying the inversion model to my work queue yesterday and it cut down the planning time by half. Thanks for the practical tips!
Really liked the concrete examples of switching models on the fly. I used the technique to debug a tricky bug this morning and it cut down my time.
Really liked the practical examples on using multiple models to break down a problem. Tried the technique while debugging a script yesterday and it helped me see the issue faster.
I tried applying the multiple models approach to a bug I was debugging last night, and it actually helped me see the issue from a different angle. The examples in the post were clear, though I wish there were more real‑world case studies. Thanks for the insights!
I really liked how the article breaks down using multiple mental models to tackle problems quickly. The examples were clear and I could apply the FEW technique to my work today. Thanks for sharing!
I liked how the article breaks down using multiple mental models; it reminded me of when I tried to debug code by switching perspectives. Good read.
I gave the multi-model technique a shot while troubleshooting a bug at work yesterday and it cut down my debugging time noticeably. Solid read for anyone feeling stuck.