← Back to blog

Product Manager · Product Metrics Basics

Product Managers: Fix Activation in 7 Days

Turn vague product questions into clear decisions. One metric at a time.

Who This Helps

You're a Product Manager who gets asked "Is this feature working?" and wants to answer with confidence, not guesswork. The Product Metrics Basics program is built for exactly this moment.

Mini Case

Meet Priya. She manages a team that tracks the same action three different ways. Activation definitions drift across teams. Last quarter, her dashboard showed a 12% drop in new-user activation, but no one could agree on what "activation" meant. Priya spent two weeks in meetings arguing about definitions instead of fixing the problem.

She used the Product Metrics Basics course to define activation as one action ("Complete first project") within a 7-day window. The team agreed on a minimal event taxonomy with just 5 key events. Within one week, they spotted the real bottleneck: a confusing onboarding step that caused 30% of users to drop off.

Do This Now (5 Steps)

  1. Pick one action that signals a user got value. Keep it simple: one event, one time window.
  2. Write down your event taxonomy — list 5 key events your team tracks. Make sure each has required properties (like user ID, timestamp).
  3. Choose a North Star metric and 2 guardrails. For example: "Weekly active users" as North Star, with "Support tickets per user" and "Error rate" as guardrails.
  4. Slice your data by one segment — new users vs. returning users, or mobile vs. desktop. See where activation breaks.
  5. Share your metric charter with the team. One page. No jargon. Everyone agrees on definitions.

Avoid These Traps

  • Defining activation differently in every meeting. Pick one definition and stick with it for at least 4 weeks.
  • Tracking 20 events before you have 5 right. Start small. Add later.
  • Ignoring guardrails. A North Star without guardrails is a rocket without brakes.
  • Looking at averages only. A 90% activation rate hides a 40% rate for mobile users.
  • Changing the definition after one bad week. Give your metric time to tell a story.

Your Win by Friday

By Friday, you'll have a one-page metric charter your team can rally around. Activation is defined. Events are consistent. You'll stop debating definitions and start fixing the real problem. That 12% drop? You'll know exactly where it lives and what to do about it. And you'll sleep better knowing your next product decision is based on a metric you trust.