The Warning Signs Leaders Miss Before a Crisis
One of the more uncomfortable patterns in organizational failure is that the warning was rarely absent. More often it was present, specific, and known to someone who had no practical route to act on it.
That changes what readiness work actually involves. The task is less often to gather more information than to notice what is already visible, and to ensure the noticing reaches someone with the authority to move.
Six signals appear repeatedly before trouble. None of them look like emergencies. That is largely why they function as warnings, and also why they get filed under things to address later.
1. The Workaround That Became Permanent
Someone invented a temporary fix for a system that was not working. It held. It is now eighteen months old, undocumented, and known to three people.
A workaround carries useful information in two directions. It indicates where the official process fails, and it indicates where the organization is carrying an undeclared dependency. When the person who built it leaves, the workaround often leaves with them, and the failure it was covering returns without notice.
Ask in any routine review: what are you doing that is not how it is supposed to work. People will usually tell you, because they are proud of the fix. The answers form a map of weak points drawn by the people standing on them.
2. The Person Who Stopped Raising Issues
Someone who used to flag problems no longer does. This is frequently read as improvement. It rarely is.
People tend to stop reporting when reporting stopped producing a result, or when it produced a cost. The information has not disappeared. It has gone private. The early warning system has one fewer sensor, and the sensor that went quiet is often the one that was working.
A useful habit is to track who raised the last several concerns you heard. If the same two names keep appearing, the issue may not be that two people are negative.
3. Deferred Maintenance of Any Kind
The physical version is obvious. The organizational versions are less so, and they tend to behave identically: a role left unfilled and covered informally, documentation nobody has updated since a change, a certification that lapsed, training postponed for two consecutive cycles, a vendor contract running past its review date.
Each of these is individually defensible. The pattern is the thing worth watching. Deferred maintenance accumulates quietly and often presents all at once, which is why organizations experience it as a sudden crisis rather than as the slow arithmetic it actually was.
4. A Single Point of Failure Nobody Has Named
Most organizations have at least one. Fewer have said so out loud.
The test is direct. Name the functions that would stop entirely if one specific person were unavailable for two weeks. Then ask whether a documented alternative exists, and whether the alternate has ever actually performed the task rather than simply being listed.
The failure mode here is usually not that organizations lack backups. It is that the backup exists on an org chart, has never performed the function, and in some cases does not know they are the backup.
5. Agreement That Arrives Too Quickly
A proposal that draws no objection in a room of experienced people is a signal worth examining rather than a result worth celebrating. Either the proposal is genuinely sound, or the room has learned that objecting carries a cost.
The two can look identical from the chair. One way to distinguish them is to ask directly for the strongest case against, and to observe whether anyone can produce one. A room that cannot articulate the downside of its own decision may not have evaluated it.
6. The Plan That Has Never Been Run
Most organizations have a continuity plan. Far fewer have executed one, and the distance between a plan on paper and a plan that has been run is where the failures tend to live: contact lists carrying departed staff, an assembly point that is now a construction site, a notification sequence that assumes a system since replaced.
A plan that has never been tested is not yet a plan. It is a document describing one. The first time it is exercised should not be the first time it is needed.
Why These Get Missed
None of these signals are hidden. The reason they go unaddressed is usually structural rather than perceptual.
Each one is a problem that is not urgent today, often raised by someone who is not senior, about a system that is currently working. Most organizational incentives route attention toward the visible and the immediate. A warning about something that has not happened yet competes poorly against something that is happening now, and it tends to keep losing until it stops being a warning.
This is why individual vigilance alone does not resolve it. A personally attentive leader still runs out of attention. What changes the outcome is a structure in which noticing is distributed, raising a signal is low cost, and someone holds standing authority to act on one without escalating it first.
Where the Mosaic Shift Matrix™ applies
Within the broader Mosaic Intelligence Method™, the Mosaic Shift Matrix™ maps organizations against two dimensions, structural clarity and load distribution, producing four organizational states: Fragile Architecture, Managed Stability, Reactive Structure, and Stewarded Architecture.
Signals go unread far more often in organizations where responsibility is concentrated and decision paths are unclear, because the person who sees the problem and the person who can act on it are not the same person and have no reliable route between them. Examining structure directly is frequently more productive than asking people to pay closer attention.
What to Do When You Find One
Rather than launching a review, do one thing this week for one signal.
Take the single point of failure. Name the function, name the alternate, and have the alternate perform the task once while the primary is present. That is an afternoon. It converts a theoretical backup into a real one, and it reveals immediately whether the documentation is adequate, because the alternate will not be able to follow it if it is not.
Then take the next one. Readiness is rarely built in a planning cycle. It is usually built by closing one gap at a time, during the period when nothing is wrong and nobody is asking you to.
Questions leaders ask
What are the warning signs of an organizational crisis?
Six recur: a temporary workaround that became permanent, a person who stopped raising issues, deferred maintenance of any kind, a single point of failure nobody has named, agreement that arrives too quickly in a room of experienced people, and a continuity plan that has never been run.
Why do leaders miss warning signs before a crisis?
The reason is usually structural rather than perceptual. Each signal is a problem that is not urgent today, often raised by someone who is not senior, about a system that is currently working. Organizational incentives route attention toward the visible and the immediate, so the warning keeps losing until it stops being a warning.
How do you find a single point of failure in an organization?
Name the functions that would stop entirely if one specific person were unavailable for two weeks. Then check whether a documented alternative exists and whether that alternate has ever actually performed the task, rather than simply being listed on an org chart.
What is the first thing to do after identifying a warning sign?
Address one signal rather than launching a review. Take the single point of failure, name the alternate, and have the alternate perform the task once while the primary is present. That converts a theoretical backup into a real one and tests the documentation at the same time.
Leading before, during, and after: three phases, three different jobs.
Accounting for people, setting the update rhythm, and the four mistakes that compound.
Three commitments the most effective recovery leaders share.
Twelve questions with observable answers.
Register your group for any title and receive a Certificate of Facilitation.
Dr. Karissa Thomas is an author, keynote speaker, and leadership strategist and the creator of the Mosaic Intelligence Method™. She holds an Ed.D. in Educational Leadership and an Executive MBA and is the author of The Mosaic Way™ Leadership Series and the Leading Through the Storm series.
Leading Before the Storm
How to Recognize Risk, Build Readiness, and Act Before Crisis Forces Your Hand. Includes the Mosaic Shift Matrix™ as a shared diagnostic a team can run on its own structure.
Get the book → Bring this to your organization