The Blind Thrust Fault in Your Organization
- Kelly Brogdon Geyer

- 3 days ago
- 3 min read
At 7:42 in the morning on October 1, 1987, the ground under Rosemead, California moved without warning. I was nine years old, standing at the classroom water fountain filling my cup in Westminster, when the shaking started.
I dropped the cup and ran for my desk exactly as we were taught in drills at least a dozen times before. Under the desk, I froze. Around me, other kids reacted differently: some screaming, some crying, one or two trying to calm the rest down. I only cried once the shaking stopped. I hated earthquakes as a kid and I still do.

Seismologists later classified it as a blind thrust earthquake, magnitude 5.9. There was no visible evidence of this fault on the surface. The experts always claim that "the big one is coming" but nobody could pinpoint exactly when it will arrive. Stress had been building along it for years, invisible, until it wasn't.
That morning taught me two things, though it took decades to see the second one clearly. The first is the more obvious lesson: pressure accumulates gently in any system, geological or organizational, right up until the moment it doesn't. The second lesson is the one I think about more now. The reason I knew what to do that morning was not instinct. Before that big earthquake had arrived, some school administrators realized they should prepare kids before it arrives. They built a rehearsed response and taught it to us. It wasn't just taught. It was rehearsed, repeatedly. My body knew what I needed to do even before my brain could comprehend what was happening.
Most organizations have the first lesson memorized. Change gets described constantly in terms of pressure, saturation, capacity. Fewer have built the second: a real mechanism for sensing the shift before it arrives, rather than discovering it only once something has already ruptured.
I saw a version of this play out clearly in a transformation I worked on. The organization began the change only after it had already started laying people off for financial reasons. Not before. The environment around the business had shifted well ahead of that point, but nothing inside the organization was built to notice a shift like that early enough for it to matter. By the time the transformation officially started, it was already responding to a crisis instead of preparing for one. In my earthquake example, it is the equivalent of having no drills to prepare students and instead, the teachers just yell instructions to the kids while it is happening.
Leadership's own explanation, when I raised this, was that the organization had been through a lot of change before and had gotten reasonably good at it. I ran a short survey to test that belief before we went any further. The results told a different story. On the one hand, they were right in that the organization had been through a great deal of change. On the other hand, repeatedly changing had not made them good at any of it. According to employees, the organization had struggled with nearly all of it. The track record leadership was confident in did not exist. Nobody had actually checked.
This is precisely what Assessment & Sensing, one of the six dimensions of the Adaptive Capability Ecosystem (ACE), is built to catch. Not the failure to react once a problem is visible. The failure to notice the problem exists at all, until the cost of not noticing has already been paid.
Most change methodologies are built for the moment after the rupture: how to manage a transformation once a crisis has already triggered it. Fewer are built for what comes earlier, the quiet accumulation of stress that precedes it, the fault line nobody mapped because nobody thought to look. That earlier work stays mostly invisible and rarely gets credit, in the same way a well-run fire drill gets no attention until the day the building actually catches fire. But it is the difference between an organization that responds to a shift and one that absorbs it before anyone outside ever has to.
Where would your organization actually notice a shift like this one, before it shows up in a round of layoffs or a stalled transformation? A free starting point, if you want an honest read before that conversation is the Organizational Adaptability Pulse Check.
If this pattern sounds familiar and you would rather talk it through directly, I am happy to have that conversation.




Comments