Three questions to ask your IT team before the next multi-site crisis
A short format, built for a leadership meeting: three questions that reveal whether your organization would see the next major incident coming, or learn about it at the same time as its customers.
Walter Blanchard · · 2 min read
Key takeaways
- The delay between a problem first appearing and reaching the leadership team is the most revealing indicator — and the least often measured.
- A dashboard that only measures what was planned for will never catch what wasn't anticipated.
- A weak signal only has value once validated by someone who knows the ground truth, on data with controlled access.
You don't need a months-long audit to find out whether your organization would see its next multi-site crisis coming. Three questions, asked in a leadership meeting, are enough to surface the answer.
Question 1 — How much time passes between the first sign and us knowing?
Ask your CIO or operations director to reconstruct the real timeline of your last major incident: when did the first sign appear in the data (tickets, emails, frontline reports)? When was it flagged as a problem? When was leadership informed?
In most organizations, no one has ever asked the question in exactly this order — the incident gets documented, the delay that preceded it rarely does. If the answer is "we don't know," that's already an answer.
Question 2 — Do our dashboards measure what we planned for, or what we didn't anticipate?
Monitoring tools and service reports answer questions that have already been asked: ticket volumes, availability, SLA compliance. That's essential — and structurally insufficient. A weak signal, by nature, concerns something that doesn't yet have a box on the dashboard.
Ask to see a recent example of a problem that built up gradually (slipping deadlines, similar requests worded differently) and was only caught late. If there's no recent example, that's rarely a good sign — it usually means no one is looking for them.
Question 3 — Who validates a signal before a decision gets made, and on what data?
A grouping of scattered signals is only a hypothesis until someone who knows the ground truth confirms it. Ask who, concretely, would play that validation role — and over what data scope. If the answer involves broad, uncontrolled access to personal data, that's a risk in its own right, separate from the operational problem you were trying to solve.
A good practice: read-only access to the tools, data pseudonymized by default, and a systematic human decision before any action.
Why these three questions are enough
They require no project, no budget, no new tool — just one hour in a leadership meeting. And on their own, they reveal whether your organization would be informed of an emerging problem in time to act, or only after the fact, from its customers or the press.
Where to start
If the answers leave a doubt, the Nexsentia Diagnostic is built to settle it on facts: a few weeks of read-only access to your existing tools, to establish whether actionable signals already exist in your data — and how fast they could reach you.