I killed a report. It didn't stay dead.

I was cleaning up a client's Power BI workspace when I found a small report sitting untouched for months. Nothing sprawling, just a handful of pages, but built years earlier around one CEO's exact preferences. He'd since left the company, and going by the usage logs, nobody had opened it since. It had all the marks of the textbook case: something shaped around one person's habits instead of a business need, and once that person was gone, it just kept running because nobody made the call to stop it.

So I made the call. Archived it. Felt good about it too. One less report somebody had to keep fresh for nobody in particular. One less thing eating maintenance time every week.

A week later I got a message. Somebody else in the C-suite, not the person the report had been built for, wanted to know where it went.

Turns out the old CEO hadn't been the only one looking at it. He'd been pointing at least one other exec toward it. That person had kept using it long after the original request was ancient history. There was no requirements doc that said so. Why would there be? It was just a habit one person picked up from another, and the habit outlived the reason for it.

I told them the truth. It had gone low-usage, so it got flagged in a cleanup pass. I'd misjudged who was actually still pulling from it. Then I brought it back.

Here's the part that's actually useful, not just a good story. When I finally did retire that report for real, months later, I didn't rebuild it better. I sat down with the person still using it and asked what they actually needed out of it. Turned out almost everything they cared about already existed somewhere else, in a report built for the whole team, not assembled around one executive's personal taste. There was no reason to keep a one-person report on life support once the same data was already sitting in something everyone else was already using.

That's usually the real problem with a report like this. It's not that it exists. Reporting is supposed to exist. It's that it got built as a personal artifact instead of shared infrastructure. When the person it was built for moves on, there's no natural next owner. Just whoever happens to be looking at it when someone finally tries to clean house.

Every business I've worked with has at least one of these. A dashboard someone built for a boss who left three years ago. A report that "everyone knows" gets sent out but nobody could tell you who actually reads it. A spreadsheet with a name like [Owner]'s Weekly, still refreshing itself every Monday morning.

Do you know, off the top of your head, which of your reports were built for a specific person instead of a specific need? And if that person left tomorrow, would you know who else was relying on it before you touched it?