The Dashboard Built Before Anyone Asked What It Was For

Reuben Castagnetti is a freelance operations consultant who has helped set up financial dashboards for nine small businesses over the past four years. The pattern he sees most often is the same one: someone discovers that their accounting software has a dashboard feature, enables every available module, and calls it done. Three months later, the dashboard is open in a browser tab that nobody refreshes. It became wallpaper.

Data availability is not the same as relevance

The mistake is starting with what data exists rather than starting with what decisions need to be made. These are different questions. A business owner who needs to decide each week whether to take on new project work needs different numbers than one managing a retail operation with daily stock turnover. The same dashboard template serves neither well.

Questions worth answering before building anything

• Which financial decisions do you make weekly, and what information do they require?
• Which numbers, if they changed by 10%, would cause you to act differently today?
• Are there figures you currently calculate manually that take more than 20 minutes per week?
• Who else reads this data, and do their decisions differ from yours?

Reuben now runs a one-hour session with clients before touching any dashboard tool. He calls it a decision audit. The output is a list of no more than eight decisions the dashboard needs to support, each with a named metric attached. Every chart built after that session has a job. In his experience, dashboards built this way stay in active use. The ones built around available data tend to get abandoned within six weeks.