Episode 02 · ERP transformation

The ERP went live.
So why was the business case dying?

Go-live is a milestone. Sustained adoption is what turns an ERP investment into business value.

“The system went live. The old habits did too.”A familiar post-go-live risk—told through an illustrative scenario.
Follow the story Explore the 4-part discipline
ERP+
People · Process · Value
System live ✓Technical milestone
Adoption?The value question
↗ Business valueEarned through behaviour
01 / The six-month-later test

The celebration ends.
The real test begins.

Imagine an ERP launch that appears successful. Six months later, employees have quietly returned to familiar workarounds. The software may be functioning—but the intended ways of working are not yet habits.

What the project dashboard says

“We delivered.”

  • ✓Go-live milestone achieved
  • ✓Core technical tests completed
  • ✓Training sessions delivered
What daily work reveals

“We haven't fully adopted.”

  • ↺Spreadsheets and parallel trackers return
  • ↺Manual workarounds bypass workflows
  • ↺Expected business benefits remain uncertain
“Go-live is a milestone. Value is a behavior.”Ram Narayanan · CHANGEReadyX™ Insights
02 / The discipline

Four moves that help sustain adoption.

Select each card to reveal the leadership question and a practical action.

01

Readiness before go-live

Find risks while there is still time to act.

+ Explore the action
Ask: Do leaders, managers and affected teams understand what must change?

Act: Identify readiness gaps, assign owners and resolve critical barriers before they become post-launch problems.
03 / Measure what matters

From launch milestones to people signals.

Explore the adoption meter. Adjust the illustrative score to see how a readiness conversation changes. This is a demonstration—not a validated assessment or benchmark.

Illustrative adoption readiness
38
Illustrative scenario: adoption risks need attention.
◎

Actual workflow usage

Are eligible transactions completed in the intended ERP workflow?

↻

Workarounds and rework

Are manual trackers declining, and are data quality and cycle times improving?

✦

Capability and reinforcement

Can people perform the work, and do managers reinforce the new behaviours?

04 / Quick interactive check

Would your organization pass the adoption test?

Select the statements you can support with evidence. Your result is a simple discussion prompt, not a formal readiness score.

Post-go-live adoption checklist

Be honest. “We think so” is different from evidence.

5 questions
0/5
Start with evidence.

Select the statements your organization can demonstrate today. Unchecked items identify areas to investigate.

05 / The executive takeaway

Before investing another million, ask a different question.

Is the constraint technical, operational or behavioural? A focused readiness diagnostic can help leaders identify where intervention is needed and connect the response to adoption evidence.

CHANGEReadyX™ is a transformation-readiness and adoption diagnostic approach developed by Ram Narayanan through TAPAS Advisory. Its guiding sequence is Diagnose → Activate → Validate → Design.

Explore Ram's portfolio ↗ Read from the beginning ↑
Quick answers

ERP adoption, explained.

Why do ERP implementations struggle after go-live?

Technical implementation does not guarantee consistent use. Capability gaps, weak manager reinforcement, workarounds and poor linkage between adoption and business outcomes can all contribute.

How should ERP adoption be measured?

Combine workflow usage, role-based proficiency, process compliance, workarounds, manager reinforcement and relevant business performance indicators. Define a baseline, owner and measurement period for each.

What does change management contribute?

It helps people understand the change, build the required capabilities, adapt their behaviours and receive reinforcement after launch—connecting technology delivery with organizational adoption.