My origin
This lens was formed inside live businesses, where the work was already moving, the commitments were real, and the structure underneath them was not holding.
Some of it started in graduate work on multi-constraint problems. The challenge was never optimizing one variable in isolation. It was making systems perform under competing demands without breaking somewhere else. I did not know it then, but that turned out to be the right problem.
Early in my career I helped introduce new capability into live organizations and watched what happened when the surrounding structure could not absorb it. What used to take days happened instantly. The technology worked. The organizations around it did not. They failed because the structure underneath could not keep up. Decisions piled up. Handoffs broke. Capability had moved faster than the structure built to carry it.
Later I was brought in from the other side — when the architecture had already buckled, the business was already live, and the clock did not stop. That is where I learned the difference between analyzing systems and being responsible for them.
Over time the pattern stopped looking situational and started looking structural. Different technologies. Different industries. Different stakes. The visible failure changed. The break underneath it usually did not.
That is where this lens comes from. Not from studying these failures at a distance. From causing some of them and spending the rest of a career fixing what that kind of break actually costs.
Connect directly →