Board week arrives and the same ritual begins: a small team disappears into a war room to assemble the number — pulling exports, reconciling versions, arguing about which system is right — and emerges days later with a forecast nobody fully trusts, least of all the buyer who'll eventually diligence it.
The reflex is to buy clarity: a new BI tool, a warehouse project, one more dashboard layered on top. It rarely changes anything, because a dashboard is a window, and the problem isn't the window.
The pattern underneath
The forecast is a guess because its inputs are reconstructed by hand every cycle, from systems that don't agree, by people who won't be available next quarter. The number isn't wrong because it's badly displayed; it's wrong because it's stale the moment it's assembled, and there's no trail explaining how it was built. A prettier dashboard on hand-assembled inputs is just a faster way to be confidently wrong.
A dashboard is a window. If the inputs are reconstructed by hand each quarter, you've only bought a clearer view of a guess.
The fix is to make the number a by-product instead of a project: a system that assembles the metric continuously from source, reconciles the disagreements with a rule instead of a meeting, and leaves an auditable trail of how it got there. The war room disappears — not because the team got faster, but because the number was already standing when they walked in.
A number that defends itself is worth more than a number that merely looks good. One compounds into the exit; the other gets rebuilt every ninety days.
The fastest way in is to point at the leak you feel — at whatmovesit. You'll get the honest read: what it is, whether software actually fixes it, and how far it moves.
Point at your leak