Why it is written this way
When asking AI for KPIs with a simple prompt like "Give me KPIs for my team," it typically outputs generic metrics like revenue, traffic, conversion rate, and customer satisfaction score. While none of these are wrong, they fail to clarify what the team should actually execute this week. Top-line revenue is an outcome shaped by multiple overlapping variables rather than a lever a team pulls directly; tracking only lagging outcomes leaves teams clueless about what to adjust when numbers drop.
This is why the second Task paragraph strictly prohibits simply listing KPIs out of the gate. Without this negative constraint, LLMs default to standard textbook KPI lists. The third paragraph breaks the process into three structured Steps, enforcing mathematical decomposition (such as Repeat Customers = Customer Pool × Repurchase Rate). Formulaic breakdowns ensure mathematical completeness without overlap or gaps (MECE), making trade-offs and focus areas explicit.
In the fourth Format paragraph, the "Data Source Location" column separates realistic, deployable KPIs from theoretical ones. Teams frequently define sound formulas that cannot actually be queried from any dashboard. Allowing a "Not Tracked" label exposes instrumentation gaps early, allowing team leaders to separate metric design from tracking infrastructure implementation.
Finally, the concluding paragraph filters out uncontrollable variables and limits the weekly review set to just three indicators. Tracking ten metrics leads to dashboard fatigue where none get monitored; focusing on three ensures consistent operational review during weekly standups.
Unfamiliar terms? See Aha AI: chain-of-thought, output-format
Compared with a bad example
Help me set KPIs for my team this year. The goal is doubling repeat customers.
Produces a generic list of standard metrics: Repurchase Rate, Customer Lifetime Value (CLV), Churn Rate, and Net Promoter Score (NPS). Because the relational logic connecting these metrics to daily actions is missing, the team won't know which lever to pull first. Targets will be filled with arbitrary numbers like "30% repurchase rate," with no data source specified, leaving the dashboard empty and abandoned by the first weekly review.
Variations
Auditing & Streamlining Existing KPIs
Below this line, I will paste the list of metrics our team currently tracks. Please explain the exact mathematical or causal link between each metric and our "{{ultimate final goal}}". For any metric that lacks a clear mathematical relationship, explain why it does not directly contribute. Additionally, identify any missing metrics necessary to achieve the target within {{time period}}, and flag any existing metrics that {{responsible organization}} cannot directly control.
Auditing and pruning existing metrics is often faster than building a framework from scratch. It immediately removes vanity metrics that do not roll up into core goals.
Creating a 1-Page Weekly Operational Review Template
From the KPIs developed above, select only the top 3 critical metrics for {{responsible organization}} to monitor weekly, and design a 1-page dashboard template for our weekly operations meeting. For each metric, include: Current Week Value | Week-over-Week Trend | Remaining Gap to {{time period}} Target | Key Action Item for This Week (1 line). Also specify, for each metric, which secondary diagnostic sub-metric the team should inspect first if the primary metric deteriorates.
Designed for operational execution post-KPI setup. Pre-defining troubleshooting paths saves significant diagnostic time during meetings.
Model notes
Review the Step 1 mathematical decomposition first before accepting the downstream metrics. If the high-level equation is flawed, every downstream operational metric will be misaligned, making post-table corrections much harder.
Related prompts
Last updated 2026-09-02 · Found a mistake? Let us know