Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is Evolution Just a Slow Revolution?

In managing a product, a team, a company - or even yourself - I almost always see two camps.

The evolutionists.

They believe change should be careful. Gradual. Step-by-step.

  • “Don’t break it - improve it.”

  • “Let’s avoid sharp moves.”

  • “The system needs time to adapt.”

And then there are the revolutionists.

  • “Cut it now.”

  • “Change the model.”

  • “Shut down the old, build the new.”

  • “Otherwise it won’t fly.”

For a long time, I considered myself an evolutionist.
Revolutions felt like impatience. Like weak thinking. Like a failure to work with complex systems.

But at some point, I looked at evolution from a different angle.

And what became uncomfortable is this:

Evolution isn’t soft.
Evolution is just revolution stretched over time.

We call it “gradual” only because we zoom out too far.
Zoom in - and you’ll see something else.

Evolution doesn’t improve the old.
It eliminates it.


Biology Doesn’t Negotiate

In biology, this is obvious.

A new function doesn’t negotiate with the old one.
A new species doesn’t compromise.

It displaces.

Not because it’s aggressive - but because otherwise it doesn’t survive.

Old neural connections don’t “politely make room” for new ones. They degrade if unused. The brain doesn’t preserve outdated strategies out of respect for experience.

From a neuroscience perspective, learning is not an upgrade.
It’s replacement.

Strengthening one pattern weakens another.
Every stable new behavior forms at the cost of an old one.

It’s a biological zero-sum game.


The Same Happens in Organizations

In management, it works the same way.

A new operating model doesn’t “sit on top” of the old one.
A new culture doesn’t “enrich” the previous culture.
New metrics don’t “complement” old incentives.

They kill them.

If you introduce OKRs but still reward individual heroics - guess which system survives?
If you say “we’re Agile now” but keep centralized decision power - what actually changed?

When change is slow, it feels civilized.
But that’s just a matter of scale.

A system either restructures - or it defends itself.
There is no third option.


The Evolution Trap

Here’s the dangerous part.

When a leader says, “Let’s evolve,” very often what they really mean is:

“Let’s delay the death of the old system.”

They’re trying to preserve an identity that is no longer viable - under the banner of stability, empathy, or risk management.

But evolution doesn’t preserve identity.

It optimizes for survival.

If old patterns: roles, incentives, processes, metrics, power structures - are not truly dismantled, nothing changes.

You get:

  • Cosmetic transformation

  • Process theater

  • A sense of motion without real outcomes

And that’s how “Agile transformation” becomes a branding exercise instead of a structural shift.


Why This Matters in Agile

Agile, at its core, was never about adding ceremonies.

It was about killing certain management patterns:

  • Killing rigid upfront certainty

  • Killing information silos

  • Killing authority without feedback

  • Killing progress measured by activity instead of value

When those patterns remain alive, Agile becomes an overlay - not a shift.

And overlays don’t evolve systems.

They exhaust them.


The Real Question

The paradox is this:

Real evolution almost always feels like revolution from inside the moment.

And pseudo-evolution is often the most conservative way to change nothing.

So the question isn’t:

Are you an evolutionist or a revolutionist?

The real question is:

Are you willing to let the old die?

Because without that - there is no evolution.

Only preservation disguised as progress.

1 comment

Aubrey Wade
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 20, 2026

I'm an agile / process expert by trade and very intrigued by your article. Thanks so much for posting! I love the extremes of your article. 

Any change has to have a starting place. And needs to have companions. The best change is something that isn't resisted, but when others attach to it, vs forced. (IE: you are able to network and get others to join you vs forced compliance.)

I think the question here is it better for "evolution" to really include solicitation to network change informing and adoption for a hard change? Or is it bad that the old dies? Maybe that is really the question. If it is, is it really bad? 

I mean, isn't there a reason we have evolution AKA Revolution? 

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events