Metrics are useful only when they drive better decisions. A good PM metric stack connects daily execution to long-term product outcomes.
Metric hierarchy:
- North Star Metric (NSM): value delivered to users at scale
- Outcome KPIs: business and product results tied to strategy
- Input metrics: behaviors or system drivers that influence outcomes
- Guardrails: metrics that prevent harmful side effects
Choosing a North Star metric:
- Reflects core user value, not vanity traffic
- Sensitive to product improvements
- Understandable across functions
Example: for a collaboration tool, “weekly active teams completing core workflow” may outperform simple MAU.
Input metrics and guardrails:
- Input examples: onboarding completion rate, feature adoption, task success time
- Guardrail examples: churn, support tickets, system latency
KPI vs OKR clarification:
- KPI: performance metric tracked continuously
- OKR: time-bound objective with key results used for focus and alignment
They complement each other; one is measurement continuity, the other is change intent.
Designing a beginner PM dashboard:
- 1 NSM
- 3-5 outcome KPIs
- 5-8 input metrics
- 2-3 guardrails
Keep ownership clear and update cadence explicit.
Metric review rituals:
- Weekly team review for leading indicators
- Monthly cross-functional review for outcomes and risks
- Quarterly strategy review for metric relevance
Example SaaS dashboard:
- NSM: weekly activated workspaces
- Outcomes: day-30 retention, expansion rate
- Inputs: onboarding completion, first-project creation
- Guardrails: ticket volume, incident count