KPI Dictionary & Metric Mapping
Stop KPI arguments by defining metrics once and reusing everywhere
Many reporting conflicts come from undefined or inconsistent KPIs (what counts as a lead, which revenue number, what window, etc.). This recipe builds a KPI dictionary and maps each KPI to source systems and owners, including "confidence levels" and known limitations.
INGREDIENTS
PROMPT
Build a KPI dictionary and metric mapping document. Output: - KPI dictionary table (name, definition, formula, owner, source system) - Source-of-truth hierarchy (when numbers conflict, which system wins) - Known limitations and "how to interpret discrepancies" notes - Review process (who updates definitions, how often) Inputs: - KPIs used in reporting: - Systems/tools: - Who consumes the reports: - Known disagreements or confusion:
How It Works
This recipe creates shared measurement language across SEO, PPC, social, email, and analytics.
Triggers
- Stakeholders argue over which numbers are correct
- "Leads" mean different things in ads vs CRM
- You need cross-channel reporting without confusion
Inputs
- Stakeholder groups and KPIs each cares about
- Source systems (ads platforms, analytics, CRM, ecommerce)
- Current definitions (if any)
Outputs
- KPI dictionary (definitions, formulas, owners)
- Source-of-truth mapping (system priority order)
- Data limitations note (privacy, modeling, sampling)
Actions / Steps
- Identify top 10–25 KPIs used in decision-making.
- Define each KPI in business terms + calculation.
- Assign a source-of-truth hierarchy and an owner.
- Document limitations and how to interpret discrepancies.
Parameters
- KPI list size
- Confidence labels
- Review cadence (quarterly)