Pressure-test a metric definition before adoption
Use to catch ambiguity and gaming risk in a proposed KPI before the whole team relies on it.
You are an analytics lead reviewing a proposed metric.
Metric name: {{metric_name}}
Proposed definition: {{proposed_definition}}
What decision it informs: {{decision}}
Data source: {{data_source}}
Task:
1. Restate the definition as an unambiguous formula with exact filters, grain, time window, and dedup rules.
2. List edge cases the current wording does not resolve (refunds, nulls, timezone, multi-counting).
3. Identify how this metric could be gamed and what perverse behavior it might drive.
4. Suggest a guardrail or counter-metric to pair with it.
5. Recommend a final crisp definition.
Be pedantic on purpose; ambiguity here costs the whole org later.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{metric_name}}
- {{proposed_definition}}
- {{decision}}
- {{data_source}}
Related prompts
You are a meticulous data analyst. Here is a sample of my raw dataset (header row plus a few rows): {{sample_rows}} Context: this data describes {{data_description}} and I plan to...
You are a senior Python data engineer. Write clean, reproducible pandas code to clean my dataset. Columns and their meaning: {{column_spec}} Known issues to handle: {{known_issues}...
Act as a data analyst guiding me through exploratory data analysis. Dataset summary: {{dataset_summary}} My goal / the question I care about: {{analysis_goal}} Produce an EDA plan...
You are a SQL expert writing for a {{sql_dialect}} database. Here is the relevant schema (tables, columns, types, keys): {{schema}} Question to answer: {{question}} Rules: - Use on...
You are a SQL reviewer. Explain and debug the query below. Dialect: {{sql_dialect}} What I expected it to return: {{expected_result}} What is actually wrong (if known): {{symptom}}...
You are a database performance specialist for {{sql_dialect}}. Slow query: {{query}} Context: - Approximate row counts of the main tables: {{table_sizes}} - Existing indexes: {{ind...
0 Comments
Loading discussion...