prompt

Metric Definition Specification

Create a complete metric definition for {{metric}} with calculation logic, nuances, and stakeholder alignment.

Updated June 2026
The prompt
Write a metric specification for {{metric}}:

1. Definition & rationale:
   - Plain-language description
   - Why does this metric matter? (business impact)
   - How does it connect to {{north_star}}?

2. Calculation logic:
   - Numerator & denominator
   - Filters (time range, geography, user cohorts)
   - Deduplication rules (per user? per session?)
   - Null handling
   - Formula (SQL pseudocode or plain English)

3. Nuances & gotchas:
   - Is this revenue per user or per transaction?
   - Do we exclude certain user segments (bots, test users)?
   - Timezone handling for daily/weekly metrics
   - Seasonality considerations

4. Validation:
   - Sanity checks (expected range, growth trajectory)
   - How to detect calculation errors?

5. Stakeholder ownership:
   - Who owns this metric?
   - Who is the primary consumer (product, finance, etc.)?
   - How often is it reviewed?

6. Changes & versioning:
   - What has changed about this metric over time?
   - Are there legacy definitions to reconcile?

Format as 1-page wiki or Markdown document.
Did it work? Rate this prompt

Variables

Metric name (e.g. 'Monthly Recurring Revenue')
Company north star metric (if applicable)

Details

Author

AI Khazna

License

Security

Type

prompt

Related assets

More curated picks in Data & Analytics.

Audit before you install

Run any source through our checks - AI visibility, security, performance, and stack detection.

More in Data & Analytics