
Sign up to save your podcasts
Or


Story: Six months after go-live, the CEO asks where the benefits are — while the old spreadsheets quietly return. This is an illustrative scene, not a real case.Tension: Programmes were mobilised for the milestone, never campaigned for adoption.Discipline: Readiness before milestones, role-based capability, manager enablement, and adoption-to-value measurement.Diagnostic question: Six months after your go-live, will the new way still hold?Chapters:1. The Question Behind the Name2. Twenty-Five Years in the Room3. The Four-Part Discipline4. Diagnose Before You InvestDiagnose before you invest: tapasadvisory.com/diagnosticRam Narayanan, Transformation Leader, founder of TAPAS Advisory, creator of CHANGEReadyX™.
An ERP business case dies after go-live when the program was mobilized for the milestone and never campaigned for adoption — and AI layered on that gap only makes the workaround faster. In this episode, Ram Narayanan shares four takeaways from his practice: transformation before technology, governance as the foundation, data readiness, and process discipline before intelligence. Why do ERP implementations fail after go-live? Because adoption was never campaigned for. Chapters: 1 The Boardroom Demo, 2 The Hidden Failure, 3 Transformation First, Governance Underneath, 4 Data Clean, Discipline Intact, 5 The Diagnostic Question. tapasadvisory.com — Ram Narayanan, Transformation Leader | Architect of CHANGEReadyX, TAPAS Advisory.
An ERP business case dies after go-live when the program was mobilized for the milestone and never campaigned for adoption. In Episode 4 of CHANGEReadyX Insights, Ram Narayanan answers the most expensive question in ERP: when should change management begin? During ERP planning — with a four-part discipline: readiness before milestones, role-based capability diagnosis, manager enablement, adoption-to-value measurement. Chapters: 1) The Question Every CIO Asks Too Late 2) The Milestone Trap 3) Start During Planning: The Four-Part Discipline 4) Go-Live as a Readiness Decision 5) Your Diagnostic Question. Run the diagnostic at tapasadvisory.com/diagnostic. — Ram Narayanan, Transformation Leader | Architect of CHANGEReadyX, TAPAS Advisory
Episode 3 of CHANGEReadyX Insights with Ram Narayanan, Transformation Leader and Architect of CHANGEReadyX™, TAPAS Advisory. A conversation on ERP transformation readiness, adoption, and what separates go-live from real change.
The AI tool went live. The licenses are active, the dashboards are up — and nobody changed how they work. Ram Narayanan on why AI adoption fails at the workflow layer, and how CHANGEReadyX™ diagnoses readiness before you scale. From TAPAS Advisory.
The chart changed. The roles, the boxes, the reporting lines — all redesigned. But the work didn't. Ram Narayanan explores why operating model redesigns fail at the human layer, and what the CHANGEReadyX™ lens reveals about readiness before restructuring. From TAPAS Advisory.
ERP transformations don't fail at go-live. They fail at adoption. Millions committed, go-live declared a success — then adoption stalls, workarounds creep back, and the business case quietly dies. In this episode, Ram Narayanan explains the missing layer: people-and-adoption — readiness before milestones, role-based capability diagnosis, manager enablement, and adoption-to-value measurement. Learn more at tapasadvisory.com/erp-transformation.