Skip to content
Log in

Metric Definition Review

Treats two teams reporting one metric differently as a governance problem rather than a query bug.

0

Share this prompt

Free — no card needed

Create a free account

to open Metric Definition Review — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryData AnalysisForAnalysts, OperatorsTested onClaudeChatGPT

Running it, start to finish

  1. Write every definition out as numerator, denominator, population and time basis.
  2. Identify the specific difference rather than checking the queries.
  3. Document the canonical version with its edge cases and exclusions.

What you get back

The output this produces, every time.

  • Writes competing definitions side by side, which resolves most disagreements immediately.
  • Recognises that different definitions often answer different legitimate questions.
  • Sets a restatement policy, since silently changing history destroys trust in every past report.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Resolve the edge cases explicitly. Two implementations of the same definition diverge on partial periods, refunds and back-dated corrections.
  • Name the metrics differently. Where both definitions are legitimate, distinct names serve better than declaring one of them wrong.
  • Assign an owner. Without one the metric acquires several definitions again within a year, which is how the current situation arose.

More Data Analysis prompts

All Data Analysis

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.