Back to Prompts

Key Product Metrics

Delivery
109 uses
Updated 3/27/2026

Description

This prompt helps define critical product metrics, aligning them with business objectives. It ensures a data-driven approach to measuring solution impact, user engagement, and growth.

Example Usage

You are a product analytics advisor helping a PM define the right success metrics. Build a metrics framework for [Type your product or feature] that connects business outcomes to actionable product signals.

## Product Context
- **Product/Feature:** {{product_name}}
- **Business objective:** {{business_objective}}
- **Product stage:** {{product_stage}}
- **Current data infrastructure:** {{data_tools}}

## Metrics Framework

### 1. North Star Metric
- Define one metric that best captures the value your product delivers to users
- Explain why this metric matters and how it connects to revenue
- Set a baseline (current) and target (90-day goal)

### 2. Input Metrics (3-5)
For each metric that drives the North Star:
| Metric | Definition | Current Baseline | Target | Owner |
- Include a mix of acquisition, activation, engagement, and retention metrics
- Ensure each is measurable with your current data tools

### 3. Guardrail Metrics (2-3)
- Metrics that should NOT degrade while optimizing the North Star
- Example: revenue growth should not come at the cost of NPS dropping below X

### 4. Measurement Plan
- Where does each metric live? (dashboard, SQL query, third-party tool)
- How often should each be reviewed? (daily, weekly, monthly)
- Who owns each metric and what action do they take when it moves?

### 5. Alert Thresholds
- Define red/yellow/green zones for each key metric
- What triggers an investigation vs. an all-hands response?

### 6. Anti-Metrics
- List 2-3 vanity metrics the team should explicitly NOT track and explain why

Customize This Prompt

Customize Variables0/5
Was this helpful?
Read the full guide
In-depth article with examples, pitfalls, and expert sources
Ready to use this prompt?

Related Delivery Prompts