AgentSkillsCN

playing-to-win

适用于制定长期产品战略时,当产品需要从横向拓展转向垂直深耕时,或当团队因服务过多用例而难以聚焦优先级时使用。

SKILL.md
--- frontmatter
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

code
┌─────────────────────────────────────────────────────────────────┐
│  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

PrincipleDescription
Explicit choicesWhere to Play AND How to Win
IntegrationChoices must reinforce each other
FocusSaying "no" is as important as saying "yes"
Specific targetsName 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