Building a Management BI Dashboard: From Data to One Screen Your Leadership Team Actually Uses

A management BI dashboard pulls the company's KPIs automatically from ERP, CRM and production systems and shows them on one screen, calculated by the same rule for everyone. Choosing the indicators is only half the job: data sources, refresh rates, the one-screen layout, drill-down, threshold colours, a definitions glossary and access rights have to be designed together.

What really happens in the management meeting

It is the first Monday of the month. Finance brings a revenue figure from the ERP, sales brings a different one from the CRM, and the gap comes down to how returns and uninvoiced orders are counted. The production manager's OEE table is last week's spreadsheet. The first half hour goes on "which number is right?", and the decision is pushed to the next meeting.

Three problems usually sit behind this:

• Too many indicators. Forty charts added "just in case" make it unclear what to look at. A dashboard that shows everything highlights nothing.
• No shared definitions. Terms such as "revenue", "active customer" or "on-time delivery" have no single written definition, so every department does its own calculation. When the same customer has separate records in the CRM, the online shop and the helpdesk, merging them into one profile to count "active customers" is the job of a customer data platform (CDP).
• Manual feeding. The data depends on someone exporting and merging it in Excel. When that person is on leave the report is late; when a formula slips, the number is wrong. We list the typical warning signs in outgrowing spreadsheets for business tracking.

That is why a dashboard project starts not with choosing software but with the question "what does management need answered every week?" We cover the move from monthly spreadsheet reports to automated reporting in from Excel reports to BI; when you reach the point of comparing products, how to choose a BI tool helps you weigh licensing, connectors and permissions.

The cost of not fixing it

In Türkiye, business intelligence is still the exception rather than the rule:

According to TurkStat, in 2025 28.3% of Turkish enterprises with 10+ employees used ERP software, 12.0% used CRM and only 6.5% used business intelligence (BI) software. (TurkStat ICT Usage Survey in Enterprises 2025)

The gap widens with company size: the same survey found BI in use at 35.1% of enterprises with 250+ employees but at only 4.9% of those with 10-49. Many companies with an ERP have their data recorded, but it does not come back to management as decision support; it is still copied into spreadsheets to be reported.

The cost of deciding on wrong or late numbers is hard to measure, but it is not small. Data quality expert Thomas C. Redman estimates the cost of bad data at 15% to 25% of revenue for most companies (MIT Sloan Management Review, "Seizing Opportunity in Data Quality", 2017). It is an expert estimate, but the direction is clear: a company answering the same question with two different numbers spends its time reconciling rather than deciding.

There is a people angle too. TurkStat reports that in 2026 only 15.2% of Turkish enterprises employed ICT specialists, and 31.7% of those that tried to recruit them in 2025 reported difficulties (TurkStat ICT Usage Survey in Enterprises 2026). If reporting depends on one person's spreadsheet skills, reporting stops when that person leaves. The weekly cash spreadsheet is the classic example; we explain how to connect it to source data in cash flow reporting automation.

Where do the indicators come from?

A dashboard is only as good as the indicators on it. Which KPIs make the screen is derived from goals: one outcome measure per goal, one or two measures that signal it in advance, and a written definition, owner and threshold for each. We set out that selection method step by step in how to set KPIs, and cover the indicator set for sales teams separately in sales dashboard metrics. This article focuses on turning a chosen set of KPIs into a screen management opens every day.

How to build a management dashboard: 7 design decisions

1. Data source: one official source per KPI. Each indicator is calculated from data pulled automatically from the ERP, CRM or MES, not from a hand-built file. Where several systems need combining, the data is first consolidated through a data warehouse and ETL process. Whether transformation happens before or after loading is decided by the difference between ETL and ELT. Feeding one KPI from two sources simply moves the meeting-room argument onto the screen.
2. Refresh rate: matched to the speed of the decision. Operational KPIs such as stock and orders refresh within minutes or hours, finance daily, strategic indicators weekly or monthly. Refreshing too often loads the live system; refreshing too rarely turns the dashboard into a month-end report. A "last updated" time sits next to every KPI. Which metrics genuinely need to be live is covered in detail in real-time reporting. Second-by-second machine and sensor readings belong in a time-series database for sensor data rather than relational tables, and reach the dashboard as summaries.
3. The one-screen rule. The executive summary fits on one screen without scrolling: 6–10 indicators, with the most critical one top left. Each shows the figure, target, previous period and a trend line. Adding a KPI means removing another, which keeps the screen lean. On the customer side a single satisfaction measure is usually enough; we explain how NPS is measured in a separate guide.
4. Drill-down. One click takes you from the summary to a department, then to a customer, product or line, and finally to the invoice or work order. A number you cannot drill into starts the argument all over again. Plan the drill-down path at the start, because it shapes the data model. If customer and product codes differ between systems the breakdowns will not add up; that matching is solved through master data management (MDM).
5. Threshold colours and alerts. The KPI owner sets the green, amber and red thresholds; colour is a decision signal, not decoration. A KPI that turns red notifies its owner, so managers do not have to open the dashboard every day. For unusual deviations a fixed threshold cannot catch, AI anomaly detection takes over. Finding out why a production KPI turned red calls for root cause analysis with manufacturing data.
6. A KPI definitions glossary. Hovering over a KPI shows its formula, source, inclusions and exclusions, owner and the date its definition last changed. The glossary is what makes departments answer the same question with the same number. Even with sound definitions, duplicate and inconsistent records can distort the figure, so quality checks come before the dashboard. Who owns each definition and how it may change is settled by a data governance framework.
7. Access rights. Access is role-based: the managing director sees the whole company, a regional manager their region, a sales rep their own customers. Breakdowns that contain personal data, such as staff or customer details, are opened only to the roles that need them. Who viewed which screen, and when, is logged. A data catalog and data dictionary tags which tables hold personal data, and if users will build their own reports, self-service analytics governance draws the boundaries.

