playing-to-win
Playing to Win Framework
Overview
A strategic framework to create focus by making an integrated set of choices about where the product will compete and how it will succeed, rather than trying to be everything to everyone.
Core principle: Strategy is an integrated set of choices, not a list of goals.
The Four Steps
┌─────────────────────────────────────────────────────────────────┐
│ 1. DEFINE WINNING ASPIRATION │
│ What does "winning" look like for us? │
├─────────────────────────────────────────────────────────────────┤
│ 2. CHOOSE WHERE TO PLAY │
│ Markets / Segments / Personas │
│ Be SPECIFIC (not "everyone") │
├─────────────────────────────────────────────────────────────────┤
│ 3. DETERMINE HOW TO WIN │
│ Value proposition / Differentiation │
│ What makes us win in that market? │
├─────────────────────────────────────────────────────────────────┤
│ 4. EXECUTE │
│ Build capabilities and systems │
│ Align team around choices │
└─────────────────────────────────────────────────────────────────┘
Key Principles
| Principle | Description |
|---|---|
| Explicit choices | Where to Play AND How to Win |
| Integration | Choices must reinforce each other |
| Focus | Saying "no" is as important as saying "yes" |
| Specific targets | Name the segments, not "broad market" |
Common Mistakes
- Skipping "Where to Play" and building for everyone
- Building features for every user type
- Strategy = goal list rather than integrated choices
Source: Annie Pearl (Calendly CPO) via Lenny's Podcast
More from coowoolf/insighthunt-skills
gardening-mindset
Use when dealing with ecosystems, network effects, or high-uncertainty environments where the right answer cannot be known in advance, when rigid planning consumes more value than it creates
45gamification-triad
Use when designing retention mechanisms, habit loops, or auditing why users drop off despite engaging with core features, to structure gamification beyond superficial badges
44three-layer-agent-stack
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
15minimum lovable product (mlp)
In an era where AI lowers the cost of building software, viability is obsolete. The differentiator is joy and emotional connection. Prioritize "Wow" over "Aha"—brand is product interaction.
14curiosity-loops
Use when facing a significant decision (career pivot, product direction, technical choice) and feeling stuck or indecisive, when seeking contextual advice rather than generic recommendations
13pre-mortem-kill-criteria
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
13