The Organizational Pendulum
Organizations oscillate between rigor and agility.
You can't stop the pendulum.
You can learn to build for it.
The org tightens. Then it loosens.
Then it tightens again. Every time feels like a new strategy.
Something goes wrong. A product ships without adequate review. An audit surfaces a gap. A compliance event makes the news. The response is predictable: add process. Add review layers. Add sign-offs. The organization swings toward rigor. And rigor works. For a while.
Then the cost shows up somewhere else. Decisions take quarters. Good ideas die in committee. The people closest to the market can't move without approvals from people who've never spoken to a buyer. The organization starts losing the operators who actually build things.
So the mandate shifts. Move faster. Fewer gates. More autonomy. And that works too. Until scope creeps, portfolios fragment, and two teams ship products that contradict each other because nobody was coordinating.
Then something goes wrong again. And the cycle restarts.
This is the organizational pendulum. It's constant. And almost nobody builds for it.
Too much rigor creates swirl. Meetings about meetings. Approvals that exist to protect the approver, not the outcome. Process becomes performance. The work slows down and nobody can point to a single decision that caused it, because no single decision did. A hundred small additions did.
Too much agility creates chaos. Speed without direction. Products launched without governance. Decisions made in hallways that should have been made in reviews. The wins are real. The exposure doesn't show up until someone's writing the incident report.
Both positions feel right from the inside. That's what makes the cycle so hard to break. The people adding governance are right that it was missing. The people cutting it are right that it calcified. Each fix becomes the next problem.
The swing is structural. You don't will your way past it.
Before you prescribe, know where the weight sits.
Most interventions fail because they're directionally wrong. A rigor-heavy organization doesn't need better governance. It needs permission structures. An agility-heavy organization doesn't need faster sprints. It needs reporting lines that don't punish transparency. The wrong prescription accelerates the cycle.
How long does it take a concept to reach a customer? If the answer is measured in quarters, the weight has shifted toward rigor.
When was the last time a launched product surprised leadership? If the answer is recently, the weight has shifted toward agility.
Do your best operators describe the culture as "bureaucratic" or "chaotic"? They're telling you where the pendulum sits. Listen to the word they choose.
How many people can say no to a project? How many can say yes? If the ratio favors no, you've built a system optimized for prevention.
The diagnosis determines everything that follows. A leader walking into a rigor-heavy culture with a speed mandate will succeed for a while and then watch the organization snap back harder than before. A compliance leader walking into an agility-heavy culture with a governance framework will be right about every risk and wrong about every timeline.
What went wrong is they didn't read the position before they moved.
The academic prescriptions are real. O'Reilly and Tushman proposed structural separation. Kotter proposed dual operating systems. What none of them produced is something an operator can implement — the kind of framework that tells you what to build on Monday when you recognize the swing on Friday.
Place the weight. See what it reveals.
Drag the indicator to where your organization sits right now. Not where leadership says it is. Where the people doing the work would place it.
The Structural Answer
O'Reilly and Tushman's argument is structural: organizations that sustain performance over time are structurally designed to explore and exploit simultaneously. Not sequentially. Not in alternating phases. At the same time, within the same entity, with different operating models for each.
Most organizations respond to the swing by choosing a side. New leadership arrives, reads the pain, and prescribes the opposite of whatever the organization just experienced. That feels like progress. It's phase two of the same cycle.
Ambidexterity breaks the cycle by refusing to choose. It builds separate structures for rigor and agility, connects them through shared strategy, and lets each operate with its own cadence, its own metrics, its own definition of speed.
The explore side operates with small teams, fast iterations, short feedback loops, and tolerance for failure. The exploit side operates with defined processes, compliance checkpoints, measurement rigor, and predictability. The mistake most leaders make is trying to run both sides with one operating model. When you apply exploit rules to exploration, you kill it. When you apply explore rules to exploitation, you lose control of it.
This dual-lane principle is the structural foundation of FORGE — where the Pipeline handles what you know and the Furnace handles what you don't.
March showed in 1991 that exploitation naturally crowds out exploration. Without structural protection, organizations default to what already works. The gravity is always toward rigor, toward measurement. Exploration dies slowly and invisibly. By the time leadership notices the pipeline is empty, the explorers have either conformed or left.
The goal isn't equilibrium. Weiser and Laamanen proved that equilibrium is dissipative -- it requires continuous energy. The moment you stop attending to it, the system drifts. The goal is abatement: reduce the amplitude, shorten the recovery time, build structures that hold both positions.
- 01 Diagnose the position. Know where the organization sits on the swing before you prescribe. Run the position check. Talk to the operators, not the executives. The people doing the work know whether the problem is too much process or not enough. They've been saying it in exit interviews for two years.
- 02 Build the dual-lane structure. Separate operating models for exploration and exploitation, connected through a shared strategy.
- 03 Fund the practice. Balance is not a destination you arrive at. It's a discipline you staff. Dissipative equilibrium means someone has to watch the drift, name it, and correct it before it becomes a mandate. Build the monitoring. Staff the role. Give it authority. The organizations that treat balance as a one-time initiative swing harder on the next cycle.
- 04 Protect both lanes from each other. Every leader has a natural orientation. Some were hired for rigor. Some were hired for speed. The job isn't to personally hold both. It's to build teams optimized for each lane, connect them through shared governance, and defend whichever lane is under pressure. The exploit lane will always try to absorb the explore lane. The leader's job is to keep that from happening.
I've watched this play out in healthcare for fifteen years. The pendulum is faster here, and the stakes are higher.
Post-M&A integration. The acquiring company centralizes for control. The acquired company loses the operational autonomy that made it worth buying. Three years later, they decentralize. The original talent is gone.
I ran a health system through acquisition and stayed as CEO for three and a half years after the close. The centralization pressure was immediate. The talent loss took eighteen months to show up.
Clinical operations. Balas and Boren estimated 17 years for evidence to reach practice (Balas & Boren, 2000, Managing Clinical Knowledge for Health Care Improvement). That was in 2000. The number hasn't moved much. Clinical innovation happens at the bedside and gets punished by compliance.
The gap between what we know and what we do is a pendulum artifact. Every new protocol that takes a decade to adopt is a swing that went too far toward control.
PE-backed healthcare services. The 100-day plan demands discipline. The operators who survive the plan demand flexibility. The tension between the investment thesis and operational reality is the pendulum at its most compressed.
Three-year hold periods don't allow for a full swing. So the damage compounds faster. I've watched a platform company hit 40% EBITDA margin in year two and lose its best clinical team by year three. The hold period ended. The damage didn't.
Product lifecycle management. The sprint toward launch ignores the governance needed after launch. The governance installed after a failure kills the next sprint. The product organization oscillates between "ship it" and "control it" every 18 to 24 months, and the people in the middle — the ones who actually build — absorb the whiplash.
The question was never which side is right.
The real question is how to prevent going so far in either direction that recovery becomes the full-time job. That's what most organizations are doing right now. Recovering from the last swing. Getting ready for the next one. Calling it strategy.
Ambidextrous organizations don't recover. They don't need to. They built for both from the start and invested in keeping both lanes operational when the political winds shift. The pendulum still moves. It just doesn't take the whole building with it.
The pendulum doesn't stop. I stopped expecting it to a long time ago. So I build for it.
If your organization is in the middle of one of these swings and the standard playbook isn't working, I've been in that room.
joe.nalley@showyourwork.health