Every few years, organizations reach a point where something has to change. The work isn't flowing the way it used to. Priorities compete with each other. Teams are busy, but customers aren't seeing value fast enough. The classic tension surfaces: time, quality, resources. You can't maximize all three. So how do you prioritize? How do you schedule? How do you organize people to actually deliver?

I've watched several organizations go through these moments, including my own at various points. The conversations are always familiar: rethinking how to schedule work, how to use resources more effectively, how to get value to customers faster. And the proposed solutions are familiar too. Cross-functional teams. Cost optimization initiatives. Hackathons to spark innovation. New team structures (call them pods, squads, or whatever the current vocabulary prefers). Each attempt is a hypothesis about what's blocking progress. Each one carries genuine hope that this time, things will be different.

What I've noticed, across organizations, reorgs, and a few mergers I've lived through, is that these change initiatives follow predictable patterns. Some spark real movement. Most quietly fade back into the existing structure. The question that's been on my mind is: why? What separates the changes that stick from the ones that get absorbed?

The structure that resists

There's a famous observation from computer scientist Melvin Conway: organizations produce systems that mirror their communication structures. Your software architecture ends up looking like your org chart. Teams organized by layer (frontend, backend, database) produce layered architectures. Cross-functional teams produce more modular designs.

The corollary that's less discussed: the system then reinforces the structure. Once you've built something that requires coordination between three teams, you've created a reason for those three teams to exist. The architecture becomes a kind of institutional memory, encoding the organizational decisions that created it.

This is why change initiatives often feel like pushing against something. They are. When you propose cross-functional pods, you're not just suggesting a new way to organize people. You're implicitly challenging the systems, processes, and communication patterns that evolved around the old structure. The existing structure has gravity.

Peter Senge, in his work on organizational change, describes how organizations naturally tend to revert to old patterns, like a stretched rubber band snapping back to its original shape. It's not that people are resistant to change (though some are). It's that the system itself has a kind of immune response. New initiatives that don't fit the existing structure face an uphill battle, not because anyone is actively hostile, but because the structure wasn't designed to accommodate them.

The pace problem

Here's another pattern I've noticed: change initiatives often fail because they expect everyone to move at the same speed.

There's a well-documented model called the Technology Adoption Life Cycle. It shows how new ideas spread through a population: innovators first (about 2.5%), then early adopters (13.5%), then the early and late majority (34% each), and finally the skeptics (16%). Geoffrey Moore identified the "chasm" between early adopters and the early majority, that gap where enthusiasm hasn't yet translated into mainstream acceptance.

This curve applies to more than technology. It applies to any change. When an organization launches a new way of working, a small group will embrace it immediately. They're energized by the novelty, willing to tolerate the rough edges, excited to experiment. But the majority will wait. They want to see if it actually works. They have legitimate questions: Does this solve a real problem? Will it last, or is it the initiative of the month? What happens to my current work while we're "transforming"?

Neither reaction is wrong. The early adopters are learning what works and what doesn't. The skeptics are protecting against premature optimization and asking questions the enthusiasts overlooked. A healthy organization has both. The rhythm of adoption emerges from their interaction.

The problem comes when leaders expect universal adoption on day one. When the hackathon generates exciting prototypes but there's no path to production. When the cross-functional pod is announced but the incentive structures still reward the old silos. When the cost optimization initiative gets executive attention for a quarter and then quietly disappears from the agenda.

What actually sticks

So what separates the changes that take hold from the ones that fade?

From what I've observed (and from some reading that's helped me make sense of it), a few patterns emerge.

Change is slower and more incremental than we want to admit. Matt Ridley, in his book on innovation, makes the case that breakthroughs are almost never sudden. The steam engine evolved over decades. The light bulb had dozens of contributors. Innovation thrives on small experiments, not grand transformations. The same is true for organizational change. The initiatives that stick tend to be the ones that start small, prove value in a contained space, and expand gradually. The ones that try to transform everything at once tend to exhaust themselves.

Intrinsic motivation matters more than mandates. Daniel Pink's research identifies three elements that fuel engagement: autonomy (directing our own work), mastery (improving at something meaningful), and purpose (connecting to something larger). When change initiatives succeed, they often do so because they tap into these motivations. Cross-functional teams can increase autonomy by giving people more ownership of outcomes. Hackathons create space for mastery and experimentation. But when these same initiatives are imposed as mandates, without addressing the underlying motivations, they tend to feel like extra work rather than genuine improvement.

Sustainable pace beats heroic sprints. Cal Newport's work on productivity makes the case against constant busyness. Real progress comes from intentionality: doing fewer things with more focus. Organizations that successfully change tend to protect space for people to actually engage with new ways of working. The ones that pile change initiatives on top of existing workloads find that people quietly drop the new stuff when the pressure gets high enough.

The structure has to actually change. This seems obvious, but it's remarkable how often it doesn't happen. New team structures get announced, but the old reporting lines stay in place. Cross-functional collaboration is encouraged, but the performance reviews still measure individual output by specialty. The hackathon produces a prototype, but there's no budget to take it further. For change to stick, something in the underlying structure has to shift: incentives, resource allocation, decision rights. Otherwise, the rubber band snaps back.

The rhythm

I don't have a framework for managing organizational change. If I did, I'd probably be selling consulting services instead of writing blog posts. What I do have is a growing appreciation for the rhythm of it.

Change is rarely as sudden as the announcements suggest. Resistance is rarely as irrational as it appears. The tension between time, quality, and resources doesn't get resolved; it gets navigated. Organizations are not machines that can be reprogrammed. They're more like ecosystems, where new species have to find a niche and existing species adapt or don't.

The initiatives I've seen succeed tend to have a few things in common: they start small enough to prove value before demanding universal adoption, they tap into genuine motivations rather than relying on mandates, they actually change something structural rather than just adding a layer on top, and they have patience for the natural pace at which people adopt new ways of working.

The ones that fade tend to share the opposite pattern: big announcements, universal rollouts, mandates without motivation, and structures that stay unchanged underneath the new vocabulary.

Every cycle, I watch organizations try various experiments. Cross-functional teams. New ways of prioritizing. Attempts to break out of established patterns. Some work. Some don't. The rhythm of it has started to feel familiar.

The question isn't how to eliminate resistance to change. It's how to participate in the dance, recognizing that the music has a tempo of its own.