​

Thinking Frameworks

“The quality of your thinking determines the quality of your life.”

These are the mental models I actually use — not textbook definitions, but practical tools I reach for when making decisions, solving problems, or cutting through noise.

---

​

First Principles Thinking

What it is: Strip a problem down to its fundamental truths and build up from there, rather than reasoning by analogy (“this is how it’s always been done”). When I use it: Architecture decisions, product strategy, career moves — any time the default approach feels wrong but I can’t articulate why. Example: When designing slashAvi.sh, the default approach was “pick a blog platform.” First principles: What do I actually need? A connected knowledge system, not a chronological blog. That led to Mintlify (docs-as-code) instead of Medium or WordPress. The trap: First principles thinking is expensive. Don’t use it for every decision — save it for high-stakes, non-reversible choices. For everything else, heuristics are fine.

---

​

Inversion

What it is: Instead of asking “How do I succeed?”, ask “How would I guarantee failure?” Then avoid those things. When I use it: Goal planning, risk assessment, system design. Example: Planning my Life OS — instead of “How do I be productive?”, I asked “What would make me completely unproductive?” Answer: no sleep schedule, reactive calendar, no boundaries on Slack, no protected focus time. So I built systems to prevent each one. The trap: Inversion shows you what to avoid, not what to pursue. Use it alongside forward-thinking, not as a replacement.

---

​

Second-Order Thinking

What it is: Think past the immediate consequence. Every action has a first-order effect (obvious) and second/third-order effects (hidden). Most people stop at first order. When I use it: Financial decisions, team processes, automation choices. Example: “Let’s add a mandatory code review approval step” — First order: better code quality. Second order: slower PR cycle, developer frustration, people gaming the system with rubber-stamp approvals. Third order: talent attrition. The full picture changes the decision. The trap: You can spiral into infinite “what ifs.” Limit yourself to two levels of consequence for most decisions.

---

​

The 80/20 Principle (Pareto)

What it is: Roughly 80% of outcomes come from 20% of inputs. Find the vital few and focus there. When I use it: Prioritization, feature development, time allocation. Example: In my personal finance system, 80% of savings come from 3 decisions: housing choice, car choice, and automated investment. Optimizing coffee spend is noise. I focus on the big levers and ignore the small ones. The trap: The 80/20 split isn’t literal — it’s directional. Don’t use it to justify ignoring the “long tail” when quality requires thoroughness (security, testing, legal compliance).

---

​

Regret Minimization Framework

What it is: Project yourself to age 80 and ask: “Will I regret not doing this?” Useful for big, scary, irreversible decisions. When I use it: Career moves, migration decisions, creative projects. Example: Moving to Australia — the logical analysis was ambiguous (good salary but far from family, new culture but uncertain career path). The regret question was clear: “At 80, will I regret not trying?” No. “Will I regret not trying?” Absolutely. Decision made. The trap: This framework biases toward action, which is usually good but not always. Sometimes the regret-minimizing choice is to stay and go deeper, not to jump.

---

​

Eisenhower Matrix

What it is: Categorize tasks into four quadrants based on urgency and importance. Focus on Important + Not Urgent (Quadrant 2) — that’s where long-term growth lives. When I use it: Weekly planning, deciding what to work on when everything feels urgent. Example: Writing for Nishabdham is Important + Not Urgent. It never screams for attention, so it gets pushed indefinitely — unless I deliberately schedule it in Quadrant 2. Most things that matter for long-term growth (health, writing, relationships, learning) live in Q2. The trap: Everything feels urgent when you’re stressed. The matrix only works if you’re honest about what’s actually important vs what just feels pressing.

---

​

Pre-Mortem

What it is: Before starting a project, imagine it has already failed. Ask: “What went wrong?” This surfaces risks that optimism blinds you to. When I use it: Product launches, major refactors, team initiatives. Example: Before launching a new feature at work, I run a 15-minute pre-mortem with the team: “It’s 3 months from now and this feature flopped. Why?” Common answers: we didn’t validate with users, the migration path was too complex, we underestimated ops load. Each answer becomes a mitigation action. The trap: Pre-mortems can become doom-spirals if not time-boxed. Keep it to 15 minutes and focus on the top 3-5 risks, not every possible failure mode.

---

​

Compound Thinking (1% Gains)

What it is: Small, consistent improvements compound dramatically over time. 1% better every day = 37x better in a year. 1% worse = nearly zero. When I use it: Habit building, skill development, financial planning. Example: My writing habit — one sentence per day seems trivial. Over a year, it’s 365 sentences. Over two years, it’s a body of work. The same applies to savings, fitness, and technical skills. The math of compounding favors patience over intensity. The trap: Compounding requires consistency, not perfection. Missing one day isn’t a failure — missing two weeks because you “broke the streak” is. The system matters more than any single day.

---

​

How I Choose Which Framework to Use

Not every decision needs a framework. Here’s my rough heuristic: The goal isn’t to memorize frameworks — it’s to internalize them so they become reflexive. Like any habit, it starts mechanical and becomes automatic.