Building Business Strategies That Actually Survive Contact With Reality
I spent about six years working on strategic planning for mid-market technology companies before I realized most frameworks were built for textbook scenarios, not actual business environments. The difference between a strategy that looks good on a slide deck and one that holds up when revenue drops 30% overnight is something nobody teaches in business school. Tobe Keeney's approach to resilience and innovation in business strategy focuses on building organizations that can absorb shocks while simultaneously pursuing growth. It's not just about risk management, and it's not just about being creative. The two things usually get separated in corporate settings, which is why most companies end up either too rigid or too chaotic.Tobe Keeney Architect Of Resilience And Innovation In Modern Business Strategy
The core idea is straightforward enough, but execution gets messy fast. You build strategic plans that assume disruption will happen, then design your operations so that when it does, you're not starting from zero. At the same time, you maintain enough flexibility in your resource allocation that innovation doesn't get suffocated by the very processes meant to keep you stable. I worked with a logistics company a few years back where the standard resilience playbook would have failed completely. We had built out supply chain redundancy for their primary routing corridors, which covered maybe 80% of normal disruption scenarios. Then the Suez Canal blockage happened, followed by a series of port strikes that our models hadn't accounted for. The strategies we'd built around "known unknowns" were solid, but they assumed the disruption would stay within certain geographic and temporal bounds. The workaround was uncomfortable at first because it required admitting our initial framework was incomplete. We layered in what I'd call adaptive capacity planning. Instead of just adding backup suppliers, we restructured procurement so that contract terms included trigger points for rapid reallocation. When a disruption hit a region, the decision about where to reroute wasn't something that required a three-week committee process. The authority and funding were already coded into the operational contracts. This cut response time from roughly ten days to about forty-eight hours in subsequent incidents.
Here's something most strategy guides won't tell you: resilience and innovation often compete for the same resources in the short term. When you're in survival mode, you don't have bandwidth for experimental projects. The Keeney approach addresses this by separating what I call core resilience from adaptive innovation. Core resilience covers the basics, the things that keep the business functioning under stress. Adaptive innovation is a smaller, ring-fenced portion of resources dedicated to exploring new approaches that might become your next advantage. The key is maintaining that separation even when it feels like you should pour everything into survival. Another counter-intuitive point that takes people by surprise is that over-investing in resilience can actually reduce your capacity for innovation. I've seen companies build such robust contingency systems that they become slow and bureaucratic. The question isn't how much resilience you can add, but where the marginal cost of additional resilience starts exceeding the marginal benefit. For most mid-size companies, that point comes surprisingly early. Beyond a certain threshold, more backup systems and redundant processes just add overhead without meaningfully improving your ability to handle novel disruptions. The practical implementation involves a few components. First, you map your critical value streams and identify the single points of failure in each. Not the theoretical risks, the actual bottlenecks that would cause immediate damage if they failed. Second, you build recovery protocols for those specific points that can be activated within 24 to 72 hours without executive approval. Third, you establish an innovation budget that operates on a different timeline than your main operational budget, with its own governance that protects it from being raided during downturns.
One limitation of this approach that deserves mention is that it requires a level of organizational maturity that many companies simply don't have. You need people who can think in systems, who understand that their decisions in one area create ripple effects elsewhere. If your leadership team is still operating in silos with quarterly targets that conflict with each other, adding resilience and innovation frameworks on top of that just creates more complexity without solving the underlying coordination problem. In those cases, you're better off starting with basic cross-functional alignment before investing heavily in strategic architecture. The measurement side is also tricky. Resilience is hard to quantify because the absence of disruption doesn't prove your strategies worked. I've found that leading indicators like time-to-recover from minor incidents, the ratio of adaptive capacity spending to total operational spend, and the number of new process variations that teams implement without escalation give you a sense of whether the system is actually building capability or just adding paperwork. If you're considering implementing this in your own organization, start with a single value stream rather than trying to roll it out company-wide. Pick something that matters, something with clear dependencies you can map, and run a full resilience and innovation exercise on that one area. You'll learn more from one concrete implementation than from reading about the framework thirty times. The theory is sound, but the practical challenges are where most people figure out whether their organization is actually ready for this kind of strategic architecture.
Get the Full Details
