Season's Savings | ₹5/mo for 3 months
₹199/month after first 3 months. Renews automatically. Terms apply.
Day 2 Operating Model: What Happens After Go-Live (And Why Transformations Fail)
Failed to add items
Add to cart failed.
Add to wishlist failed.
Remove from wishlist failed.
Follow podcast failed
Unfollow podcast failed
-
Narrated by:
-
Written by:
Everyone plans for go-live. Almost nobody plans for the day after.
On this episode of Business Uncomplicated, Rich Nazzaro and Andy Worobel dig into Day Two: the day after go-live, when a digital transformation either starts paying off or quietly falls apart. Change management matters, but it isn't enough. Day Two is about building an operating model that changes how the business actually runs.
Rich and Andy cover why process mapping should come before requirements, how to use UAT to test your operating plan (not just the system), and why "adoption" is the laziest metric in the world. Rich shares the Dell story where server deals were being "lost" to Apple, and why only 12% of organizations sustain transformation gains past three years (McKinsey). They also get into re-baselining the business case when scope gets cut, holding leaders accountable for results, bringing finance into the operating rhythm, and the one meeting every company should kill.
If you're a CIO, CRO, RevOps or transformation leader running a Salesforce, CRM, CPQ or AI program, this one's for you.
In this episode:
- What "Day Two" means and why most programs ignore it
- Why technology is just a business process in a system
- Using UAT to test SOPs, dashboards and metrics
- Leading vs. lagging indicators and why adoption isn't enough
- Re-baselining your business case to protect ROI
- Rapid fire: the meeting to kill, and whether rhythm or strategy fails first
- (00:00:02) - Catching up and the pace of the year
- (00:00:46) - Budget season and constant change
- (00:02:39) - Introducing Day Two: the day after go live
- (00:03:28) - Why change management alone isn't enough
- (00:05:09) - Fragmented initiatives and missing process ownership
- (00:06:27) - Process mapping and learning from Sapient-era discipline
- (00:08:12) - Technology as a manifestation of business process
- (00:09:03) - Client-centric process design and hidden variations
- (00:10:30) - Planning for ownership before the project even starts
- (00:12:02) - Measuring success beyond go-live and baseline data
- (00:13:45) - Operationalizing work streams and overlooked dependencies
- (00:15:29) - Consultants guide, clients decide
- (00:16:38) - Using UAT to rehearse the future operating state
- (00:19:58) - The Day Two to Day 60 problem
- (00:21:37) - Building SOPs and leading vs lagging metrics
- (00:24:39) - Adoption metrics and the real data behind behavior change
- (00:27:11) - Quarterly reviews and real accountability
- (00:34:20) - Why transformation gains fade after three years
- (00:35:43) - Re-baselining business cases and confidence checks
- (00:37:56) - AI, iterative design, and evolving systems
- (00:42:03) - Finance partnership and bottom line vs top line thinking
- (00:44:04) - Programs as part of a bigger continuum
- (00:45:02) - Rapid fire: meetings, rhythm, and strategy
- (00:51:10) - Closing thoughts on consultants and operationalizing change