Module 3 of 10

Strategy & Bets

Setting product direction, making big calls, communicating strategy

1

Bet, Search, Decide

Name the bet. Search for the truffle. Someone has to decide.

When you're building something new, you don't have all the answers — and that's normal. Think of your strategy like placing a bet: you have a hypothesis about who needs what, you go test it, and you adjust as reality reveals itself. The key is to be honest that it's a bet, stay alert to what the market is telling you, and make clear decisions instead of staying frozen.

2

Vision as Load-Bearing Wall

Vision isn't broadcast — it's infrastructure.

A vision tells your team where you're all going, so every decision they make — even when you're not in the room — points in the right direction. Think of it like a pilot announcing the destination: without it, everyone on the plane is just guessing. Write it down, make it visual, and repeat it constantly until people can say it back to you.

3

Trade-offs Over Verdicts

Show the trade-off. Own the recommendation. Let them own the decision.

When stakeholders push for different features, don't just pick one and defend it emotionally. Use a consistent scoring method like RICE to show where every request sits relative to your goals, then present the actual trade-off: 'If we build X, we delay Y, and here's what that costs.' You're not saying no to a person — you're showing them where they sit in a shared system.

4

Concentrated Bet Strategy

Startups concentrate to build; incumbents diversify to preserve. Know which one you are.

A 'bet' is a big strategic commitment of time, money, and people toward an outcome that isn't guaranteed. The key question isn't which bets sound exciting — it's how many bets your company can actually afford to protect and pursue seriously given your resources. For most early-stage teams, the honest answer is one.

5

Execution Eats Strategy

Ship to learn. Strategy follows execution.

You'll be tempted to spend a lot of time on strategy because it feels important and glamorous. But customers don't care about your roadmap — they care about the product in their hands. Spend maybe 20% of your time pointing in the right direction, and 80% actually building, shipping, and learning.