Send us a textWhether to go for iterative deployment or the big bang is always subject to debate. But one factor that is often missed is the number of issues you might get on the day of deployment. As well as, the number of resources that you may require to avoid and control the impact of business disruptions. Most consulting companies would often advise against massive rollouts. The smaller the deployment, the more manageable it is. But that may not always be possible due to the system architecture. And the amount of additional temporary overhead that may be required to support a phased deployment.In today's episode, our guests, Nate and Jess Schisler share their insights on Lululemon’s case study of a massive rollout of their ERP and WMS. They also discuss the specific decisions that led to them opting for the one-weekend rollout despite their system integrator advising otherwise. Finally, they share details about the architectural considerations and resulting inventory issues that required months of hyper-care post-deployment.For more information on growth strategies for SMBs using ERP and digital transformation, visit our community at wbs.rocks or elevatiq.com. To ensure that you never miss an episode of the WBS podcast, subscribe on your favorite podcasting platform.

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related