From Manual Excel Reporting to Governed BI
Two versions of the same report, two different totals, and a meeting spent arguing about who was right. Now there is one number, and everyone trusts it.
The situation
Executive reporting at a produce company ran on heroics. Every week, analysts exported data from the ERP into Excel, repaired it by hand, rebuilt the same lookups, and assembled the pack leadership saw. The process consumed two full days of skilled time per cycle, and the result still couldn’t be fully trusted. Two versions of the same report circulated with different totals. Meetings opened with debates about whose figure was right. The people making eight-figure decisions were doing it on numbers with an asterisk.
What I did
I replaced the export-and-repair pipeline with governed business intelligence: reports that draw automatically from one controlled data layer instead of from whatever was exported that morning.
First I built the data foundation, pulling the authoritative records out of the ERP into a governed layer where every entity keeps one permanent ID and the data refreshes itself. Governed means the layer is read-only downstream: the numbers can’t be quietly edited on their way to a meeting. Then I rebuilt the executive reporting on top of it, working with leadership to define each measure once, in writing, so that “shipped,” “margin,” and “on-time” meant exactly one thing each. That definition work sounds small. It’s most of the battle.
I also trained the team to self-serve, so a question like “show me that by commodity” is a click, not a request that takes an analyst’s afternoon.
What changed
The weekly reporting cycle went from two days of manual assembly to essentially zero. The dueling-versions problem ended because there’s only one version. Executives stopped auditing the numbers and started acting on them, and the analysts who were rebuilding spreadsheets every week now spend that time on analysis the business had never had time for.