How to build reporting that leads to decisions rather than to a monthly document nobody acts on.
Written for Teams producing marketing reports that get read and then changed nothing.
The bottleneck
Most marketing reports describe what happened. Very few say what should change as a result. The difference is whether the report was designed around decisions or around available data.
The second failure is definitional. A lead means four different things to four people, so the same number gets reported and interpreted differently in the same meeting.
Why it happens, five levels down
- Reports are produced and nothing changes.Why? They describe activity rather than support a decision.
- They were built from what the tools export.Why? Nobody asked which decisions the report is for.
- Decisions were not defined first.Why? Reporting is owned by whoever runs the tools.
- It sits with tooling rather than leadership.Why? It is seen as an administrative task.
- Reporting has no decision owner.Root cause. Name the decisions first and the dashboard designs itself.
The diagnostic
Run this before planning any work. It tells you whether this is your constraint or whether something else is.
- List the decisions this report should support. If the list is empty, stop building it.
- Ask three people to define a qualified lead. Compare the answers.
- Check whether every metric has a written definition and a source.
- Confirm each number has a baseline and a comparison period.
- Check whether anyone has ever changed a plan because of this report.
- Look for metrics nobody has asked about in six months. Remove them.
The build sequence
| Stage | Work | Timing |
|---|---|---|
| Decide | Name the decisions the reporting exists to support. | Week 1 |
| Define | Write definitions for every metric. Circulate and get agreement. | Week 1 |
| Baseline | Record the current state with dates before changing anything. | Week 2 |
| Connect | Link the data sources so the report builds itself. | Weeks 2–3 |
| Comment | Every report carries an interpretation and a recommendation. Numbers alone do not. | Ongoing |
| Review | Monthly review that ends in a decision, or it did not need to happen. | Monthly |
KPI watchlist
| Metric | Source | Read it as |
|---|---|---|
| Data completeness | Source systems | Whether the report can be trusted |
| Pipeline and conversion | CRM | The commercial picture |
| Customer acquisition cost | Spend against closed work | Efficiency |
| Decisions made per review | Meeting record | Whether reporting is working |
Record a baseline and a date range for each before any work begins. Reconstructing a baseline afterwards is usually impossible.
Four ways this goes wrong
- Reporting every available metric. Volume hides the signal.
- Changing metric definitions mid-year without noting it.
- Presenting numbers without interpretation.
- Reporting traffic to a board that needs pipeline.
Name the decisions first
A dashboard without a decision behind it is a document nobody reads.
