Stop Blaming the System: The Messy Truth About Bad Workflows
Many small and medium-sized businesses find themselves in a frustrating position, convinced that their ERP system has failed them. However, what if I told you that the real culprit often lies not within the software itself, but in the unchanged, undocumented, or outdated workflows that were stubbornly carried over from the past? It’s a bit like trying to fit a square peg into a round hole—no matter how hard you push, it just won’t work.
Statistics show that 50-75% of ERP projects underperform or outright fail. Take Hershey, Lidl, and Target Canada as prime examples; they all pointed fingers at their ERPs when the truth was far more mundane: poor planning and an unwillingness to adapt. Instead of blaming the tools meant to help them streamline operations, perhaps it’s time for these businesses—and yours—to take a closer look at their internal processes. After all, even the best technology can’t compensate for workflows stuck in yesterday’s mindset. Embracing change might just be your ticket to unlocking your ERP’s true potential.
The Real Problem: Workflow, Not the System
When it comes to the challenges businesses face, it’s easy to point fingers at outdated systems or technology. But let’s get real for a moment: the real problem often lies in your workflow, not just the tools you’re using. If you find yourself relying on manual workarounds, reverting to spreadsheets like they’re a comforting old friend, or witnessing glaring inconsistencies between departments, these are clear signs that your workflow is in desperate need of an overhaul.
Now, I get it—automation seems like an enticing solution. Who wouldn’t want to speed things up? However, automating a broken process is akin to putting a shiny new coat of paint on a crumbling wall. It might look good for a second, but underneath that facade lies chaos waiting to unfold even faster than before. Instead of solving problems, you’re just speeding up failure and creating more headaches down the line.
Take a step back and assess your workflows before diving headfirst into automation. Fixing these underlying issues will not only streamline processes but also enhance collaboration across teams. After all, no one wants their shiny new system to become another source of frustration!
One question that I like to ask my clients (or prospects) is why they are doing things a certain way. If the answer is ‘because that’s they way we’ve always done it’, and no one in the company seems to know why it’s done that way, that’s a red flag for me, re their workflows. I want to dig deeper, and find out what the end result is that they want to achieve with their system and then work backwards from there to review their existing workflows.
The Common Trap: New Tech, Same Old Problems
When companies invest in new software, it’s easy to slip into the mindset that this shiny new tool will magically resolve all existing issues. Unfortunately, this is often where the trap lies: expecting new technology to fix everything while unwittingly dragging along those pesky bad habits from old workflows.
Take ERP implementations, for instance. Many organizations dive headfirst into these projects without first mapping or standardizing their business processes. It’s like trying to fit a square peg in a round hole—over-customization becomes the name of the game as teams attempt to contort the system to accommodate outdated practices. This can lead to chaos, confusion, and ultimately frustration when employees find themselves wrestling with a system that was never designed for their needs.
And let’s not forget about “spreadsheet addiction.” Just because you’ve implemented an ERP doesn’t mean your team will suddenly abandon their beloved spreadsheets. In fact, many find themselves relying on them even more post-implementation—a classic case of old habits dying hard. So before you roll out that new software thinking it’ll be a panacea for all your problems, take a moment to reflect: Are you ready to leave those bad habits behind? If not, you might just end up with new tech but the same old headaches.
I often see heavy reliance on Excel, and I believe it stems from two factors … users want to stay in their comfort zones, and users fear learning the new system
Why Workflow Mapping Comes First
When it comes to implementing new systems or processes, skipping the step of workflow mapping is like trying to navigate a new city without a map. You might get somewhere eventually, but chances are you’ll end up lost, frustrated, and possibly in a part of town you didn’t intend to visit. Without workflow mapping, you configure blindly or based on assumptions that may not hold water.
Taking the time to map out both your current state and future state workflows before implementation is essential. This process doesn’t just serve as a guide; it uncovers bottlenecks and missed steps that could derail your efforts down the line. Think of it as a treasure hunt where the prize is efficiency and clarity.
Involving users in validation during this mapping process can make all the difference. They bring invaluable insights about daily operations that you may not have considered. Plus, having their input fosters buy-in—because who doesn’t want their voice heard when changes are on the horizon? So let’s embrace workflow mapping as our trusty compass—it will lead us toward smoother transitions and successful outcomes!
How We Do Things Differently
At AGS Enterprises, we want to know what your current processes look like, what work-arounds you’re currently doing in your existing system, and most importantly why you need these processes. We like to start with the end in mind, then figure out the best way to get there. We want to know where your pain points are before we start, so we can address those, rather than just showing off the shiny objects.
If we’re converting your old data, we want to work with you to clean it up first. GIGO (Garbage In, Garbage Out) is real, and we ant to avoid bringing that to your new system.
We also look at your existing forms and see if there is crucial data on them that doesn’t exist in the new system’s forms. I once had a client tell me that he was happy with this existing invoices from the legacy system, and if new system could produce the same invoices, he’d be happy. I took a look, and realized that the substance of the forms was very similar, but the formatting was quite different. I let him know that while I could give him the same forms that he already has, the time and effort to match all the shading, might be better spent on his custom reports. I asked him to look at the canned reports from Spire Systems and then mark those up with any changes he wanted. He agreed with me, it was more efficient to modernize the look of invoices with the Spire format (compared to the legacy one) and to tweak it to add in some custom fields.
Your ERP Is a Tool. It’s Only as Good as Your Process
When it comes to your ERP system, remember this simple truth: it’s a tool, and like any tool, its effectiveness hinges on how you wield it. Think of it as a fancy Swiss Army knife—it can do wonders in the right hands but can easily become an expensive paperweight if you’re not using it properly.
If you want different results from your business operations, you need to rethink your workflows. That means taking a hard look at what you’re currently doing and asking yourself if it’s truly serving your goals or just adding unnecessary complexity. An ERP can unlock immense value for your organization, but only if the foundation is solid.
So before diving headfirst into implementation or upgrades, take a step back and evaluate your processes. Streamlining workflows and ensuring they align with your objectives will set the stage for success. After all, an ERP is only as good as the processes that support it—and trust me, no amount of software wizardry can compensate for outdated or inefficient workflows. Embrace change where needed, and watch as that shiny new system transforms into something truly valuable for your business.
Curious what outdated processes might be costing you? I’d be happy to walk through your current workflows and highlight the gaps.