What exactly is a Power BI dashboard?
In everyday language, any screen with numbers and charts in Power BI is a dashboard. Microsoft does make a distinction (checked on 6 November 2026):
- A report can have several pages and you can filter and click through it. You build it in Power BI Desktop or in the online service.
- A dashboard is officially one page of tiles that you pin from one or more reports. It only exists in the online service. You cannot filter it, and you cannot create it in Power BI Desktop.
So what an SME calls a dashboard is usually a report with an overview page. That is how we use the word in this article too. The official dashboard is useful if you want numbers from different reports on one screen, or if you want an alert when a number crosses a threshold. That works on dashboard tiles, and only for cards, KPIs and gauges.
Who is it for and at what moment?
Ask three questions before you create a chart:
- Who opens it? A managing director, a team lead and a finance employee each want to see something different. Choose one main user per dashboard.
- When do they open it? At the Monday meeting, at month-end close, or every morning before planning? The more concrete the moment, the more likely it is to happen.
- Which decision depends on it? "Which projects do we need to adjust this week?" is a good question. "How is revenue doing?" usually gets you little more than a nod.
If you cannot answer these, it is too early to build. Which numbers belong on it is covered in the 10 KPIs every SME dashboard needs. If you have nothing in place yet, start with Power BI for SMEs, which explains what you need to get going.
Which pages does a good Power BI dashboard have?
For most questions this is enough. It is our experience rather than a law, so feel free to drop what you do not need.
- Overview. A few key numbers with a comparison, and the trend over time. After half a minute you know whether something is wrong.
- Analysis. The same numbers split by what matters to you: customer, project, branch or employee. This is where you find out where a deviation comes from.
- Detail. A list of the rows underneath, such as invoices, orders or projects. This is where the concrete action comes from: call this customer, look at this project.
- Notes. What each number means, which system it comes from and who to call if it is wrong. This page is not exciting, but it saves a lot of debate.
If someone wants to go from the overview to one customer or project in one click, you can do that by clicking through to a detail page (in Power BI this is called drillthrough). That keeps the overview calm.
If two groups really need to see different things, build two dashboards on the same data model rather than one dashboard with ten pages. The definitions stay the same while each group has its own way in.
How do you set up the overview page?
Microsoft's design tips are written for dashboards, but they also work well for the first page of a report:
- Put the most important thing at the top left and move towards more detail from there, in the direction you read.
- Keep everything on one screen. If you have to scroll to see it, there is too much on it.
- Use cards for the key numbers and give them context. "€84,000" says little, "€84,000, which is 6% below budget" says something.
- Choose boring charts. Bars and columns for comparing, sorted by value, and no 3D. According to Microsoft, use a pie chart only with fewer than eight categories, and we would stay well below that ourselves.
We add two things of our own. Only use colour when there is an agreed target behind it: red then means someone has to do something. And show the date of the last refresh on the page. Anyone who cannot see how old a number is will go and check it somewhere else anyway.
Do people mostly look on their phone? Then you can create a separate mobile view per page. Note that you only see it in the Power BI app for iOS and Android, and only with the phone upright. In a web browser you always get the standard view.
What makes sure a dashboard actually gets used?
This is the part that often gets forgotten at handover. Five things that help:
- Check the numbers before anyone sees them. Compare them with your accounts and investigate every difference. One wrong number in the first demo sticks for a long time.
- Give it a fixed place in a meeting. Put it on the screen at the start of the meeting, instead of an Excel list or a verbal update. After that, nobody needs convincing any more.
- Bring it to people. With an email subscription, someone receives a snapshot in their inbox at a fixed time, for example every Monday at eight. That requires a Pro or PPU licence. On dashboard tiles you can also set an alert for when a number crosses a threshold, but it only works after a refresh and only you can see your own alerts.
- Appoint an owner. Someone who knows the process, answers questions and decides what gets added. This does not have to be a technical colleague, but it does have to be someone's job.
- Measure whether it gets used. Power BI has a usage report with views per report and per page. It shows the last 30 days and has preview status. You need a Pro or PPU licence and edit rights on the report, your admin must have enabled it and it does not work in My Workspace.
That usage report is handy for tidying up after a few weeks. A page nobody opens can go. If everyone goes straight to the detail page, your overview is probably not what people are looking for.
An example: the Monday meeting at a cleaning company
A fictional example. A cleaning company with forty employees and three team leads reviews the week every Monday. Accounting and time tracking sit in separate systems, and the question is: at which sites are the hours getting out of hand?
- Main user: the operations manager, who chairs the Monday meeting.
- Overview: hours planned versus worked this month, revenue versus budget and the number of sites more than 10% over, plus the trend per week.
- Analysis: overruns per team lead and per site, reachable by clicking from the overview.
- Detail: the time entries of one site over the last four weeks.
- Notes: what counts as a worked hour, what happens to sick hours and who manages the numbers.
The first check reveals that one team books sick hours to sites. They fix that first. After that the dashboard goes on the screen every Monday and the team leads receive a subscription email beforehand. After four weeks the usage report shows that nobody opens an extra page on material costs. It gets removed, and the meeting is now about three sites rather than about whose list is right.
Why does a Power BI dashboard not get used?
These are the causes we come across most often:
- One dashboard for everyone. The result is a screen where each department needs a piece and nobody needs the whole. One main user per dashboard prevents that.
- Adding every request straight away. After six months there are twelve pages. Agree that something comes out when something goes in.
- Filters as a fix for an unclear question. Ten filters above a page means the user has to find the answer themselves. Choose a default view that already answers the question.
- No target. A number without a comparison does not lead to action. Decide what good looks like for each key number.
- A refresh that fails unnoticed. After a few days of old numbers, people drop off. Agree who gets the alert and what they do then.
- Everyone exports to Excel. That is no disaster, but it is a signal. Ask what they do with the numbers there. Often a detail page or a breakdown is missing that you can easily add. Not sure whether you are ready for Power BI at all? Read Excel or Power BI.
The data underneath can be the cause too. If the numbers come from separate exports, the dashboard is only as good as the person updating them every week. Then you start with fixed integrations or with data engineering.
Help with your Power BI dashboard
We build Power BI dashboards for SMEs, on the data you already have. We start with a free introductory conversation about your question and the decisions that depend on it. You then receive a proposal with a fixed price per phase, so you can start small. We check the results together with your team, and at handover you get documentation, an explanation and access and admin rights.
Read more about dashboarding and our approach. Would you rather know first what to look for when choosing a partner? See Hiring a Power BI consultant.
