Decision-Making and Resilience in Uncertainty

Strategy vs. Planning: Embracing the "Angst"

The first and most critical mental shift is understanding the profound difference between a plan and a strategy. Most companies have plans, but very few have a real strategy. A plan is a list of internal activities you control. A strategy is a coherent set of choices about how you will win in a competitive market you don't control.

This distinction is the very source of the uncertainty and anxiety that founders face. Planning feels comfortable because you control the inputs—hiring developers, launching a marketing campaign, building a new feature. Strategy feels uncomfortable because it involves making a bet on an outcome you don't control—whether customers will choose you over a competitor.

The key takeaway is that your job as a CEO is not to create a perfect, static plan. It is to formulate a clear, logical theory of how your company will win, and then build a system to test and adapt that theory in the real world. This requires a new set of thinking tools.

Your Thinking Toolkit: Key Mental Models for Founders

If strategy is about navigating complexity, then mental models are your compasses and maps. A mental model is a simplified representation of how something works. For a technical mind like yours, you can think of them as conceptual algorithms for decision-making. They don't give you the answer, but they provide a structured way to analyze a problem.

The Farnam Street channel is an excellent resource for this, and we'll explore some of their most powerful models for founders.

Let's apply these three models directly to the challenges of running your IT services company:

1. Second-Order Thinking: The Consequences of Consequences

First-order thinking is fast and easy. It looks for the immediate solution to the immediate problem. Second-order thinking is deeper and more deliberate. It asks, "And then what?"

• Scenario: A large, well-known Nepali company offers you a project, but at a 30% discount on your standard rate.
• First-Order Thinking: "Great! This project will improve our cash flow this month and add a prestigious logo to our website."
• Second-Order Thinking:
  • "And then what? Our team will be working on a low-margin project, potentially burning them out and fostering resentment."
  • "And then what? We set a precedent. This client will expect discounts forever, and they might tell other local companies about our low rates, damaging our future pricing power."
  • "And then what? The time we spend on this low-margin project is time we don't spend prospecting for high-margin international clients, delaying our ultimate goal."

Second-order thinking transforms a seemingly good opportunity into a strategic liability. This is the "problem finder" mindset from our previous lesson in action.

2. Probabilistic Thinking: Becoming a Better Bettor

Uncertainty means you can't know the outcome, but you can estimate the odds. Probabilistic thinking replaces the question "Is this the right decision?" with "What is the expected value of this bet?"

• Scenario: You're considering spending NPR 50,000 on a targeted LinkedIn ad campaign to attract US-based clients.
• Binary Thinking: "This is risky. It might not work, and we'll lose the money." Or, "We have to try this to grow!"
• Probabilistic Thinking:
  • "What do we estimate is the probability of this campaign generating at least one qualified lead? Based on some research, let's say 25%."
  • "What is the probability of it failing completely? 75%."
  • "If it fails, our downside is capped at NPR 50,000."
  • "If it succeeds, and we land one average-sized international project (e.g., $10,000 or ~NPR 1,300,000), the upside is huge."

This decision has an asymmetric payoff: limited, known downside and a very large potential upside. Even with a high chance of failure, it's a strategically sound bet to make. Your job is to consistently place small, well-reasoned bets with asymmetric payoffs.

3. Inversion: Avoiding Stupidity is Easier than Seeking Brilliance

Instead of asking how to achieve a goal, you ask what would guarantee failure. By identifying and then avoiding the paths to failure, you dramatically increase your chances of success.

• Goal: Secure our first five international clients.
• Forward Thinking: "We need to build a better portfolio, write better cold emails, and improve our website." (This is vague).
• Inversion: "What would absolutely guarantee we fail to get any international clients?"
  • We'd have terrible communication skills and respond slowly. (Solution: Set a 12-hour response time SLA).
  • Our contracts would be unprofessional and leave clients feeling unprotected. (Solution: Invest in a solid legal template).
  • We'd deliver buggy code and miss deadlines. (Solution: Implement a mandatory code review and QA process).
  • We'd fail to understand their business context and just be 'code monkeys'. (Solution: Train our team to ask 'why' during discovery calls).

