Product Managers: Turn Questions into Decisions with a Weekly Scoreboard

Who This Helps

This is for product managers who sit in meetings where everyone has a different opinion on what the data says. You have questions like "Should we ship this feature?" or "Why did retention drop?" but no clear way to answer them. The Metrics & Dashboards Basics program is built for you. It helps you define a metric system you trust and build a dashboard that supports calm weekly decisions.

Mini Case

Meet Maya. She manages a SaaS product with 12,000 active users. Her team tracks 20 different numbers every week. Last month, they argued for 45 minutes about whether to prioritize speed improvements or new features. Maya had no single metric to settle the debate. She joined Metrics & Dashboards Basics and learned to pick one North Star Metric. She chose "weekly active users" and defined three supporting metrics: sign-up conversion (currently 8%), 7-day retention (42%), and feature adoption (15%). Within two weeks, her team had a clear decision framework. They shipped the speed improvement because retention was below target. No more arguments.

Do This Now (5 Steps)

1. Pick one North Star Metric. Look at your product and ask: what single number, if it goes up, means everything else is working? For Maya, it was weekly active users. Write it down with a clear definition.

1. Define three supporting metrics. These are the levers that move your North Star. For example, if your North Star is revenue, supporting metrics could be new customers, average order value, and churn rate. Set a realistic target for each.

1. Build a weekly scoreboard. Create a simple dashboard that shows your North Star and supporting metrics. Update it every Monday. No more digging through spreadsheets during meetings.

1. Add guardrails. Decide what happens if a metric drops below a threshold. For example, if 7-day retention falls below 40%, trigger a review. This keeps your team proactive, not reactive.

1. Review and adjust. Every month, check if your metrics still match your product goals. If you launch a new feature, update your supporting metrics. This keeps your system fresh.

Avoid These Traps

• Tracking too many numbers. If you have more than five metrics on your scoreboard, you're not focusing. Cut down to what matters.
• Vague definitions. "User engagement" means nothing. Define it as "number of sessions per user per week" or similar.
• Ignoring targets. A metric without a target is just a number. Set a realistic goal so you know when to act.
• Changing metrics every week. Stick with your North Star for at least a quarter. Consistency builds trust.
• Forgetting the human side. Your team needs to understand why each metric matters. Share the story behind the numbers.

Your Win by Friday

By the end of this week, you will have a one-page metric tree with your North Star, three supporting metrics, and clear targets. You will also have a draft of your weekly scoreboard. Your next team meeting will start with data, not opinions. And honestly, that feels pretty great.