Before we could move forward, we had to understand exactly where our processes were hitting a wall. That meant starting with a full health check across every core function: finance, warehousing, procurement, sales, and beyond. We looked at how transactions flowed, where handoffs stalled, and how data was being captured, shared, or lost along the way. It quickly became clear that our problems weren’t isolated. They were systemic.
Once we had that baseline, we went straight to the heart of it: the data. Poor-quality data was undermining everything: product codes were inconsistent, pricing data was duplicated, vendor records had gaps. Cleaning up our master data was no small job, but it was essential. Once that work was done, I could finally look at a report and know it reflected the truth.
With better data came the chance to revisit how our processes actually worked. We didn’t just want to replicate old habits in a new system. We mapped out how we wanted things to run, using SAP’s standard capabilities as the reference point. That forced us to rethink how quotes got created, how inventory moved, and how approvals were managed. In many cases, simplifying our processes created efficiencies we hadn’t even been aiming for.
And of course, none of it would stick without our people. This wasn’t just about learning to click the right buttons. We spent time explaining why the changes mattered, showing how their work connected to business outcomes, and giving them space to ask questions and test things out. It wasn’t always smooth, but gradually, people stopped seeing SAP as an obstacle and started seeing it as a tool they could trust.
One of the biggest turning points came when team members who had previously avoided SAP started coming to us saying, “I’m still doing this in Excel, how do I move it into SAP?” That shift, from resistance to ownership, was when I knew the culture was changing.
