metric-framework-designerlisted

# Metric Framework Designer ## When you activate Before a product's first real user. User says: "what should I track?", "set up metrics for X", "ready to launch — what do I measure?" ## What you produce A `products/<name>/metrics.md` file: ``` ## Metrics Framework — <product> ### North star metric <single number> — what we optimize for above all else. Why this one: <reasoning> ### Activation criterion A user is "activated" when they: <specific action within Y minutes/days of signup>. Why this defines "real" use: <reasoning> ### Retention targets - Day 1: ≥ X% of activated users return - Day 7: ≥ Y% - Day 30: ≥ Z% - Benchmarks based on <industry / similar-product reference> ### PMF target Sean Ellis survey at N=40 active users: ≥40% answer "very disappointed" to "how would you feel if you could no longer use this?" ### False-positive shape (what would LOOK like PMF but isn't?) 1. <e.g. "spike from HN front page that decays in 7 days"> 2. <e.g. "high signup rate but D7 retention < 20%"> 3. <e.g. "founder's network signup dominance"> ### Anti-metrics (things we deliberately don't optimize) - <e.g. "page views" — vanity> - <e.g. "signups without activation" — see above> ### Reporting cadence - Daily: 1 number — yesterday's <NSM> - Weekly: cohort retention curve + signup → activation funnel - Monthly: revenue, churn, expansion (post-payments) ### Tracking implementation - PostHog events to fire: <list of event names> - PostHog dashboards to create: <list> - GSC + Plausi