Every report needs an owner, a decision and a review date
Most data teams are busy. Fewer can say what their work changed last quarter.
That is rarely a talent problem. It is what happens when reports pile up faster than anyone retires them. We call it operating debt: the running cost of reporting that no longer serves a decision.
How the pile grows
The pattern is simple. Someone asks a question. An analyst builds a report to answer it. The report gets a weekly schedule. The question gets answered, and the report keeps running.
Adding a report takes one request. Retiring one takes agreement from everyone who might still look at it. Under those rules, the pile only grows.
A few years on, there are three versions of “monthly revenue”, each built by a different person. The leadership meeting opens with an argument about which one is right. Analysts spend their week reconciling numbers instead of explaining them.
Gartner’s research hints at the result. In a survey of 566 data and analytics leaders, fewer than half (44%) said their team was effective at providing value to the organisation. In the same survey, 44% said their teams had grown in the past year (Gartner).
The signs are easy to spot:
- Reports outlive their decisions. The launch happened months ago. The launch report still runs every Monday.
- Definitions changed, the logic didn’t. Revenue was redefined last year. Half the reports still use the old rule, and someone adjusts the numbers by hand before the board pack.
- Only the builder can explain it. When they leave, nobody knows whether to fix it, rebuild it or switch it off.
- Switching one off causes alarm. Nobody used it, but nobody is sure.
Why it costs more once AI arrives
A person learns which report to ignore. An AI assistant doesn’t, unless someone tells it.
Connect an assistant to your shared drive or warehouse and it reads the stale report alongside the live one. Microsoft makes the same point to its own customers. It says Copilot and agents work best when content is current and well governed, and it recommends archiving inactive sites so answers draw on current material (Microsoft Learn).
Operating debt used to cost analyst hours. With AI on top, it can also produce confident wrong answers.
The rule that clears it
Give every recurring report three things:
- An owner. One named person, not a team.
- A decision it serves. One sentence: who uses it, for which call.
- A review date. Every 90 days is a sensible start.
At each review, the owner either confirms the decision it still serves, or the report is archived with a note saying why and where its replacement lives. Archive it rather than delete it, so anyone who misses it can ask.
Treat definitions the same way. When a metric changes, list every report that uses it, then update or retire each one.
None of this needs a big programme. The first pass is usually a spreadsheet with one row per report and an afternoon of short conversations.
When not to bother
If you have ten reports and a team of five, you don’t need a policy. You need one hour together and a list of what to switch off. The rule earns its keep when nobody can say how many reports exist.
Don’t retire a report just because it is old, either. A ten-year-old cash report that the CFO reads every Friday is doing its job.
The takeaway
A report with no owner, no decision and no review date costs you something every week, and more once AI starts reading it. Name all three, or switch it off. Then look again in 90 days.