Assisted reporting question desk (L2)
Leaders ask their reporting questions in one channel. RevOps answers with the number, the definition used, and the source, assisted by a saved prompt. It kills the analyst interruption cycle and the metric definition drift.
The steps
- 01
Publish the metric dictionary
Tool: Looker
Every metric with a single written definition and owner. Most reporting disputes are definition disputes wearing a data costume. Owner: RevOps lead. DoD: top twenty metrics defined with owners.
- 02
Answer with definition and source
Tool: Claude
Format is number, definition used, source report, as of date. Never a bare number, which is how two teams end up quoting different truths. Owner: RevOps analyst. DoD: format enforced on every answer.
- 03
Route repeats into the dashboard
Tool: Looker
A question asked three times becomes a dashboard tile. Track repeats deliberately rather than answering forever. Pitfall: dashboards built on requests nobody repeats. DoD: repeat log reviewed monthly.
- 04
Escalate definition conflicts
Tool: Slack
When two definitions collide, the metric owner decides within a week and the dictionary is updated with a dated change note. Owner: metric owner. DoD: conflicts resolved with a dated entry.
Tools in this playbook
Building the team behind this workflow?
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.