Ever had one of those days where you think, "What could possibly go wrong?" and then, well, everything goes wrong? That's a bit like diving headfirst into system implementation without a plan. Trust me, I've been there, and it's less like a cool dive and more like a belly flop.
All growing businesses outgrow their systems over time. The pain comes on slowly, like a subtle ache in your knee after a little too much weekend running. We tend to treat that problem in our business much like the pain in our knee. We ice it. We bandage it. We wait and hope for the best. Much like a wonky knee, sometimes that’s enough, but many times it is not.
If you aren’t planning to run a marathon, or even a 5k, you can probably work around it. But what if you are? I bet your business is planning on growing. Growth only works with a good solid foundation. An antiquated, patched together system is NOT a good foundation.
Instead, you need a training plan for your business’s marathon. You need to realistically evaluate your system needs before they become a problem and have a plan for keeping them healthy and thriving to support your business as it grows.
I’ve been doing system implementation and integration work for over 30 years. I have seen and done every kind of implementation, conversion, and overhaul. My experience has given me a very clear understanding of what makes these projects work, and what doesn’t. Let me share with you some of my wisdom.
Failure is an Option
According to Gaertner, 75% of ERP system implementation projects fail on their first go around. Why is that? Several things can impact that. But I believe inadequate planning is one of the main reasons.
Planning might sound as appealing as scheduling a root canal but hear me out. Without it, you're basically choosing to walk blindfolded into a minefield. Here's the kicker: The average cost of IT downtime is about $5,600 per minute. Yeah, per minute. Let that sink in while you think about your last "unplanned downtime."
The Art of the Plan
Good planning is like having a map in a treasure hunt. It doesn't take the fun away; it just stops you from wandering into quicksand. For instance, think about when you're planning a road trip. You don’t just throw a dart at a map and drive. You think about stops, snacks, and the playlist. System implementation planning is the same, just swap snacks for stakeholder meetings (though snacks are still welcome).
Planning takes time, good people and money. Many businesses underestimate just how much of those things are required. It is human nature to get anxious to “get on with it”. We like to shortcut the planning part of our projects and get to the “doing” part of it. We also tend to be stingy with our “best” people, which can result in some of our not best people making plans and decisions for our company that will resound for years and years to come.
And money. It’s always about the money. Companies often don’t allocate ANY money to the planning process. That’s a mistake. Planning takes research, trial runs, project development and training. All of those things cost. Don’t shortcut your plan by being cheap.
The Power of Proper Testing
Testing your new system before going live isn’t just a good practice—it’s your sanity saver. Imagine you’ve just launched a new billing system. Now, instead of sending out invoices, it’s sending out happy birthday wishes. Sure, it’s friendly, but that won’t look great on your quarterly financials.
Testing isn’t a one and done step. Testing needs to be built into the project starting in the planning phase and continuing into post-implementation. Key elements of the project need to be tested and retested in different ways. The more complex the system, the more interactions with other systems, the more voluminous the data, the more testing required. Don’t shortcut the testing.
Real-Life Mishaps (Because Misery Loves Company)
Here’s a fun story: Once, during a particularly enthusiastic system rollout that skipped adequate testing, a company found out that their "automated" system was more "auto-mated." It mated data that should never have been together, creating a chaotic data offspring no one knew how to handle. Lesson? Test, then test again, and maybe once more with a cherry on top.
Bringing It All Together
Successful system implementation isn’t about avoiding change; it’s about managing it. Like directing a toddler-filled birthday party, you need to know who's doing what, where the emergency exits are, and always keep an eye on the clown (or in this case, your project milestones).
Want to avoid your project being a case study in what not to do? Plan meticulously, test religiously, and maybe keep a stash of headache meds handy.
Need a Navigator?
Embarking on a system implementation journey can feel like charting unknown territories. With over 30 years of experience in making technology work for businesses, I'm here to guide you through your system's marathon. Don't run into the wilderness without a map. Let’s strategize your next steps together. Reach out to me, and let’s ensure your system supports your growth smoothly and effectively.