The persistence of corporate currents

Why knowing what good looks like hasn't changed anything

Almost every leader I have worked with has a book that changed how they think. For some it’s Accelerate. For others, Team Topologies, or Lean Enterprise. There are Five Dysfunctions of a Team, or The Toyota Way. Some inspire change. Others described their organisations so precisely that they half-expected the author to have worked there.

The inspirational change ones are the worst. They underline half the pages. They start a book club. Six months later, the organisation remains stubbornly in the same position.

Let’s say a director reads Accelerate. She introduces DORA metrics. She tells her teams to ship smaller, learn faster, reduce cycle time. She means it. She oversees the implementation.

The teams improve. Cycle times come down. Deployment frequency ticks up. She creates dashboards with numbers that go up and to the right.

But business performance doesn’t follow. Customer traction measured in quarters, deliveries measured in roadmap promises kept or missed. These numbers remain stubbornly static.

She runs an AI adoption campaign and it’s the same pattern; she’s implementing tooling that makes her teams go faster. But the organisation’s procedures and practises outside the team mean that the bottleneck moves. It’s never resolved.

The director wonders what she’s doing wrong.

The great beyond

Unfortunately for her, the answer is “nothing.”

McKinsey’s 2026 State of Organizations report found that 88% of leaders say they’re deploying AI. “However just as many report no significant bottom-line impact.” A Harvard Business School study documented organisations with near-universal copilot adoption but “the absence of a repeatable path that leads from a proof-of-concept to a standard operating model.”

The annual DORA report tells us that she’s right to want smaller batches and faster feedback. She’s right that cycle time matters more than roadmap fidelity.

There’s a useful idea in David Foster Wallace’s 2005 commencement speech. Two young fish swim past an older fish who asks “How’s the water?” They swim on for a while before one turns to the other and says, “What the hell is water?”

The director can’t see the water either. She sees the metrics and campaigns for change. She does this in an organisation with a quarterly planning cycle, a fixed roadmap, an established reporting structure and cadence. These things create invisible constraints on flow. Our director experiences them as how the organisation works.

The tension nobody measures

Her performance is measured against two things that operate in tension with each other.

Her teams are measured on flow: cycle time, deployment frequency, change failure rate. These metrics reward small batches, fast feedback, and the ability to change direction when you learn something new.

She is measured on delivery: roadmap completion, quarterly commitments, predictable output. These reward large batches, because a large batch is a visible batch. Something you can put on a slide. Something her VP can take to the board and point at.

The metrics she introduced can change the team behaviour, but they don’t influence the organisational water. The organisation’s reward structure hasn’t changed. The planning cadence hasn’t changed. The definition of progress hasn’t changed. Only the teams have changed, and they could only change so far before hitting a ceiling that wasn’t theirs.

What the dashboard can’t show

The director’s DORA metrics are good metrics. The teams’ improvements are real. The problem isn’t the measurement; it’s the boundary.

Flow was never going to move past a certain point, because the ceiling is the operating cadence of the organisation above it.

This is what makes corporate currents persist. The knowledge is correct. The metrics are correct. The intervention is correct. It’s the scope that’s wrong. The director changed the thing she could change and measured the thing she could measure, and both confirmed her thesis. The plateau wasn’t a failure of execution. It was the system absorbing local improvements without changing the behaviour of the whole.

Seeing the water

The fish don’t know they’re in water, but they know how to navigate a reef. We can make local changes, improve our corner of the ecosystem. But the water itself; the operating cadence, the reward structures, the way progress is defined upward; nobody designed it. It evolved. A thousand rational choices, each one a best fit to the conditions of the moment: board expectations, investor rhythms, sales cycles, regulatory reporting. Over time, those choices calcified into an environment that everyone inhabits and nobody owns.

But ecosystems aren't static. Evolution is a continuous process. The director who sees the water is in a different position to the one who doesn't. She can't boil the ocean. But she can stop treating the plateau as a team problem and start making the tension between what she measures and what the organisation rewards visible to the people who set the conditions. That's not a transformation. It's a shift in pressure. And pressure, over time, is how environments change.