Inversion gives you a concrete, actionable checklist of critical risks to mitigate. This is the core of building organizational resilience.

A Framework for Resilient Decision-Making

Let's combine these ideas into a practical, repeatable framework you can use for any significant decision.

Step 1: Frame the Decision as a Strategic Choice

• What is our goal? Where are we choosing to play, and what is our theory about how we will win? (Reference the HBR video).
• Example: "Our strategic choice is to enter the US market for Django development. Our theory is that we can win by offering a superior price-to-quality ratio combined with excellent communication, targeting small to medium-sized agencies who need a reliable white-label partner."

Step 2: Conduct a "Pre-Mortem" (Inversion)

• Imagine it's one year from now and the initiative has failed spectacularly.
• Brainstorm all the possible reasons why it failed. (e.g., "We couldn't build trust," "Our time zone difference was a bigger issue than we thought," "Our pricing was actually too low, making us seem low-quality.")
• This gives you your primary risk register.

Step 3: Analyze the Chain Reactions (Second-Order Thinking)

• For your proposed course of action, what are the first, second, and third-order consequences? Consider the impact on your team, cash flow, brand, and focus.

Step 4: Place Your Bet (Probabilistic Thinking)

• Acknowledge you can't be certain. Assign rough probabilities to the outcomes.
• Look for the asymmetric bet: the option with manageable downside and significant upside.
• Is there a way to run a smaller, cheaper experiment to get more data before making the big bet? (e.g., A small ad campaign before hiring a full-time salesperson).

Step 5: Document and Iterate

• Write the decision down on a single page.
  • The Choice: What we decided to do.
  • The Logic: Why we believe this will work (our theory).
  • Key Assumptions: What must be true for this to work? (e.g., "We assume US agencies are actively looking for outsourcing partners on LinkedIn.")
  • Success Metric: How will we know if we are winning? (e.g., "Number of discovery calls booked with US agencies per month.")
• This document is not bureaucracy. It's your learning tool. Regularly review it. If an assumption proves false, you don't call the decision a "failure"—you simply tweak the strategy with new data. This loop is the engine of resilience.

This Week's Implementation Plan

It's time to apply this framework to a real decision at your company.

1. Identify One Uncertain Decision: Choose one significant strategic question you and your co-founder are currently facing. Examples:

   • "Should we niche down to only serve the fintech industry?"
   • "Should we invest time and money to get listed on Clutch?"
   • "Should we hire a junior developer now or wait until we have more revenue?"

2. Run it Through the 5-Step Framework: Create a document and work through the process.

   • Step 1: Frame it. Write down your strategic theory for why this decision makes sense.
   • Step 2: Pre-Mortem. List at least 5 reasons this initiative could fail.
   • Step 3: Second-Order Effects. Map out the potential ripple effects of the decision (positive and negative).
   • Step 4: Assess the Bet. Is this an asymmetric opportunity? What's the cost of being wrong vs. the reward for being right?
   • Step 5: Document. Summarize the choice, logic, and key assumptions on a single page. If you decide to proceed, set a date in 1-2 months to review your key assumptions against reality.

This exercise will transform a vague, anxiety-inducing problem into a structured, well-reasoned strategic bet.

Conclusion

You have now completed the foundational module on the founder's mindset. You've moved from being a reactive developer to a proactive leader, armed with systems for managing your time, scaling your impact through delegation, and now, making sound decisions in the face of uncertainty.

Key Takeaways:

• Embrace the discomfort of strategy; it's where value is created.
• Use mental models like Second-Order Thinking, Probabilistic Thinking, and Inversion to deconstruct complex decisions.
• Build resilience not by avoiding failure, but by creating a system to learn from your bets and adapt your strategy.
• Every significant decision is a hypothesis. Your job is to run the experiment as cheaply as possible and learn from the results.

With this internal operating system established, we are now prepared to engage with the external world. In our next lesson, we will begin Module 2: Company & Legal Foundations. We will shift from the abstract world of mindset to the concrete world of legal mechanics, starting with the essential first step: navigating the requirements for legally registering your IT company in Nepal.