Renan Guedes, the CEO of Exed Consulting, has sat in more go-live war rooms than most people have had coffee. And he keeps seeing the same pattern:

“Companies celebrate go-live as the finish line, when it is actually where the hardest work begins”.

I had the chance to discuss this with Renan Guedes and SAP’s Richard Howells on this week’s Future of Supply Chain podcast. Renan puts it in a fun analogy where most supply chain transformations treat go-live like a wedding reception: months of preparation, a big celebration, photos, applause and then everyone goes home.

Renan put it, “The relationship starts after the wedding reception, usually with a hangover.”

But what separates the transformations that create lasting value from those that become expensive technology projects? Renan’s experience points to four lessons that consistently make the difference.

1. Go-live isn't where transformation succeeds or fails, it's where the real work begins.

The hangover is real. Users are slow. Workarounds multiply. Someone builds a spreadsheet “just for now,” and you sit there trying to figure out why things are drifting; then you have a support ticket queue and a knowledge base nobody reads.

Renan saw this firsthand with a large telco company in Latin America that went through a 3-year company-wide transformation. Every business unit was tracking well, until one month one area’s forecast accuracy crashed and inventory spiked for no obvious reason.

“When we interviewed the team, we realized that during that particular month, the system had a problem during the forecasting run, so they didn’t use the system forecast. They did something on their own in the spreadsheets and used that instead. If we hadn’t caught it, the next month would have been worse. Over time, they could have lost the value of the investment entirely in that area.”

The team fixed the root cause, realigned the process, and that business unit was back on track the following month.

Had nobody been measuring, that one quiet workaround would have become the new normal, and the new normal would have slowly swallowed the entire investment in that area.

2. Start with the business outcome, not the technology solution

The technology conversation often starts before the business problem is fully understood. When that happens, companies risk investing in solutions without addressing the real constraint holding the business back.

Renan saw this play out with a cosmetics company in Brazil. What started as a request for a technology solution turned out to be a much simpler business decision.

The company was struggling with high logistics costs. Because of insurance limits, they could not fully load their trucks without exceeding the covered value of the shipment. The team believed the answer was a transportation management system and had already started down the familiar path: demos, proof of concepts, vendor evaluations, and procurement discussions.

Renan asked one question: "If the insurance won't let you fill the truck, why aren't you using smaller trucks?" Nobody had thought of that.

No system. No implementation. No six-figure project. Just a different vehicle strategy, and the cost reduction was massive.

The real problem wasn’t surfaced until someone sat across from the VP of Logistics and asked what was actually going on. The business had handed the problem to IT. IT translated it into a system requirement. The requirement became an RFP. And the RFP never mentioned insurance caps. It said: implement a transportation management system.

Renan adds: “Technology is an enabler for change, but it's not why we do things. It's not the purpose. We need to go back to the purpose, to the outcome we are looking for. If you don't have that in place at the start of a project, you don't know if you've been successful when you go live or a year after you've gone live.”

3. If you're only measuring system adoption, you're missing the point of transformation

A system can be fully adopted but still fail to deliver the value the business expected.

Renan sees this as one of the biggest disconnects in digital transformation: companies often measure whether people are using the technology, but not whether the technology is improving the business.

“There is a misalignment between how IT and software companies measure adoption, how business or change management measures adoption, and how real results could get from it.” says Renan.

IT teams often look at system activity: user logs, transactions, performance, and whether users are engaging with the functionality that was implemented. Business teams often measure adoption differently, focusing on whether people are trained and capable of using the system effectively.

But these measures miss the most important question: is the business getting the outcomes it invested in?

Are inventory levels improving? Are freight costs decreasing? Is forecast accuracy getting better? These are the metrics that justified the transformation in the first place.

Renan believes many organizations avoid measuring these outcomes because they are afraid of what the numbers might reveal.

“People are often afraid of the judgment that comes with showing that an investment is not delivering the expected results. The first reason people avoid measuring outcomes is fear.”

But measurement is not a threat; it is what enables improvement. “What we get from measuring is confidence,” he explains. By tracking business results over time, organizations can identify when a transformation is drifting and take action before problems become permanent.

Renan saw this with a customer that went through a difficult transformation with significant resistance to changing existing ways of working. After go-live, skepticism remained until the team started measuring the outcomes that mattered: inventory levels, freight costs, and forecast accuracy.

When people saw the results, they realized the effort behind the transformation had paid off.

As Renan puts it: “Going through the process of change creates value and makes the organization more prepared to change again. This creates a flywheel that makes your organization increasingly capable of transformation.”

4. Digital transformation is the foundation for future resilience and AI

“Everyone wants to do something with AI. But many processes and many companies are not even digitalized yet,” says Renan. Before organizations can scale AI, they need the basics in place: digital processes, reliable data, the right partners, and teams prepared to work differently.

Renan explains: “If you want to use AI and get value from it, things need to be digital. You need to have great data. You need to have great partners and great team on board. Once you have all of that, maybe you can go to AI with great results because the other way around is very difficult. There are no shortcuts.”

For supply chains facing increasing uncertainty, resilience will not come from adopting the newest technology first. It will come from building the capabilities that allow organizations to adapt when conditions change.

A successful transformation is not about finding the perfect technology, celebrating the go-live, and moving on. Just like a relationship, the value comes from what happens after the celebration: the commitment, the adjustments, and the continuous effort to make it work.

Learn how to improve supply chain digital transformation success, drive technology adoption, and unlock business value beyond go-live in the latest episode of Future of Supply Chain.