How It Works
A trusted business answer should produce more than a narrative.
Adequate Data should show:
1. Question asked - the plain-English request
2. Clear answer - the result in business language
3. Calculation used - the query or calculation behind the answer
4. Data used - source table or file, fields, row counts, and context
5. Verification boundary - what was verified, projected, or not verified
6. Receipt - exportable evidence for later review
Example Questions
Good prompts:
- "Who were the top 10 users of our asset library last month?"
- "Which assets were downloaded the most by sales?"
- "Why did software spend increase in April?"
- "Which reps created the most pipeline this quarter?"
- "Which customers submitted the most urgent support tickets?"
Verification Labels
Use precise labels:
- Verified - tied to SQL, source context, and an evidence receipt
- Projected - calculated from assumptions or incomplete future data
- Diverged - materially different from a previous baseline or expected range
- Not verified - narrative or UI context that lacks sufficient source evidence
Avoid labels that imply magic or automatic correctness.
SQL View
The calculation used is part of the product promise. Users should be able to inspect it, copy it, and understand which source, filters, and definitions it belongs to.
The receipt should make clear whether the calculation can be reproduced against the same data snapshot.