define-growth-metricslisted

# Define Growth Metrics Turn a metric name into a reproducible measurement contract. Keep targets tied to a baseline, source, owner, and decision context. ## Inputs Require: - product and business model; - user or account entity; - candidate value event; - available event and billing data; - current baseline or an explicit unknown; - decision owner and review cadence. ## Workflow 1. State the decision the metric should inform. 2. Define the entity and eligible population. 3. Define numerator and denominator in plain language. 4. Define observation window, cohort maturity, time zone, and exclusions. 5. Name the value event and explain why it represents delivered value. 6. Record source tables or events and query version. 7. Record baseline with date and source, or set it to `null`. 8. Propose a target only with provenance, rationale, and human owner. 9. Add at least one counter-metric for quality, risk, or cost. 10. Separate activation, retention, revenue, and satisfaction rather than merging them into one score. 11. For an introduction-enabled first-user loop, use the recipe below instead of treating an invite or signup as value. ## Introduction-loop metric recipe Use this only after the first-five direct-seeding batch has a reviewable value observation. Keep each event separate: - `qualified introduction`: an eligible reuser identifies a recipient with the same stated problem; it is not a sent message. - `referred user's first value`: the introduced user reaches the