Most organizations have reporting. Far fewer have awareness. The difference is whether anyone would notice something going wrong before a customer told them.
Situational awareness is a term borrowed from aviation and military operations, and the borrowing is apt: it describes the gap between having instruments and understanding your situation. A cockpit full of gauges is not awareness. Knowing what those readings mean, what they imply about the next ten minutes, and which ones warrant action — that's awareness.
Businesses fail this test constantly, and usually not from lack of data. They fail it from having enormous amounts of data arranged so that no one can form a picture from it.
Historical reporting. Last month's revenue, last quarter's spend, the deals that closed. Necessary, universally present, and the least useful for decisions because the window to act on it has closed.
Current state, at a latency short enough to intervene. Which accounts are trending toward risk right now. Which workload started costing 40% more this week. Where a process is backing up today. Fewer organizations have this, and it's where most operational value sits.
Projection. Given the current trajectory, what breaks next quarter and what does it cost? Very few organizations reach here — not because the modeling is hard, but because it requires Levels 1 and 2 to be trustworthy first.
Here's a more useful metric than any dashboard: how long does it take this organization to find out something is wrong?
Not how long to fix it — how long to know. If a critical process fails at 9am Tuesday, when does someone with authority learn about it? Some organizations answer in minutes. Many answer in weeks, and a discomfiting number answer “when the customer complains.”
That number is the real measure of operational intelligence, and it's rarely tracked because it's uncomfortable. It also predicts almost everything else: cost overruns, missed forecasts, and churn all correlate tightly with how late the organization finds out.
Three failure modes, all common.
No one is looking. A dashboard is pull-based; it requires someone to remember to check. Awareness is push-based — the system tells you when something crosses a threshold that matters.
Everything is shown, so nothing stands out. Forty-tile dashboards where every metric has equal visual weight force the viewer to do triage the system should have done. If everything is important, nothing is.
No one is accountable for the number. The same failure that undermines cost governance undermines awareness. A metric with no owner produces observation, not response.
Awareness comes from a small set of numbers that genuinely describe the health of the business, each with an owner, each with a threshold that triggers something specific, reviewed on a cadence that matches how fast they can move.
That's less technically impressive than a real-time visualization layer, and considerably more effective. The organizations that respond fastest aren't the ones with the most instrumentation — they're the ones where a small number of people know exactly which handful of numbers matter and would notice within hours if any of them moved.
Metrics architecture, ownership, and operating cadence are core to how a 90-day plan is built.
See how the Diagnostic works →