What is a KPI dashboard? The first screen a manager opens in the morning

Example scenario: Picture a software consultancy in Maslak. In the management meeting, the website visitors chart is on screen, and it has gone up. Everyone is pleased and nobody does anything. In the corner of the same screen, the number of quotes awaiting a reply has also gone up, and nobody looks at it. The first is interesting information; the second is a KPI, because when it rises a sales manager should pick up the phone.

KPI stands for key performance indicator. The word key is there for a reason: a company can measure a great many things, and the key ones are those that show the way to the goal.

This distinction decides the dashboard's fate. Any measure might be useful to someone one day, but only the ones that trigger a decision go on the dashboard. The rest belong in a report.

There is a simple test for whether a measure is a KPI: if this figure jumped sharply tomorrow, who would do what. If the answer is a name and an action, it is a KPI. If the answer is silence, however interesting the measure is, it is just taking up space on the dashboard.

An indicator without an owner is everybody's job and nobody's. An indicator without a threshold does not tell you when to worry. An indicator without a record behind it is just a figure; when it rises, it cannot show which customer, which quote, or which employee is behind it.

Setting the threshold is often harder than choosing the indicator. For quotes awaiting a reply, the threshold can be a length of time: a quote left unanswered beyond the day you set turns red. For contracts, the threshold is the time left before the end date. Setting it with the person who does the work avoids an alarm line that has nothing to do with reality.

• Sales: quotes awaiting a reply, opportunities closed this period.
• Contracts: contracts about to end with no renewal decision.
• Money: overdue receivables, payments coming due.
• Operations: slipping deliveries, missing field reports.
• Team: late clock-ins, tasks completed on time.

Take this list as a starting point. Every company's dashboard comes from its own goals; at a construction firm, site handovers come first, at a showroom, visitors who move on to a quote. What matters is that every row can be tied to a goal the company is pursuing today; a row that cannot be tied to one stays off the dashboard, however familiar it looks.

Revenue shows the result, and it arrives late. You see it drop when the month closes, and by then there is nothing left to do. Unanswered quotes, postponed customer visits, and enquiries left without a reply, on the other hand, move before revenue falls. A manager who watches them manages the cause, not the result. At a showroom the difference is concrete. The month-end sales figure describes the past. A rise during the week in visitors who leave without a quote describes the weeks ahead, and it is something to discuss with the sales adviser today.

The screen is ordered by priority: what awaits a decision at the top, information below. Colour is used only when a threshold is crossed; if everything is red, nothing is. Every row has a name next to it, because the question is always the same: who is going to sort this out.

The screen has to read well on a phone. Managers often start the day not at a desk but on the way in or over coffee. A dashboard that does not work on a phone only gets opened once they reach the office, and by then the first meeting has already started. The screen has a rhythm as well. In the morning it shows the day's decisions; in the evening, how the day closed. The same indicators answer different questions at different hours: in the morning, what should I do; in the evening, what happened.

The most common reason is that the data is carried over by hand. The dashboard feeds from a spreadsheet, the spreadsheet is filled in once a week, and when the manager looks on Tuesday they see Friday's picture. A dashboard that turns out wrong once or twice loses trust, and nobody looks at a screen they do not trust. Where the weekly spreadsheet stalls is covered in from Excel reports to live records.

The second reason is that indicators multiply. One gets added at every meeting and none are ever removed. As the screen gets crowded, the row that needs a decision gets lost among the information rows. When adding an indicator, it is a good habit to ask which one comes off.

The third reason is that you cannot get behind the dashboard. The manager sees a red row, wonders which customer or which quote it is, and calls someone to find out. The dashboard raises the question but does not answer it; after a while the manager skips the dashboard and goes straight to the phone.

In Corex360, vehicles, messages, calls, quotes, contracts, files, invoices, attendance, and projects sit on the same core, and the intelligence core reads them together. X AI reads the core and the inbox overnight, and in the morning one report arrives on your phone: what it did, what is waiting, what it is asking you. To get behind a row you simply open the card; you see which customer or which quote the red row is about without calling anyone.

The indicators come from rules you write: when a quote goes unanswered, a contract nears its end, or a field report is missing, the row enters the briefing on its own. When the day ends, what was planned and what happened close on the same screen. You can see how a manager's day runs with this screen on the page on a manager's morning briefing.