We need a dashboard for that!

20 October 2026

It’s a familiar response when a business wants better visibility of its performance. Perhaps sales are slowing, costs are increasing or a team is struggling to keep track of its workload. A dashboard feels like a sensible next step: bring the information together, add some charts and make it easier to see what’s happening.

It may well be the right answer. But before anyone starts building it, there’s a more useful conversation to have. What does the business need to understand, who needs that information, and what will they do with it?

The dashboard is the presentation layer

A dashboard presents a selected view of the data. Through measures, trends, comparisons and layout, it tells a story about something the business needs to understand. The choices behind that presentation matter: what we include, what we leave out, which period we compare and what we identify as good or poor performance all influence how someone interprets the result.

Underneath that presentation sit the data, relationships, definitions and business rules that give the numbers meaning. A sales figure might look straightforward, but does it represent orders received, invoices raised or payments collected? Does it include cancelled orders, returns and VAT? Are we comparing it with a target calculated on the same basis?

Those questions need answers whether the final output is a dashboard, a report or a spreadsheet. Choosing a chart cannot resolve an unclear definition. In tools such as Power BI, the distinction is visible in the architecture: report visuals query an underlying semantic model, which supplies the relationships and calculations used to interpret the data.

So, what’s the difference between a dashboard and a report?

The terms overlap, and businesses often use them interchangeably. A useful distinction is their purpose. A dashboard generally helps someone monitor a situation and identify where attention is needed. A report provides more room to explore the detail, explain findings or communicate a particular view of the business. Tableau’s overview makes a similar distinction between a high-level dashboard and a more focused, detailed report.

A dashboard might help a sales director see that revenue is below target and that the gap has widened over the last three months. A supporting report might break that performance down by customer, product, region or transaction, helping the team investigate what sits behind the headline.

That doesn’t mean dashboards cannot contain detail or reports cannot be interactive. Neither is automatically real time, and both can be reviewed regularly. The distinction is less about the software or format and more about what the reader needs to accomplish. Individual platforms also have their own definitions of these terms, so it helps to be clear about whether we are discussing the business purpose or a particular software feature.

The same data can support different stories

Imagine a business whose sales are ahead of last year. A dashboard showing total revenue and year-on-year growth could reasonably suggest that performance is improving. Add the target, however, and it becomes clear that the business is behind its plan. Introduce margin, and the picture changes again: revenue has grown, but the additional sales are generating less profit.

A detailed report might then show that growth is concentrated in a few heavily discounted products, while several established customers are buying less. That gives the sales team something specific to investigate, although understanding the reasons may still require conversations with customers and colleagues.

Each view uses related data, but answers a different question. The dashboard helps people recognise where to look. The report helps them examine what is happening. Neither tells the whole story simply because the numbers are accurate.

Start with the question behind the request

When someone asks for a dashboard, it is worth understanding what prompted the request. Which decision is difficult today? What information is missing? How quickly does someone need to know when something changes, and what level of detail would help them respond?

The answers shape more than the visuals. They influence which data is needed, how measures should be defined, how frequently information should be refreshed and who needs access to it. They also help establish whether the business needs an overview, a detailed report, alerts or a combination of those things. This is consistent with Tableau’s dashboard design guidance, which starts with understanding the purpose and audience before designing the presentation.

Sometimes that conversation reveals that an existing report could answer the question with a small change. Sometimes it exposes gaps in the underlying data or disagreement about what a measure means. Those are useful discoveries to make before investing in another screen.

What should change once it exists?

A useful dashboard makes something easier to understand and act on. Its value comes from the decisions it supports and the work it helps people do.

At Node9, that is where we start: understanding the business question, establishing what the information needs to mean and then deciding how best to present it.

The next time someone says, “We need a dashboard for that,” ask them to explain what they need it to help them understand. That conversation is the beginning of building something useful.