Every month, someone in your company spends two or three days pulling numbers into a spreadsheet, formatting it, and emailing it to leadership. Leadership skims the first page and moves on. By the time anyone reads it, the data is already three weeks stale. This ritual feels like management. It is mostly theater.
Moving from spreadsheet to dashboard reporting is supposed to fix this. But most dashboard projects fail in a specific, predictable way: they replace one unread document with a busier one. Forty charts, twelve tabs, every metric anyone ever mentioned, and still nobody checks it because there is no signal in the noise.
The problem is never the tool. It is the lack of a constraint. A dashboard that shows everything decides nothing. Here is how to build one people actually open.
Pick five numbers, not fifty
The single most important rule: a dashboard is limited to the numbers that change what someone does today.
Not the numbers that are interesting. Not the ones that are easy to pull. The ones where, if the value moves, a specific person takes a specific action. If a metric changing would not cause anyone to do anything differently, it does not belong on the dashboard. Put it in an archive if you must, but keep it off the screen.
For most small and mid-size businesses, five metrics carry almost all the decision weight. For a distributor, they might be:
| Metric | The decision it drives |
|---|---|
| Cash on hand | Do we pay suppliers now or wait? |
| Orders today vs. target | Do we push sales this afternoon? |
| Stock below reorder point | What do we buy this week? |
| Overdue receivables | Who do we chase today? |
| Order error rate | Is the process breaking? |
Five numbers you check every morning beat fifty you review once a quarter. The constraint is the value. When someone asks to add a sixth chart, the right question is: what will you do differently when it moves? If there is no answer, it stays off.
Automate the refresh or it dies
A dashboard that someone has to update by hand is just a spreadsheet with nicer colors. The moment refreshing it becomes a chore, it goes stale, and a stale dashboard is worse than none because it quietly misleads.
The whole point is that the numbers update themselves. That means connecting the dashboard to where the data actually lives: your order system, your accounting software, your point of sale. If those systems do not talk to each other today, that is the real project, and I wrote about it in System Integration Explained: Making Your Tools Talk.
If your data still lives entirely in spreadsheets, you will hit a wall fast, because spreadsheets were never built to be a live data source for other tools. That breaking point is covered in Google Sheets as a Database: Where It Breaks.
Put it where people already look
The best dashboard in the world fails if opening it requires logging into a separate system nobody remembers. Behavior beats intention. People check what is in front of them.
So meet them where they are:
- A screen on the wall in the operations room, always on.
- A single link pinned in the WhatsApp group leadership already uses all day.
- A short automated message every morning: "Cash: Rp 340M. Orders: 62% of target. Overdue: Rp 88M."
That last one matters more than people expect. A dashboard you have to remember to visit gets visited less each week. A number that arrives on your phone at 8 a.m. gets seen. Push beats pull for anything you want checked daily.
Cheap tools that get you there
You do not need an expensive business intelligence platform to start. For most Indonesian SMEs, the honest options are:
- Google Looker Studio (formerly Data Studio). Free, connects to Google Sheets, most databases, and many ad platforms. If your data is already in Google's ecosystem, start here. It is genuinely good enough for the five-number dashboard.
- Metabase. Open source, you can self-host it, connects straight to your database, and non-technical staff can build their own views. My default recommendation once your data lives in a real database.
- A simple custom page. If you already have a web app running the business, a single dashboard page reading from the same database is often the cleanest path, because there is nothing new to maintain.
Start with the free option and the five metrics. Prove people check it daily. Only then consider spending money. Buying a powerful platform before you know which five numbers matter is how dashboard projects turn into shelfware.
Kill the monthly report ritual
Here is the part that makes this stick: once the live dashboard is trusted, retire the manual monthly report entirely.
This is the hard conversation, because someone's job has quietly become producing that report, and it feels like admitting the work was busywork. Reframe it. Those two or three days a month are freed up for analysis instead of assembly. The person who used to compile numbers now asks why the numbers moved, which is worth far more.
If you keep both the manual report and the dashboard, people default to the familiar one and the dashboard withers. Pick the live version and commit. A tool that saves quiet, recurring hours like this is exactly the kind of unglamorous win I described in Internal Tools: The Quiet ROI Nobody Puts on LinkedIn.
The takeaway
The move from spreadsheet to dashboard reporting is not about prettier charts. It is about picking the five numbers that drive decisions, making them refresh themselves, and putting them where people already look, so the data is fresh enough to act on and simple enough to read.
Start this week. Write down the five numbers that would change a decision today, and build the smallest possible view of just those. You can always add later, but you will rarely need to. The discipline of five is the whole trick.