The Organizational Pendulum

You've watched a new CPO arrive with an agility mandate.
Six months later, a single audit finding produces 14 new review steps.

You've sat in the meeting where someone says "we need to move faster" while someone else says "we need more governance." You've watched both of them be right. You've watched the organization pick one, ride it until it breaks, then pick the other.

A compliance gap surfaces. A patient safety event. A product launch that skipped three checkpoints and cost real money. The response is always the same: add process. Add review layers. Add sign-offs. The organization swings toward rigor.

It works for a while. Then the process becomes the problem. Decisions take too long. Your best product people leave because they can't ship anything without seven approvals from people who weren't in the room when the decision was made. So leadership swings back. They flatten hierarchies, cut approvals, tell everyone to move fast.

That works too. Until something goes wrong again.

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 is invisible until it isn't.

Both positions feel right from the inside. That's what makes the pendulum so durable. The people adding governance after a failure are correct that governance was missing. The people removing governance when speed dies are correct that process had calcified. Each side is solving a real problem. And each solution becomes the next problem.

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.

The diagnosis isn't academic. It determines everything that follows. A CPO walking into a rigor-heavy culture with a "move fast" mandate will succeed for 18 months 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. Both will wonder what went wrong.

What went wrong is they didn't read the position before they moved.

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 published "The Ambidextrous Organization" in 2004. The core argument: 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 actually 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.

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, toward the known. 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, and build structures that hold both positions so the organization doesn't have to choose.

• 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 shared strategic intent, as described above.
• 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 Teach leaders to hold both. The hardest part. Most leaders have a natural orientation toward rigor or agility. The best ones learn to hold both without flinching. They can sit in a compliance review at 10 a.m. and a product brainstorm at 2 p.m. and bring the right operating posture to each. That's not code-switching. That's fluency.

I've watched this play out in healthcare for fifteen years. The pendulum is faster here, and the stakes are higher.

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, burning out the people in the middle who just want to build something good.

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. The institutional knowledge they carried is unrecoverable. 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. Evidence-based rigor takes 17 years to reach practice (Balas & Boren, 2000). 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.

Looking at the products I've built, the pattern is obvious. Each one addresses a failure mode of the swing.

The pendulum framework isn't theoretical for me. It's the structural throughline I recognized after building, not the blueprint I started with. Each product solves a specific breakdown that occurs when organizations swing too far in one direction.

None of these products announce themselves as pendulum solutions. They don't need to. They work because they're built on the same structural insight: the organization will always oscillate. The question is whether your infrastructure oscillates with it or holds steady while the politics swing.

I assess where your organization sits on the swing and build the structural fix.

This is hands-on work. Not a deck. Not a report. A diagnosis of where your organization sits, a build spec for what needs to change, and the first version of whatever structure should exist. I've done this inside a Fortune 25 payer, inside PE-backed health systems, and inside my own companies.

joe.nalley@showyourwork.health

The question was never which side is right.

Rigor is right. Agility is right. They're both right at different moments, and they're both destructive when they overshoot. 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 they invested in the people and structures to keep both lanes operational when the political winds shift. The pendulum still moves. It just doesn't take the whole building with it.