Design examples by dashboard type

Treat the table as a starting point; every company derives its KPIs from its own goals. On map-based dashboards the KPI is read by location rather than in a table: a municipality tracks faults and losses on its municipal GIS map, while a farm tracks crop health by field alongside a drone NDVI analysis layer.

The same map layer can carry pre-harvest drone crop yield estimates or, on construction sites and quarries, drone stockpile volume measurements as KPIs.

For a water utility the dashboard map is the water network GIS inventory of pipes, valves and service connections; on large farmland where flying a drone is impractical, field KPIs come from satellite imagery for agriculture.

In a factory, part of the dashboard lives on the shop floor rather than in the boardroom. KPIs from factory energy monitoring, or OEE by line, can be pushed to digital signage screens in the production area. On a line screen the one-screen rule is even stricter: three or four large numbers and a threshold colour, readable from several metres away.

Three common mistakes

• Trusting the average. "Average delivery time: 3 days" looks fine, but if some orders take 10 days, that is where customers are lost; customer churn analysis shows which accounts are quietly drifting away. Show the distribution, or the number of records over the threshold, next to the average. If delays stem from delivery planning, route optimisation lets you track stops and deviations per vehicle as well.
• Showing a rate without its base. When the scrap rate rises, volume or product mix may have changed too. Showing units or value next to the rate prevents false alarms.
• Decorating the screen. 3D pie charts, speedometer dials and colour gradients slow reading down. Plain bar and line charts are the fastest way to compare.

Pre-launch checklist

• Every KPI has a definition card that can be opened from the dashboard.
• Every KPI has a single official source.
• The "last updated" time is visible next to each KPI.
• The dashboard has run in parallel with the old Excel report for at least one period, and the differences have been explained.
• The executive summary is readable on a phone and, if wanted, arrives by email each morning.
• Role-based permissions have been tested with different users.
• A review meeting to remove charts nobody uses is in the diary for three months' time.

A dashboard can show forecasts as well as history. We cover tracking on-shelf availability and days of cover by store in retail inventory optimisation, and comparing site consumption with an hourly forecast in electricity load forecasting.

How we build management dashboards at Digital Bridge

On our BI dashboard projects we design the indicators and the data flow before the screens:

• Dashboard and KPI workshop. With management we capture the questions that need answering every week, write a definition card (formula, source, owner, threshold) for each KPI and sketch the one-screen executive summary using your own figures.
• Direct connections to source systems. We connect to Logo Tiger/GO, SAP, Mikro, Netsis and bespoke ERPs, CRMs, marketplace APIs and MySQL, MSSQL and PostgreSQL databases. For systems exposing a REST API we build the API integration; for production KPIs we bring in data from MES production management or SCADA.
• One source of truth. Where several systems and historical comparisons are involved, we consolidate the data in a data warehouse so reports do not slow down the live ERP. We break down what drives the budget in data warehouse cost factors, and explain when raw data belongs in a data lake instead.
• Data quality first. If duplicate customer accounts, inconsistently coded products or empty fields distort a KPI, we fix it at source through data governance and quality work. Showing bad data in a nicer chart solves nothing.
• A dashboard that refreshes itself. It updates at the agreed interval; managers drill from a KPI down to the invoice or work order, and the owner is alerted when a threshold is crossed.
• A phased start. We begin with the executive summary and one departmental dashboard, then extend to other areas once the KPIs are bedded in, so the definitions are tested against real data early on.

For HR indicators such as absence, overtime and shift adherence, the source is usually entry and exit data. SmartPass combines card access control, time and attendance and canteen meal counting in one system; it calculates attendance against the shift plan and produces reports that can be passed to payroll. That data can feed the dashboard under the same definition rules.

We do not sell off-the-shelf packages; after a needs analysis we provide a written proposal covering scope, phases and cost. Since 2013 our Adana-based team has served clients in every province of Türkiye, remotely and on site. For data warehousing, data quality, GIS and drone analysis, see our full Data & Analytics guide.

Next step

Try a simple exercise before your next management meeting: write down the five questions management asks every month and note, for each, which system the answer comes from today, who prepares it and how many hours it takes. That list is enough to scope your first dashboard. Get in touch and we will review it with you and mock up an executive dashboard using your own data.