So, you’re about to experience a brand new ERP implementation and you’ve got your whole timeline planned out. There’s a go-live date circled on the calendar. But what does your company’s go-live date really represent? Is that at what time the first stage rolls out, or when every single part of the system launches? That’s the dissimilarity between a phased ERP implementation and an all-in, big-bang go live. The two are very different philosophies of ERP implementation and go-live. One seeks to just fling everyone into the total of the new system and figure out any kinks as an organization, and the other to stagger the roll out of the new ERP across departments and modules so that there are a number of small test environments for solving problems. That way, by the time the whole business is on ERP, the software is supposedly working smoothly.
Unsure whether should you phase in your new ERP implementation or take an 'all-in' approach? There’s no certain right answer when it comes to how to carry out your ERP implementation, only the right fit for your unique business needs. We’ll break down the general ideas behind each hypothesis and why you might want to pick one over the other.
The pervading theory of big bang implementation is that every functionality and module gets turned on the same date. This is a ‘throw them into the pool so they learn to swim’ style implementation. Of course, while the name may imply a state of slight chaos after go-live, that’s not of need true. A lot of planning will need to go into a ‘big bang’ implementation. The idea behind such a technique is that everyone in the company learns about the new software at the same time. Every co-worker will be able to help the next during the learning processes, and you won’t have to keep up training sessions for as along as a phased go-live would take. While this is admittedly a higher risk strategy, it can from time to time be the most reasonable, especially for smaller businesses where it would be extreme to split implementation out over departments that only contain a few people.
This won’t be the right solution for larger companies that don’t have a strong support network that can withstand being bombarded with questions and support tickets in the days after go-live. If you want to go big-bang mentality but are afraid that you won’t have a strong enough safety net in place, you might want to take advantage of outside consulting help. Your business can bring in ERP experts that are trained to communicate knowledge and solve real issues for the period of implementation to act as a springboard for all questions and concerns.
Phased implementation prefers the incremental approach to rolling out ERP modules. This is a less risky style of go-live, as it easier to roll back malfunctioning or poor new features if they haven't been implemented across the whole company. It will also put less strain on your project team, as they will be able to plan ahead and spread out their resources over the course of the whole phased implementation, rather than having to worry about different departments having problems with separate modules simultaneously. Phasing can happen in several different ways, as businesses choose the best style for their needs: you could roll out distinct ERP modules one at a time, the whole ERP systems across different business departments, or across different geographical offices, for example. Whatever option fits your best, the incremental style means you can focus the efforts of your support team and software experts on one task at a time.
Of course, phased implementation may not be the right choice for your company just because it seems less risky than big-bang style. As we’ve mentioned previously, it won’t be tenable in small-to-midsize businesses that only have a small group of employees. Phasing will also naturally augment the time a project takes not great for companies trying to stay on a strict go-live deadline or those who want to keep a combined sense of urgency and excitement about an implementation across the entire company.