create-metrics-framework

To define a North Star metric with guardrails, specify a single primary metric reflecting user value, supported by 3-5 input metrics and 2-3 guardrail metrics. This framework prevents unintended optimization and aligns product context with measurement readiness.

Structuring KPIs with AARRR and HEART frameworks involves mapping 3-5 input metrics across acquisition, activation, retention, revenue, and referral alongside happiness, engagement, adoption, and task success. This approach supports your North Star metric with measurable, actionable indicators.

Creating a metrics framework document involves analyzing your product context to generate a structured markdown file. This file defines your North Star, input, and guardrail metrics, providing a standardized reference for teams to instrument and monitor product success.

You need guardrail metrics when optimizing a North Star metric to prevent gaming and unintended optimization. Establishing 2-3 guardrails ensures boundaries stay intact, protecting critical business areas while the primary metric improves.

Yes, you can generate a metrics framework for a specific product area or business goal by providing it as the argument. The system analyzes the specific context and outputs a defined metrics document tailored to that area.

You should include 3 to 5 input metrics in a product measurement framework. These measurable inputs support the North Star metric and are mapped across AARRR and HEART lenses to ensure comprehensive coverage of product performance.