Confession: I used to build beautiful reports. Forty pages, every filter you could want, cross-tabs, drill-downs, the works. I'd send them out feeling very professional. Then I'd check: nobody opened them. Not the sales manager. Not the owner. Not even the person who asked for the report in the first place.
It took me an embarrassingly long time to learn the truth about business reporting: the best report is the one that gets read, and the one that gets read fits on one page.
Why the 40-Page Report Dies
I once watched an owner print a monthly sales report — all 40 pages — and use it as a monitor stand. I'm not exaggerating. It held up his second screen for two years. Best use that report ever got.
Long reports fail for three reasons:
They're built for the builder, not the reader. The person who builds the report loves detail — every dimension, every filter, every footnote. The person who reads it wants to know: are we okay? That's it. "Are we okay" is a one-page question.
They bury the decision. Page 37 might contain the critical insight — inventory of the top seller is about to stock out. But nobody reaches page 37. If the decision isn't on page 1, the report has no decision. It's a document, not a tool.
Precision nobody needs. The report shows revenue to the penny: $1,247,338.19. The owner needs to know: "about $1.25M, up from last month." All those decimal places aren't accuracy — they're noise that slows down reading.
The One-Page Format
Here's the format I use now for every recurring report. One page. Five sections. Takes me 20 minutes to build, and people actually read it:
1. The headline (one line). "September: $1.25M revenue, up 8% vs August, 3% above target." If they read nothing else, they know if we're okay.
2. Three numbers that moved. Not thirty. Three. Revenue, margin, and one operational metric (on-time delivery, inventory turns, open tickets — whatever runs your business). Each with a vs-last-month arrow. That's it.
3. One thing that's off track. The single issue that needs attention. Stock-out risk on the top product. A customer 60 days past due. Pick ONE. If everything's on fire, pick the biggest fire — the report isn't the place for the full incident list.
4. One decision needed. "Approve the $12k expedite fee to avoid the stock-out? Yes / No." Reports that end with a decision get replies. Reports that end with data get monitor stands.
5. The appendix link. "Full detail here →" with a link to the 40-page version. It exists for the one person who wants it. Everyone else gets the page.
How to Build It in Your ERP
In Odoo, this is a dashboard: one dashboard, five KPI cards and a list view. Twenty minutes. Set it as the default view for the sales manager so it's the first thing they see, not the fortieth thing they ignore.
In SAP Business One, use the dashboards and KPIs in the web client, or a single Crystal/XL Reporter template with the five sections. The XL Reporter version is nice because the owner can refresh it themselves without calling you.
In a spreadsheet (no judgment — we all start somewhere): one tab, five boxes, conditional formatting for the arrows. Print it. Put it on the owner's desk Monday morning. Watch what happens.
The tool doesn't matter. The discipline matters: one page, five sections, one decision.
The Real Lesson
I spent years thinking my job was to provide information. It's not. My job is to provide CLARITY. Information is the 40-page report. Clarity is the one page that makes someone say "got it" and act.
Next time someone asks you for a report, ask them back: "What decision will this help you make?" If they can't answer, they don't need a report — they need the one-pager. Build that instead, and watch your reports go from monitor stands to Monday morning rituals.
— Penny, keeping the paperwork honest at Dead Brands
Want help with your ERP? Book a call with David — he'll find the reports nobody reads and replace them with ones that work.
Deadbrands.co merch: for people who read the whole thing. (You know who you are.)
