Plenty of companies have a business dashboard that took weeks to build and is opened by almost nobody. It has 40 charts, three date filters and a number in the corner that does not match the accounts. The team goes back to asking someone to “send the numbers” on WhatsApp. This article covers the mistakes that make dashboards go unused and a step-by-step way to build one your team will open every week, whether you use Looker Studio, Power BI, a spreadsheet or a custom web app.
Why dashboards get ignored
Most unused dashboards fail for one of a handful of reasons. They are worth checking against any dashboard you already have.
- Nobody asked for it. The dashboard was built because the tool made it easy, not because someone had a decision to make.
- Too much on one screen. When everything is shown, nothing stands out, and people do not know where to look.
- The numbers do not match other sources. One mismatch with the accounts or the CRM and trust is gone.
- It is slow or hard to reach. If it needs a separate login, a VPN and two minutes to load, people will not bother.
- No one acts on it. If no meeting or routine uses the dashboard, it becomes decoration.
Step 1: start with decisions, not data
Before you open any tool, write down who will use the dashboard and what they decide with it. “The sales head decides each Monday which leads to chase and which campaigns to pause.” “The founder decides each month whether to hire another technician.” Each decision points to a few numbers that matter. Everything else can live in a separate report or be dropped.
A useful test: for every metric you plan to show, ask “If this number went up or down sharply, what would we do differently?” If the answer is “nothing”, leave it out.
Step 2: define every metric in writing
Write a short definition for each number: what it counts, where the data comes from, how often it updates and what it excludes. “Revenue: invoiced amount excluding GST, from the accounting system, by invoice date, updated daily.” Agree these with finance and sales before you build. Most dashboard arguments are about definitions, and it is far cheaper to settle them on paper than after launch.
Keep the definitions visible, either on the dashboard itself as short notes or in a linked page.
Step 3: limit each business dashboard to one screen
Aim for five to eight numbers on the main view, arranged so the most important sits top left, where people look first. Show each against something that gives it meaning: last month, the same month last year, or a target. A number on its own says little. “₹18 lakh revenue” means more as “₹18 lakh, 12% below target”.
Choose simple charts. A line for trends over time, a bar for comparing categories, a single big number for a headline figure. Avoid 3D effects, pie charts with many slices and gauges that take up space for one value.
If people need more detail, add a second page they can click into. The first screen should answer “are we on track?” in under ten seconds.
Step 4: fix the data plumbing first
A dashboard is the visible end of a data pipeline. If the CRM has duplicate contacts or the sales team logs deals in a spreadsheet on the side, the dashboard will be wrong no matter how good it looks. Before building, check:
- Does each number come from one agreed source?
- Is the data entered consistently, with required fields filled in?
- Does it refresh automatically, or does someone have to upload a file?
- Will someone notice if the refresh fails?
Manual uploads are a common weak point. The person who does them goes on leave, the dashboard freezes, and nobody notices for three weeks. Automate the refresh where you can, and show a “last updated” time on the page.
Step 5: put it where people already are
Adoption depends more on placement than on design. Some ways to make a dashboard part of the routine:
- Open it at the start of the weekly team meeting and work through it on screen.
- Send a scheduled summary by email or to a team chat channel with the three headline numbers and a link.
- Make it the browser home page for the people who use it most.
- Set alerts for thresholds that matter, such as cash below a set level or leads dropping sharply, so people get the message without opening anything.
Step 6: review it after a month
Most tools show how often a dashboard is viewed. After four weeks, check who opened it and which pages they used. Ask the main users what they still find themselves asking for by message. Remove charts nobody looks at, and add the questions people keep asking. A dashboard is never finished; it should change as the business changes.
An example layout
Say a Pune bakery chain with four outlets wants a weekly view for the owners. A one-screen version might show:
- Sales this week by outlet, against the same week last month
- Gross margin percentage, against target
- Wastage as a share of production, by outlet
- Online orders and average order value
- Cash in bank against the minimum the owners want to hold
Each number has a short definition. The dashboard refreshes from the point-of-sale system and the accounting software each night, and a summary goes to the owners’ group every Monday morning. Wastage per outlet is the number they act on most, because it tells them where to adjust production.
Spreadsheet, BI tool or custom build?
A well-built spreadsheet is fine for a small team with one or two data sources. Business intelligence tools such as Looker Studio or Power BI suit teams with several sources and a need for scheduled refreshes and sharing controls. A custom dashboard inside your own app makes sense when customers or field staff need to see it, or when the logic is specific to your product. Our web app and SaaS work covers custom builds, while connecting sources and automating refreshes is part of our automation work.
If your team still asks for numbers by message, a free call can help you work out why.
Frequently asked questions
How many metrics should a dashboard have?
For a main dashboard, five to eight numbers is a sensible limit. That is enough to show whether the business is on track without burying the important figures. If people need more detail, put it on secondary pages they can open when they need it. Each metric should connect to a decision someone makes regularly; if it does not, remove it.
What is the difference between a dashboard and a report?
A dashboard is a live or regularly refreshed view of a few key numbers, meant to be checked often and at a glance. A report is usually a fuller document for a specific period or question, such as a monthly board pack or a campaign review. Many teams need both: a dashboard for weekly decisions and reports for deeper analysis.
How do I get my team to use the dashboard?
Build it around decisions they already make, keep the main view to one screen, and make sure the numbers match the sources they trust. Then build it into a routine, such as opening it at the weekly meeting or sending a scheduled summary to the team channel. Check usage after a month and remove anything nobody looks at.