1 min lesson
Defining program metrics
Pick two rows from the table in "Defining program metrics" and explain the choice each one supports.
Step 1 of 2
A growth program without a scoreboard is a hobby. Your job is to pick the two or three numbers that tell the team whether a startup program or partnership motion is working, then defend why those and not the flattering ones.
Cursor runs a developer-led motion that crosses self-serve into enterprise. The metric set has to respect that the same lead can convert through product usage, a partnership or a startup-program credit. Start by separating the one number you steer toward from the numbers that keep you honest.
- Metric role
- North-star
- What it answers
- Is the program creating durable value?
- Startup-program example
- Activated teams from the program still active at day 30
- Metric role
- Guardrail
- What it answers
- What must not break while we push the north-star?
- Startup-program example
- Credit cost per activated team; rep response SLA
- Metric role
- Leading
- What it answers
- What moves now, before the outcome lands?
- Startup-program example
- Enriched-and-qualified rate within 24h of capture
- Metric role
- Lagging
- What it answers
- What confirms real impact weeks later?
- Startup-program example
- Paid conversion and seat expansion at day 90
| Metric role | What it answers | Startup-program example |
|---|---|---|
| North-star | Is the program creating durable value? | Activated teams from the program still active at day 30 |
| Guardrail | What must not break while we push the north-star? | Credit cost per activated team; rep response SLA |
| Leading | What moves now, before the outcome lands? | Enriched-and-qualified rate within 24h of capture |
| Lagging | What confirms real impact weeks later? | Paid conversion and seat expansion at day 90 |
Commit to one north-star; surround it with the guardrails it would otherwise sacrifice.