Are you ready for logistics automation? Take our readiness quiz to find out!
Rendezvous 2026 panel blog: Why supply chain projects succeed or fail on people
Change Management in Supply Chain Projects: 5 Lessons From the Floor
Most operations leaders have lived through a project that looked solid in the steering committee and then struggled on the floor. The system was configured and go-live held, yet the operation spent months fighting the new way of working.
At Rendezvous 2026, our Managing Director Melanie Charles asked four operators to walk through real projects that went sideways before they succeeded. Their answers kept returning to change management in supply chain projects, and to the people who have to run the new process on Monday morning.
The panel brought very different projects to the stage. Bill Conrad, former President and CEO of Prime Source Foods, moved a foodservice distributor out of a 1940s-style building while implementing a new WMS. Mark Moore, President of CMC Design Build, converted a dry warehouse into a freezer and cooler on a schedule cut by more than half. Samantha Jones, VP of Distribution at Hanna Andersson, automated the post-pick operation of a single-site DC. Mark Whitlock of Midwest Distribution, who volunteered from the audience, rebuilt how his company works in six months.
What does change management in a supply chain project actually involve?
Mark Whitlock put it plainly: every project comes down to people, process and systems, “and the people side is the biggest.” Whether a team resists a change or adopts it depends on the people you work with, so he spends his early weeks understanding the current state and the future vision, then translating both into what each person does and why.
“You have to put the people first,” he said. “You have to help them understand it and then teach them the system around it.” In practice that means a training plan that starts with the purpose of each role before anyone sees a screen. On his most recent project he spent about eight weeks walking the warehouse and listening before reorganizing and reracking, and the physical fixes he made for the packing team earned more trust than any system demo.
1. Why does a team’s biggest strength become a liability after go-live?
In Prime Source Foods’ old building, supervisors and managers had the authority to do whatever it took to get product out the door, and that improvisation kept the operation running for years. “In the new building, that became a liability,” Bill said. With a WMS now directing the work, “our team was trying to figure out how to take the WMS apart.”
The cultural impact was the one thing the team had not fully thought through. The lesson for anyone planning a WMS implementation is to map the decisions people make informally today, decide which ones the system will own after go-live, and tell the floor before the cutover rather than after the first workaround.
2. How do you build buy-in when people don’t believe the project is possible?
Bill’s team had never used scanners and still moved product to the dock with two-wheelers, so a modern warehouse was hard for them to picture. Some people were dead set against the change. What gave the project its urgency was an honest look at the old building, which put the longevity of the company at risk.
From there he formed two working groups: a 15-member leadership and supervisor team that owned the transition to the new building, and a five-member WMS team that owned the technology. Those two teams made most of the decisions. “I got out of the way, I put it on them, and so there was real buy-in when we were done,” he said. An earlier ERP implementation in 2016 helped too, because the team walked into the WMS project with some confidence already earned. “A little bit of practice goes a long way and builds confidence.”
3. What changes when the schedule is cut in half?
Mark Moore’s team had helped Maines Paper & Food Service win new business that required converting a dry box into a freezer, cooler and refrigerated dock. The plan assumed about seven months of engineering, permitting and construction. The call came in July: the facility needed to ship on October 1, and the go or no-go decision was due in two days.
The client’s own list was just as tight, with staffing in two weeks and IT, material handling and a lease expansion in two months. What made it workable was trust. Instead of sending the job out for three bids, CMC stayed with subcontractors who knew the building. “All the members of the team need to trust each other. There needs to be a relationship,” Mark said. The owner, the contractor and the subcontractors negotiated overtime and risk openly, and the firm added a new first rule to its procedures manual, one word long: “Think.” A rigid process cannot replace judgment when the plan meets a wall it did not expect.
4. How do you prepare a team that has never run a project this big?
For Hanna Andersson, the automation project was the largest investment the DC had made, on a legacy ERP and WMS so customized that several vendors were working inside the same system. Then 2021 arrived with component delays and a seasonal surge six times larger than forecast, landing in October when freight and labor were both scarce.
Sam’s answer for the next project is to give functional leaders a grounding in project management principles, such as charters, risk registers and contingency planning, without turning them into project managers. The other half is culture. She wants a team that is allowed to fail and will “feel really, really comfortable to be able to shout about those failures,” because a team that only reports green hides the root cause. Mark Moore described the same idea as present and approve: bring the problem along with a proposed solution, and the manager supports the call.
5. Why should planning continue after you think it is done?
Bill’s team finished its planning a couple of months before go-live, and he was ready to stop. He kept going on advice, and then COVID closed the Canadian border, so outside specialists could not come on site for the transition. “That extra preparation meant that we could pull the project off despite not having that physical help,” he said.
Sam made the same point from the other side of the cutover. As tempting as it is to skip front-end alignment once the contract is signed, the documentation pays off every time the project hits a bump. And training has to keep going, because “the go-live is simply the start of ownership.”
Where outside project management fits
Bill was candid that his team did not know much about running projects of this kind when it started. Prime Source Foods had worked with us for several years, and we recommended a dedicated project manager for both the building and the WMS implementation, then filled that role. Our team kept the schedule honest and pushed decisions and culture in the right direction, including remotely once the border closed.
That is the role we play on most facility implementation and supply chain technology projects, whether the system is an Oracle NetSuite ERP or a WMS. We plan the people side alongside the configuration, because adoption on the floor decides whether the investment pays back.
Find out where your project stands
If you are about to start an ERP, WMS or facility project, or you are in the middle of one that is fighting the floor, a first conversation with our team covers your timeline and the points where adoption on your floor is most likely to stall. You leave with a clear view of the risks and what to plan for before go-live.