Send us a textMost people when they start on their ERP journey feel it's more of a science, which engineers can figure out easily. But then they quickly realize that irrespective of whether the model is built on a spreadsheet or a complex computer program, it relies on the quality of inputs and the context. And that’s what makes ERP implementations so hard as it’s really more of an art than a science. And just like the way an artist gets better as they get more experience under their belt, the chances of ERP implementations would be higher as you figure out the art of ERP implementation.In today's episode our guest, Tom Pierce, shares why ERP implementation is more of an art than science. He also talks about several issues related to ERP implementation projects such as how siloed culture impacts the outcome of ERP implementation, the disconnect between digital and physical processes, and how minor changes such as six vs twelve characters on bin number could result in more than 300 programming changes. Finally, we discussed some controversial concepts related to enterprise architecture such as single vs multiple sources of truth, the order of migration for different ERP components, and prioritization of features whether you should be first focusing on simpler concepts or edge cases that are likely to break your architecture and systems.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