Who This Helps
Product Managers who feel stuck in endless debate about what to build or test next. This is for you if your team tracks 20 different numbers and you need to pick one primary metric to rally around. The Metrics & Dashboards Basics course shows you how to define a system you trust.
Mini Case
Maya's team was debating three big experiments: a new onboarding flow, a pricing test, and a referral feature. Each had passionate supporters. They spent 3 weeks in meetings, going in circles. Sound familiar?
She built a simple weekly scoreboard. It showed their North Star metric (weekly active users) and three supporting metrics with clear targets. Suddenly, they could see the referral experiment was projected to move the needle by 15%, while the others were estimated at 5% or less. Decision made in 30 minutes.
Do This Now (5 Steps)
- Grab your North Star metric card. If you don't have one, write down the single number that best reflects customer value.
- List your top 3 experiment ideas on a whiteboard or doc.
- For each idea, estimate its potential impact on your North Star metric. Use percentages (e.g., +5%, +12%).
- Now, estimate the effort for each. Use a simple scale: Small (1-2 weeks), Medium (3-4 weeks), Large (5+ weeks).
- Plot them on a 2x2 grid: High Impact/Low Effort goes first. That's your next experiment. The weekly scoreboard from the course makes this a calm, weekly habit.
Avoid These Traps
- The HiPPO Trap: Don't let the Highest Paid Person's Opinion decide. Let the scoreboard guide you.
- Shiny Object Trap: Ignore the cool new tech feature if it doesn't move your core metrics.
- Analysis Paralysis: Don't wait for perfect data. A 70% confident estimate is better than no decision.
- Target Amnesia: Setting targets for supporting metrics and then forgetting to check them.
- Dashboard Sprawl: Building a second dashboard instead of cleaning up your first, cluttered one.
- Silent Alerts: Setting up guardrail metrics but not checking the alerts.
- Vague Metric Definitions: A metric like 'engagement' is useless. Define it clearly (e.g., 'users who complete 3 key actions').
- Weekly Meeting Mayhem: Using your dashboard for a 2-hour deep-dive instead of a 15-minute check-in.
Your Win by Friday
By this Friday, you will have one prioritized experiment on the calendar, backed by a simple impact/effort score. Your team will know exactly what they're building next and why it matters. You'll swap debate for data-driven decisions. And you'll get your Thursday afternoon back. Nice.