posts

The reporting system that runs on one person's willpower isn't a reporting system. It's a hostage situation with good intentions.

Every reporting org has one. The person who comes in early during close. Who knows which tab to refresh first. Who can answer the question before anyone finishes asking it.

I've been that person. I've also had to replace one. Neither is a place you want to be.

The hero gets praised in the all-hands. The hero also can't take a vacation without somebody texting them about a number. That's not a compliment. That's a system that depends on one person never being unavailable.

The right reward isn't a shout-out. It's making the hero unnecessary.

Most reporting problems come down to one question: where does this number live?

I've watched it derail meetings, projects, and entire close cycles. If the answer is "the report itself," that's the bug. The number exists where it gets shown, with no single source. Every consumer derives their own version because there isn't one to share.

A real reporting system has one true place for every number. The reports read from it. The dashboards read from it. The exports read from it. When somebody asks "is this right," the answer points to one place, not five.

It sounds basic. It's the first thing most operations get wrong, and the last thing they fix.

The number lives somewhere. Make sure it's only one somewhere.

If month-end close is a fire drill, the reporting system isn't a system.

I've sat through enough of them. Three days of recompiling, recoding, re-explaining. Somebody finds last month's numbers don't match this month's. Somebody else discovers a tab got overwritten. The CFO asks the same question the controller answered yesterday.

That's not reporting. That's an annual tradition that happens twelve times a year.

A real system makes month-end a print job. The numbers are already right. The work is just packaging them.

If the same people answer the same questions every month, that's not diligence. It's a missing feature.

Excel is not the enemy.

I spent a decade managing reporting at enterprise scale, and I still use Excel daily. For one analyst, one recurring report, or a quick model nobody else will touch, it's exactly the right tool. Fast, flexible, everyone already knows it.

It becomes the problem when it leaves that lane. When five people maintain "the same" workbook on five different laptops. When a number in one tab drives a decision and nobody can trace where it came from. When "fix Excel" is in the job description.

The tool isn't broken. The boundary around it is.

Use Excel for what it's good at. Stop asking it to do the job of a database, an audit trail, and an entire reporting org.

The best reporting system I ever built was the one nobody called me about.

Reports ran on time. Numbers matched. Executives found what they needed without asking. When I went on vacation, nothing caught fire.

That's the whole bar. Not dashboards. Not real-time. Not AI-powered. Just a system that keeps running when the person who built it isn't around.

If the operation needs the builder in the room, the builder built a job, not a system.

Every tool I already use shipped an AI feature this year.

Some of it is useful. Most of it is the same shoebox with a chatbot stapled to the lid.

A pile of mismatched data doesn't become a system because you can ask it questions in English now. It just answers in English. The wrong numbers come back faster and with better grammar.

AI is great at working with information that's already organized. It's terrible at organizing it for you. That part is still the work.

The shoebox didn't get smarter. It just got a co-pilot.

Three people. One question. Three different answers.

I've been in that meeting more times than I can count. Someone asks for last quarter's number, three departments pull their own version, and now the meeting is about the spreadsheet instead of the business.

Nobody is lying. Everyone is right inside their own file.

A reporting system isn't a tool. It's an agreement about which number is the number. The tool is just where the agreement gets written down.

If three people can produce three answers, the problem isn't the data. It's the absence of a system.

The difference between a shoebox and a filing system isn't the size of your business.

It's whether you can find what you need in under two minutes without calling someone who might remember where they put it.

I built systems at enterprise scale that answered that question. The same principles apply whether you're running a hospitality empire or a three-person operation.

The tools are actually cheaper and easier now than they've ever been.

The hard part was never the technology. It was admitting the shoebox wasn't working.

Every business has a shoebox. Most don't know it until they need something that's in it.

Tax time. An audit. A new hire who needs the history. A decision that needs last year's numbers.

That's when you find out your filing system was actually just a pile with good intentions.

I've watched it happen at enterprise scale. The chaos is the same whether the shoebox is a server room or a kitchen drawer.

Good intentions make terrible filing systems.

Shoebox is not a filing system.

I spent a decade managing reporting inside a major hospitality operation. We had servers, shared drives, databases, and a team of analysts.

We still had a shoebox problem.

Different container, same issue. Critical information living in the wrong place, in the wrong format, owned by the wrong person.

The scale changes. The box just gets a better label on it.

I've watched what happens when the person who owns the reports leaves.

It doesn't matter if it's a resignation, a promotion, or an acquisition that reshuffles the whole org. If your reporting lives in one person's head and their laptop, you don't have a reporting system.

You have a dependency.

I spent years inside operations making sure that when I walked out the door, the systems kept running. Most businesses never think about that until it's too late.

Congratulations. Your reporting system's name is Dave.

When I first started building reporting systems, I went looking for the right tool to replace Excel for complex business operations.

There are a dozen solid options. Each one built for a slightly different use case. Four hours of research later I understood why most people just stay with Excel.

That's not a tool problem. That's a selection and configuration problem.

The right answer depends on the data, the workflow, and what specifically breaks. The tools exist. Picking the one that fits a given business, and making it actually work, is the hard part.

The right tool is out there. It's just buried under eleven browser tabs and a free trial nobody remembered to cancel.

Excel is the most successful prototype that never got replaced.

Somebody built it on a Tuesday to solve a real problem. It worked. It kept working. Five years later it's still load-bearing, still undocumented, and still the thing the business actually runs on.

Every "we'll replace it next quarter" plan loses to the version that already runs.

Most businesses don't have a data problem.

They have a spreadsheet problem pretending to be a data problem.

I know because I've lived on both sides of it. A decade managing reporting inside a major hospitality operation taught me the difference.

A data problem means your information is wrong. A spreadsheet problem means your information is right: ten by ten or in ten different files, maintained by ten different people, 10 different ways, none of whom know the others exist.

One is a data quality issue. The other is a very organized shoebo… infrastructure problem.