top of page

The Adaptive Advantage: Why Rigidity Breaks Organizations Faster Than Disruption

Writer: Chrissa Pagitsas
Chrissa Pagitsas
5 days ago
6 min read

I've spent the better part of two decades in rooms where leadership teams are certain they're prepared for disruption. They have the strategic plan, the priorities everyone is aligned to, the accountability structure that keeps execution tight. That works, right up until it doesn't. The pattern I keep encountering is that the discipline these organizations are proud of is exactly what keeps them from moving once the plan stops matching reality. That's organizational rigidity, and it's nearly impossible to see from the inside, because until the moment it fails, it looks exactly like good management.




A recent example of falling into this rigidity trap involves one of the most famous companies in the world. In 2017, Google researchers published the paper that introduced the transformer,  the architecture behind virtually every major AI chatbot in use today. Within a few years, Google had built a capable conversational AI of its own (first called Meena, later LaMDA) and was running it internally.


It stayed internal, and the reasons were understandable. There were concerns about accuracy and about a product that clearly threatened the search-ads business that funded everything else for the company. As late as December 2022, Google’s AI chief told employees the company carried more reputational risk than a startup and was moving more conservatively. When OpenAI released ChatGPT in November 2022, built on the architecture Google had invented, Google's leadership reportedly declared a "code red." Its rushed first response, Bard, stumbled out of the gate in February 2023: a promotional demo video showed it giving a factual error, and the launch event that followed failed to reassure investors. Alphabet lost roughly $100 billion in market value in a single day.


This is reminiscent of what happened to Nokia nearly two decades earlier. In 2004, three years before Apple launched the iPhone, Nokia’s engineers demonstrated an internet-ready touchscreen phone. Management shelved it: no one was sure customers wanted a touchscreen, and the device would be expensive to produce. Years later, Qualcomm’s CEO described Nokia spending six to nine months just assessing opportunities that other phone makers jumped on.


Where the Google and Nokia stories diverge is what matters most for this article. Nokia’s phone business never recovered; in 2013, it agreed to sell its handset business to Microsoft. Google, meanwhile, merged its two AI research groups, the Brain team from Google Research and DeepMind, within months and shipped Gemini before the end of 2023. It was able to move ahead once it decided to.


Rigidity cost Google its head start. Adaptability kept it in the race. That is the adaptive advantage, and it’s critical for organizations.


What Rigidity Actually Looks Like

Rigidity doesn't announce itself. It wears the clothes of discipline and focus. Three signals tend to separate the two:


1.     Absence of a clear guardrail: This might matter the most. Does a mid-level leader know how far an actual number has to move from the planned number to warrant alerting higher leadership? If they don't know whether a one-point deviation matters or only a ten-point one does, they'll freeze when they should act, or escalate unnecessarily. Most organizations discover this threshold in the moment of crisis, which is the worst possible time to be discovering it.


2.     Ratio of justification to action: In flexible organizations, a team that needs to deviate from plan simply deviates, within the understood guardrail. In rigid ones, that same team spends more energy convincing stakeholders the problem is worth raising than it would spend fixing the problem. If your people are better at defending pivots than making them, you've designed flexibility out of the system.


3.     Decision friction: Once the issue is finally raised, does a response have to travel through three or four layers of approval before anyone can act? By the time alignment is reached, the window to respond has often closed. Speed and rigor are not a trade-off: McKinsey research found that organizations that make decisions quickly are about twice as likely to make high-quality ones.


Google had all three of these signals. Engineers who built its early chatbot were repeatedly turned down when they asked to share it with outside researchers, add it to Google Assistant, or release a public demo; two of them left in 2021 to start their own company. Google later paid a reported $2.7 billion in a deal largely aimed at bringing one of them back. The company’s failure wasn't a lack of talent or foresight. It was that the organization hadn’t created a path forward for an unexpected signal to challenge its overarching business plan.


Why Leaders Reach for the Wrong Fix

When pressure arrives, the instinct in almost every leadership team is to tighten, not loosen. They cut costs, reduce headcount, and report a number to the board that proves something is being done.


That instinct isn't irrational. A 10 percent cost reduction is a number you can put in a deck. Delegated authority and pre-agreed thresholds for changing course are harder to point to. They're true resilience, but they don't produce a slide, so the response that feels like leadership in a crisis is often the opposite of what the moment requires. The trap is that the time to build flexibility is precisely when the organization feels like it doesn't need to.


Designing Flexibility into the Organization

The leadership teams I see navigate volatility well make a deliberate choice well before they need it. They design flexibility into the structure instead of trying to summon it in a crisis.


That starts with whether dissent is genuinely welcome, not merely tolerated. When people can flag an anomaly that contradicts the plan without fear of being seen as unruly the organization gets its best information while a correction is still cheap. Otherwise, that information just stays hidden until it's too expensive to ignore. Ironically, Google’s own research on its teams found that psychological safety, the confidence that you can take a risk without having it held against you, was the most important factor in team effectiveness.


That culture only comes to life through delegation. Mid-level leaders need actual authority inside clear guardrails, in ordinary conditions, long before a crisis tests them. Agility and judgment under pressure are not skills that can first be flexed during a crisis. It needs to be practiced in dozens of lower-stakes calls beforehand, so the muscle is already strong when the stakes are high.


Here is a test I give leadership teams: How many stakeholders would a mid-level leader need to convince to even raise the possibility of a market disruption, and how fast could they get the resources to validate it and act? If the honest answer is “several” and “only as fast as business as usual allows,” the organization is considerably less prepared than it believes.


Where to Start

Two exercises make this concrete.


The first is a structured what-if. Choose a disruption that feels unlikely but plausible, and walk your team through what would actually happen if it landed tomorrow. Who has to be involved, how long does alignment take, how many sign-offs stand between recognizing the problem and acting on it? The gaps that surface are usually more honest than anything in the strategic plan. 


The second is a standing expectation that teams feel safe to report low-level anomalies before they're disruptive. Most organizations only listen once something is already a problem. The earliest signal is almost always small. It’s a customer comment that doesn't fit the pattern, a competitor move that seems minor. Track these low-level anomalies and review monthly or quarterly, capturing whether they start to show a trend of something bigger. Teaching people to surface those signals, and giving leadership a real process for acting on them, is what separates an organization that adapts from one that's merely disciplined. Based on Professor Clayton Christensen’s theories, in order to fight a disruption in time, incumbents should spin off independent, autonomous divisions, teams or startup units with their own resources and cost structures. This will provide the agility and autonomy of a startup in an otherwise rigid corporate structure. 


Efficiency without adaptability is fragility with good quarterly numbers. More so, organizations that respond positively under shocks or immense pressure, thrive, not just survive.  The business case for creating a perpetually adaptive organization is harder to justify when the plan is working. However, adaptability is the only thing that matters when disruptions emerge.


Seeking to strengthen the resiliency of your supply chain in 2027? My team and I can assist you to engage with the Board, internal peers, and your suppliers to meet your objectives. See our services at www.pagitsasadvisors.com. Reach me at chrissa@pagitsasadvisors.com and Christine Boyd, Chief Growth Officer, at cboyd@pagitsasadvisors.com.


Have questions or comments about how your organization is managing the impacts of uncertainty? Share with me and readers in the comments on LinkedIn.


Comments


bottom of page