What to see on a Monday morning

The difference between a dashboard and a decision

A dashboard shows you numbers. A decision changes what you do next. Those are not the same thing, and the gap between them is where a lot of Monday mornings quietly go to waste. You open a screen, you read a row of figures, you nod, and then you close the screen and do roughly what you were going to do anyway. The screen was busy. Nothing moved.

This article is about closing that gap. The goal is not a prettier dashboard. The goal is a Monday-morning view that ends in an action, not a nod. Once you understand the idea, the tooling is almost an afterthought.

What a dashboard is actually for

It helps to be precise about the words. A dashboard is a display of measurements. Those measurements are usually chosen because someone decided they matter. A performance indicator is one such measurement: in the plain definition, "A performance indicator or key performance indicator (KPI) is a type of performance measurement." [1] A dashboard is a wall of those, arranged so you can read them quickly.

Reading is the operative word. A dashboard is good at the same job a car's instrument panel does: it tells you your current speed and your fuel level at a glance. It does not tell you whether to turn left. That judgement is still yours. The instrument panel earns its place only because the two or three numbers on it are the ones that change what you do with your hands and feet in the next minute.

Most business dashboards fail the instrument-panel test. They show forty numbers because forty numbers were available, not because forty numbers change a decision. The honest question for every tile on a screen is simple: if this number were different, would I do something different today? If the answer is no, the tile is decoration.

A decision needs a choice, not a chart

A decision is a different kind of event. In the standard definition, decision-making "is regarded as the cognitive process resulting in the selection of a belief or a course of action among several possible alternative options." [2] The key words are *selection* and *alternative options*. A decision exists only when there is more than one thing you could do and you pick one.

That is why a chart on its own is not a decision and never becomes one by being larger or more colourful. A chart becomes useful at the exact moment it narrows your options. Revenue is up: so what? Revenue is up because three customers renewed early and one large account went quiet: now you have options. Chase the quiet account today, or wait a week. That is a choice, and the numbers earned their keep by producing it.

The discipline here is to design the view backwards. Start from the handful of decisions a business owner actually makes on a Monday. Who needs a reply before this gets worse. What is overdue that should not be. Where is money sitting that should have moved. Then show only the numbers that change those answers. Everything else can live in a report you open when you have a specific question, which is a different need from a standing morning view. We have written separately about the numbers that actually change a decision, and the same test applies to a whole screen: if removing a number would not change a single action you take this week, remove it.

Why more data makes this worse, not better

There is a strong instinct to fix a useless dashboard by adding to it. If the numbers are not helping, surely more numbers will. The opposite is usually true. Analysis is meant to serve a decision, not replace it: "Data analysis is the process of inspecting, cleansing, transforming, and modeling data with the goal of discovering useful information, informing conclusions, and supporting decision-making." [3] The phrase that matters is *supporting decision-making*. Support, not substitute. When a screen grows past the point where you can read it in ten seconds, it stops supporting the decision and starts hiding it.

The practical sign of this is familiar. You open the dashboard, feel vaguely informed, and take no action. That feeling is not insight. It is the comfortable sensation of having looked, which is what a crowded screen sells instead of a decision. A tool that leaves you informed and still is doing half its job and charging you for the whole.

What a Monday-morning view should contain

Here is a workable standard. A good morning view answers three questions and then gets out of the way.

• What changed since I last looked. Not the running total, which you already roughly know, but the delta. A new order, a cancelled one, a reply that came in overnight, an invoice that just went overdue. Change is where decisions live.

• What needs me, specifically, today. The things that will get worse if ignored and better if touched. A quote that has been sitting unanswered. A customer who went quiet. An approval only you can give. This is the part most dashboards omit entirely, because it requires the tool to know what *waiting* looks like, not just what *total* looks like.

• What is drifting in the wrong direction. A trend that is early enough to act on. Not a vanity line that only goes up, but the first week where follow-up slipped or support replies slowed.

Notice that each of the three ends in a possible action. That is the whole trick. A number that cannot produce an action does not belong in the morning view, however interesting it is. Save it for when you go looking.

The quiet failure modes

Two traps are worth naming. The first is the number with no owner. A metric that is nobody's job to act on will be nobody's job to act on, no matter how prominently it is displayed. Before a number goes on the morning view, decide who moves when it moves.

The second is the number that is always slightly wrong. If the figures do not match what you know from your own eyes, you will stop trusting the screen within a fortnight, and then you will go back to your inbox and your gut. A morning view is only as good as the data under it, which is why the unglamorous work of keeping records current is not separate from this topic but central to it. When your own spreadsheet quietly stops keeping up with reality, the dashboard built on top of it inherits every gap, a problem we covered in when a spreadsheet stops being enough.

It is also worth being clear about where the human stays in charge. A morning view can surface a decision and even recommend one. It should not quietly make the irreversible ones on your behalf. Where that line sits is its own subject, covered in decisions automation should never make.

How this looks in practice

When we built the morning briefing in 360REV, the rule was that every line had to end in something a person could do: reply to this, chase that, approve the other. A line that only reported a total did not earn a place. That is the one product-specific point worth making here, because the principle holds whatever software you use.

So the test to carry into Monday is short. Look at your screen and ask, for each thing on it, what would I do differently if this were different. The items that have a clear answer are your dashboard. The items that do not are someone else's idea of what a dashboard should be. Keep the first set small, make each one point at an action, and the difference between a dashboard and a decision stops being a problem you have and becomes a habit you keep.