Francesco Gizzi
Data
Business KPIs and dashboards: how to choose them and use them to decide
Almost every company I work with has numbers. Many also have a dashboard. Few really use it. It gets opened on meeting day, scrolled through quickly, the oddest figure gets a comment, and then decisions are made as always: on experience, on gut feeling, or by siding with whoever speaks loudest.
The problem is almost never the tool. Business KPIs and dashboards are usually built starting from the data available, not from the decisions to be made. Or the tracking underneath is fragile and nobody trusts the numbers. Or the same screen tries to serve the owner, marketing and sales, and ends up serving no one.
In this guide you will find the method I use with SMEs, startups and scale-ups: how to choose KPIs, how to make tracking reliable, how to structure a dashboard for management, marketing and sales, how to build reporting the team actually reads, which tools to consider and which mistakes to avoid.
KPIs and dashboards: what they are for and how to choose indicators
What they are really for
A KPI is an indicator linked to a measurable goal. A dashboard is the way those indicators become readable at a glance for the people who have to decide. That is all. If a number is not tied to a goal, it is a metric. If a dashboard does not help you understand where to act, it is decoration.
Being a data-driven company does not mean having more reports. It means that important conversations start from a shared basis. When the system works, the effects show up quickly:
- meetings get shorter, because nobody argues anymore about which number is the right one;
- marketing, sales and management read the same data with the same definitions;
- problems surface weeks earlier, when fixing them costs less;
- budget and people move towards what pays off, not towards what makes the most noise.
Working every week, for a consulting firm, with more than 25 companies on marketing, business development, sales and data, I have seen the same dynamic repeat itself across very different industries. The companies that make better decisions rarely have more data than the others. They have fewer numbers, better chosen, and a habit of reading them together.
Where a good KPI comes from
Choosing KPIs is the step that determines everything else. I always start from three questions: what goals the company has for the next 12 months, what recurring decisions it has to make to reach them, which numbers would change those decisions.
The criteria for a good KPI
An indicator deserves a place on the dashboard if it meets these criteria:
- it is linked to an explicit goal, with a target value;
- it has a written definition, the same for everyone: what is counted, from which source, how often;
- it has an owner who can influence it through their own work;
- if it gets worse, someone already knows what to do;
- it updates without hours of manual work.
When an indicator does not pass this filter, it should not be thrown away. It can sit in an operational view or an in-depth analysis. It is simply not a management KPI.
Leading indicators and outcome indicators
Revenue and margin are outcome indicators: they tell you how things went. They are necessary, but they arrive late. Alongside them you need leading indicators, which move earlier: quote requests, meetings booked, weighted pipeline, proposal conversion rate, active customers. A good dashboard keeps both families together, so management sees both the result and what is building up to it.
How many KPIs? For management, between 6 and 10. For each department, roughly the same. If you need more, a hierarchy is usually missing. I explored the topic of selection in depth in how to read the right KPIs without useless reporting.
Reliable tracking: the foundation nobody sees
An elegant dashboard does not fix fragile tracking. As a company grows, channels, tools and people entering data multiply, and trust in the numbers tends to fall. If the team does not trust the numbers, it stops using the system and goes back to its own files. At that point every department has its own version of the facts.
Tracking errors almost always stem from small inconsistencies that pile up:
- conversions defined differently across the website, ad platforms and CRM;
- campaign parameters used without a naming convention;
- optional CRM fields, half filled in or filled in differently by each salesperson;
- changes to the website or contact forms made without checking that tracking still works;
- no one responsible for data quality.
The solution is to treat tracking, dashboards and reports as a single chain. Three things are needed. A written measurement plan, stating which events are tracked, under what names and from which source each KPI is taken. A single source of truth for each number, for example the ERP for revenue and the CRM for the pipeline. And a periodic check, even just monthly, that compares sources and flags differences. Data problems are often the symptom of poorly defined processes: fixing the process comes before fixing the chart.
How to structure a dashboard for management, marketing and sales
The most frequent mistake is a single dashboard for everyone. The owner needs a summary, marketing needs channel detail, sales needs visibility on the pipeline. Three linked views built on the same underlying data are better than one endless screen.
Management dashboard
A single screen, readable in a few minutes. Revenue and margin against budget, projected cash, two or three leading sales indicators, average customer acquisition cost, a service quality indicator. Every number shows the expected value and the variance.
Marketing dashboard
Leads generated by channel, cost per lead, lead-to-opportunity conversion rate, customer acquisition cost, return on spend calculated on margin. The key point is to connect marketing to what happens next, in sales. A channel that brings in lots of leads but no contracts is not a good channel.
Sales dashboard
Pipeline by stage with weighted value, stage-to-stage conversion rates, average time to close, average contract value, activity per salesperson, closing forecast for the month and the quarter.
Some design rules apply to all three:
- each dashboard answers one main question, written at the top;
- the most important numbers sit at the top left, where the eye starts;
- every KPI is compared with a target or with the previous period;
- few elements per screen, no endless scrolling, colors used only to flag variances;
- you can drill down from the summary figure into detail, but the detail lives in a separate view.
If you are interested in the specific case of sales and marketing, here I explain how I set up a KPI dashboard for marketing and sales.
Useful reporting and tools
From dashboard to decision
Dashboards and reports are not the same thing. The dashboard is for seeing quickly. The report is for interpreting: what happened, why, what we do about it. A report without commentary informs, but rarely guides.
A monthly report that works has a simple structure: a summary page with the three main messages, the relevant variances with their explanation, the actions decided and their status. The rest is appendix. It must also be sustainable. If producing it takes two days of copy and paste, sooner or later it will stop coming out. Automating data extraction frees up time for the only part that really matters: the reading.
The cadence needs to be designed too: weekly for operational marketing and sales indicators, monthly for margins and results, quarterly to review goals and KPIs. For the financial side, this routine fits in with management control for SMEs.
Which tools you need
There are many solutions, from spreadsheets to business intelligence platforms, to dashboards built into CRMs and ERPs. The choice comes after the logic, never before. In general:
- a structured spreadsheet is perfectly fine to start with, with a few KPIs and data updated once a month;
- the native reports in your CRM, ERP and ad platforms are useful for department views, less so for bringing different sources together;
- a business intelligence tool is needed when there are many sources, frequent updates and a growing number of readers;
- a centralized data warehouse makes sense when the company wants a single version of the numbers from many different sources.
The criterion is simple: choose the lightest tool the team can keep up to date. A powerful tool fed with unreliable data is worse than a tidy spreadsheet.
A practical example
Let's take a hypothetical case: a B2B company selling management software, with 20 people. It has a CRM, an ERP, the ad platforms and an Excel file the owner updates on Sunday evenings. Marketing says leads have grown by 30%. Sales says the leads are terrible. Revenue is flat.
The work starts with defining the KPIs: what a qualified lead is, when an opportunity enters the pipeline, how acquisition cost is calculated. Then the tracking is fixed: the same naming convention for campaigns, lead source mandatory in the CRM, a link between first contact and signed contract. Only at the end are the three views built: management, marketing, sales.
After a couple of months of clean data the picture changes. One channel generates half the leads but almost no contracts. Another, more expensive per lead, has the lowest acquisition cost per customer. The budget shifts accordingly and the discussion between marketing and sales changes tone, because at last everyone is talking about the same numbers. It is the same principle I apply to campaigns: with a company in the financial sector we achieved +110% ROI on online campaigns in 3 months, and a result like that can only be measured and defended with a reliable data system.
Mistakes to avoid
- Starting from the tool. You choose the platform and then look for what to put in it. The result is a full and useless dashboard.
- Measuring what is easy instead of what matters. Impressions, followers and email opens are useful in the detail, rarely at management level.
- Too many KPIs with no hierarchy. Forty numbers on the same level are the same as no numbers.
- Different definitions across departments. If "active customer" means two different things, every meeting turns into an argument about the data.
- Ignoring data quality. A single error discovered in a meeting is enough to lose trust in the whole system.
- No benchmark. A number without a target or a previous period does not tell you whether things are going well or badly.
- No time set aside for reading. A dashboard nobody discusses in meetings dies within a few months.
Where to start
You do not need to redo everything. In most cases it pays to start from what exists: understand where the data chain breaks, cut KPIs down to the ones you really need, build a first management view and a review routine. The rest is added step by step.
With clients I usually start from an initial audit of sources, tracking and reporting, to understand which numbers are reliable and which decisions are currently being made without a basis. From there we build KPIs, dashboards and reporting together through my data, KPI and dashboard consulting. I work in person in Rome and remotely across Italy: if you feel your company has enough numbers but not enough clarity, write to me and let's see where to start.
FAQ
How many KPIs should a management dashboard have?
Generally between 6 and 10. They must be linked to explicit goals and have an owner. Other indicators can sit in department or in-depth views.
Do you need a different dashboard for each department?
In most cases, yes. Management needs a summary, marketing and sales need more detail. What matters is that all views start from the same data and the same definitions.
Can a dashboard replace the monthly report?
Not entirely. The dashboard is for reading quickly, the report is for interpreting variances and setting actions. They work best together.
When should tracking be reviewed?
When sources give different numbers for the same thing, when the team does not trust the data or when decisions are made ignoring the existing system.