Frameworks Are Load-Bearing

Say the word framework in a room of executives and watch the temperature drop. ITIL. NIST. COBIT. The words land like paperwork — a tax levied on the people who would rather be building something. Overhead. Ceremony. The stuff you tolerate because an auditor is coming. I have sat in those rooms for nearly thirty years, and I understand the reflex completely. I also think it is one of the most expensive misreadings in enterprise technology.

Frameworks earn that reputation honestly, and the reason is structural. They are least visible precisely when they are working. A change that doesn’t break production, an incident that never becomes an outage, a dependency someone documented three years ago and nobody has thought about since — none of that shows up in a quarterly review. Discipline that succeeds looks like nothing happening. So it gets read as nothing happening, and the first thing cut when budgets tighten is the thing that has been quietly holding the weight.

Then a bad day arrives, and you find out.

When I established the CIO function at a North American multi-plant food manufacturer and rebuilt the enterprise systems environment in forty-six days following an international cyberattack, I learned something I have not been able to unlearn: under that kind of pressure, the discipline sorts itself instantly into load-bearing and decorative. Nobody argues about the value of a documented environment at hour zero of a rebuild. You either know what you had, or you are reconstructing an enterprise from memory and hope. Every hour of clarity you have on that day was purchased on some ordinary day years earlier, by someone doing unglamorous work nobody applauded.

That is what a framework actually is. Not a rulebook to obey — a load path. A way of distributing weight so that no single point carries more than it can hold, and so that when something does give, the structure around it does not come down with it. ITIL is not a certificate on my wall; it is a way of ensuring that the knowledge required to run a system lives in the system rather than in one person’s head. That distinction is the entire difference between an organization and a dependency on a few heroic individuals who will eventually leave.

Which is also why the framework is not the binder. I have watched organizations fail in both directions, and the two failures look nothing alike. One buys the standard, prints the documents, passes the audit, and changes not a single behavior — compliance as costume, a structure drawn on paper and never built. The other skips the standard entirely, moves fast, and accumulates undocumented dependencies until the whole thing is a single point of failure wearing a org chart. The first knows the words. The second knows the work. Neither one is safe. The question is never do we have a framework. It is is the discipline actually running — and you can only answer that by looking, continuously, not by pointing at a shelf.

I did not come to this only from the institutional side. I have been building my own ventures since the 1990s, and nothing teaches you the worth of structure like operating without any. From the founder’s seat you feel every missing process personally — the undocumented decision you have to reconstruct, the dependency that lives nowhere but in your own memory, the thing you did once and can no longer repeat. And you learn the corollary that most of the anti-framework argument gets exactly backwards: structure is not what slows you down. Structure is what lets you move fast without having to be careful about everything at once. It is the reason you can stop holding the whole building in your head.

So when I say design it right, secure it, and sign your name to it, the first move comes first for a reason. Designing it right is not an aesthetic preference. It is the decision to build something that can survive contact with a bad day — and frameworks are how you make that decision at a scale no one person can hold. They are not bureaucracy. They are the part of the building you never see, right up until the moment it is the only thing keeping you standing.

— Keith Formell