playbooks

home / skills / coowoolf / insighthunt-skills / playing-to-win

playing-to-win skill

/decision-thinking/playing-to-win

This skill helps product teams define a focused long-term strategy using the Playing to Win framework to select where to play and how to win.

npx playbooks add skill coowoolf/insighthunt-skills --skill playing-to-win

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.8 KB
---
name: playing-to-win
description: Use when defining long-term product strategy, when needing to pivot from horizontal to vertical focus, or when teams struggle with prioritization due to serving too many use cases
---

# 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*

Overview

This skill codifies the Playing to Win framework to help product teams create focus by making an integrated set of strategic choices. It guides you from defining what winning looks like to selecting where to play, determining how to win, and aligning execution. Use it to replace vague goal lists with a cohesive, prioritized strategy.

How this skill works

The skill walks teams through four concrete steps: define a winning aspiration, choose specific markets or segments, determine a differentiated value proposition, and align capabilities and execution. It inspects current product scope and prioritization problems, surfaces overbroad target definitions, and forces explicit trade-offs. Outputs are clear choices that tie target segments to differentiators and execution priorities.

When to use it

  • Defining or revising long-term product strategy
  • Pivoting from a horizontal, broad approach to vertical or niche focus
  • When teams are adding features to serve many disparate use cases
  • Prioritizing roadmap items against strategic trade-offs
  • Aligning cross-functional teams around a single set of choices

Best practices

  • Start by writing a concise winning aspiration that guides decisions
  • Specify exact segments, personas, and use cases instead of 'everyone'
  • Translate 'how to win' into measurable differentiation and defensible capabilities
  • Use explicit yes/no choices; document what you will not pursue
  • Align hiring, metrics, and roadmap to reinforce the chosen strategy

Example use cases

  • A SaaS product narrowing from generic collaboration to legal teams as a vertical
  • A marketplace deciding which customer segments to prioritize to improve unit economics
  • A startup creating a one-page strategy to resolve roadmap conflicts
  • A product leader building a business case for capability investments tied to a chosen market

FAQ

How specific should 'where to play' be?

Be as specific as necessary to guide decisions: name industries, archetypal customers, and key use cases rather than broad market labels.

Is this framework only for large companies?

No. It scales to startups and large firms because it focuses on choices and alignment, which are essential at any stage.