pm-north-star-selectorlisted

# PM North Star selector Helps a PM pick *one* North Star metric. Most teams over-rotate in one of two directions: (a) defaulting to MAU/DAU without checking whether activity actually tracks the strategic bet, or (b) reaching for a sophisticated metric (value delivered, revenue, custom composite) that nobody in the org can explain. The skill forces the comparison and lands on a single defensible number. ## When to use Use this when: - The team is defining a North Star for the first time - The team has a North Star and someone has proposed replacing it - The user is debating "should we use MAU or revenue / value / something more sophisticated?" - A leadership review keeps asking "why this metric?" and the answer doesn't hold Don't use this when: - The user wants a *full* metrics dashboard reviewed — use [`pm-metrics-critic`](../pm-metrics-critic/SKILL.md) - The user is debating *input metrics* under an already-locked North Star — that's a metric-tree exercise, see `decision-making/metrics.md` § growth equation - The strategy itself is unclear — fix that first using [`pm-framework-selector`](../pm-framework-selector/SKILL.md). A North Star without a strategy is just a number. ## The core tension A North Star has two jobs that pull in opposite directions: 1. **Capture strategic product health** — has to move when the product is genuinely working 2. **Align the org** — has to be a single number every team can explain, defend, and act on Teams that only optimize (1) end up