metrics-frameworklisted

# Metrics Framework ## Usage **When to use:** - **Lookup mode** — "how do we measure X?", "what's the formula for activation rate?", "is our churn definition correct?" — quick single-metric lookup - **Framework mode** — defining what success looks like for a product or team — full north star, input metrics tree, guardrails, OKRs **Inputs:** A metric name (lookup) or a product/team description (framework) **Output:** Lookup → definition, formula, benchmarks, common mistakes. Framework → north star, input metrics, guardrails, OKRs, quality gate verdict. --- ## LOOKUP MODE Answers "how do we measure X?" from the canonical definitions file. Saves the Slack thread that always follows ("wait, do we measure activation as 7d or 14d?"). **Clarify before looking up** — "how do we measure activation?" could mean: - "What's the definition?" → this mode - "What's our current activation rate?" → analytics tool / data team, not this skill - "Is our activation rate good?" → definition + benchmarks (this mode handles both) - "How do we improve activation?" → `friction-log` or `experiment-design` If ambiguous, ask: "Do you need the definition, the current number, or ideas for improving it?" **Lookup steps:** 1. Read `knowledge/metrics/definitions.md` If the file cannot be read: "I can't access `knowledge/metrics/definitions.md` — lookup mode depends on your team's canonical definitions. Two options: **1) Paste the file contents** and I'll look up correctly, or **2) Continue without