Beyond Change Management: Introducing the R.E.W. Principle for Technology Adoption
Organizations have no shortage of change management frameworks.
Whether you follow Kotter, ADKAR, or another well-established methodology, most frameworks answer the same question:
How do we implement organizational change successfully?
But there is another question that receives far less attention.
A question that should probably be answered first.
Should this technology replace our current process, expand it, or should we wait?
Surprisingly, most organizations skip this discussion entirely.
They assume that once a new technology appears, the objective is to replace what already exists.
History suggests otherwise.
The Missing Decision
When organizations evaluate new technologies—whether ERP systems, Artificial Intelligence, automation, or robotics—they often begin implementation planning before answering a more fundamental strategic question.
What relationship should the new technology have with the existing system?
Should it completely replace the current process?
Should it operate alongside existing processes while the organization learns?
Or is the organization simply not ready yet?
We believe this decision deserves its own framework.
Introducing the R.E.W. Principle
The R.E.W. Principle stands for:
Replace
Expand
Wait
Unlike traditional change management methodologies, the R.E.W. Principle is not an implementation framework.
It is a decision-making framework.
It helps leaders determine the appropriate adoption strategy before planning the transformation itself.
Think of it as the decision that happens before change management begins.
Replace
Replacement is appropriate when the organization has high confidence that the new technology delivers superior results and the existing process no longer provides meaningful value.
Several conditions should exist before choosing this strategy:
The technology has reached sufficient maturity.
Failures are manageable.
Recovery procedures are well understood.
The legacy process no longer contributes significant resilience or unique capabilities.
In these situations, maintaining both systems only creates unnecessary complexity.
The objective becomes complete replacement.
Expand
Expansion is often the most misunderstood strategy.
Many leaders interpret expansion as hesitation.
In reality, expansion is frequently the fastest path toward successful replacement.
Under an expansion strategy, the new technology begins creating value immediately while the existing process continues providing operational resilience.
Examples include:
AI generating recommendations while humans approve decisions.
ERP systems operating alongside carefully controlled spreadsheet processes.
AI copilots assisting software developers while engineers remain responsible for production code.
Voice radio operating alongside Morse code during the early years of maritime communications.
Expansion allows organizations to learn.
Learning builds confidence.
Confidence eventually enables replacement.
Wait
Waiting is often viewed as failure.
Sometimes it is the most responsible strategic decision.
Organizations should consider waiting when:
Technology maturity remains uncertain.
Regulatory environments are still evolving.
Organizational capabilities are insufficient.
Failure recovery mechanisms do not yet exist.
Operational risks outweigh expected benefits.
Waiting is not rejecting innovation.
It is preparing the environment so innovation can eventually succeed.
The Three Questions Every Leader Should Ask
Before deciding between Replace, Expand, or Wait, leaders should answer three fundamental questions.
1. Does the technology actually outperform the existing process?
New does not automatically mean better.
Many technologies excel under normal conditions while performing poorly during exceptional situations.
The first objective is understanding where the technology creates genuine value.
2. Can the organization recover if the technology fails?
Every technology fails eventually.
Artificial Intelligence produces incorrect outputs.
ERP implementations encounter unexpected scenarios.
Automation breaks.
The relevant question is not whether failure is possible.
The relevant question is whether the organization knows how to recover.
Organizations with strong recovery capabilities can adopt new technologies far more aggressively than organizations without them.
3. What valuable capability disappears if we remove the legacy system?
This may be the most overlooked question in technology consulting.
Every legacy process exists because, at some point, it solved a problem.
Sometimes that problem no longer exists.
Sometimes it still does.
Before eliminating a process, organizations should understand what hidden resilience it currently provides.
The objective is not to preserve outdated systems forever.
The objective is to avoid removing capabilities the organization still depends upon.
Why This Matters for AI
Artificial Intelligence is creating enormous pressure for organizations to transform quickly.
Many companies ask us:
"How fast should we implement AI?"
The better question is:
Where should AI replace existing work?
Where should it expand existing capabilities?
Where should we intentionally wait?
Those three questions produce very different implementation strategies.
Trying to replace everything at once often creates unnecessary organizational resistance.
Waiting too long creates competitive disadvantages.
Expansion frequently provides the balance between innovation and operational resilience.
Rethinking Technology Adoption
The R.E.W. Principle does not replace change management.
It complements it.
Traditional frameworks explain how to help people adopt change.
The R.E.W. Principle helps leaders determine whether replacement, expansion, or waiting represents the most appropriate strategic decision in the first place.
Only after answering that question should implementation planning begin.
Technology transformations rarely fail because the technology itself was inadequate.
More often, they fail because organizations chose the wrong adoption strategy.
Sometimes the answer is to replace.
Sometimes the answer is to expand.
Sometimes the smartest decision is to wait.
The challenge for leaders is knowing which one applies.
That is precisely the decision the R.E.W. Principle is designed to support.