We’ve written many series on best practice tech identification, tech selection, and tech implementation in the hopes of inverting the odds from an 80%+ chance of failure to an 80%+ chance of success, but given that failures are literally still happening on a daily basis, it seems that most people can’t be bothered to read best practice advice so today we’re going to flip the script and tell you all the reasons you’re going to fail and then you hope you go back and read the best practice advice we’ve freely given you (in series such as Successful Vendor Selection – The Series).

1. You Don’t Understand Your True Needs

You’ve never done a full end-to-end process analysis on your organization, you don’t understand how inefficient your processes are, what processes you actually need, why you need them, and how much better you could be doing. You just know that the KPI metrics you are tracking are not on par with industry averages based on what your overpriced consultants are telling you, that your balance sheet isn’t as good as best in class, and that you need to do something … and that something is get a shiny new tech toy that the overpriced consultants will help you select by telling you who to invite to your RFP. (And you should know all the problems with this — they’ll only recommend the partners they have sycophant partnerships with, get referral and implementation fees from, and who will ensure that they remain your overpriced consultancy of choice.)

2. You Don’t Understand What You Already Have

Once you understand what the correct processes are, why, and where the automation points are, you need to revisit the systems you have to see where they can solve the problems. Chances are you have a number of suites, supply chain platforms, and ERPs with easy to implement plug-in modules that solve a lot of the problems you have without buying any new systems. And even if new systems might do it better, chances are the improvement won’t be worth the extra money, downtime, and change management — which will all cost you dearly. The reality is that if you can get an 80% solution today, with tools your people are already using, that’s much better than a potential 95% years in the future.

3. You Don’t Understand What Your Capabilities Actually Are

By this we don’t mean your process capabilities or technological capabilities, we mean your actual functional capabilities. Your domain knowledge, your ability to execute on that domain knowledge, and your natural efficiency. It’s pointless improving processes to apply more advanced techniques or employing modern technology to speed up processes when you’re not capable of managing those advanced processes or technology. If you employ processes and systems you’re not ready for, they won’t deliver any results while costing you millions of dollars in the system selection and implementation processes.

4. You Don’t Understand How Long It Will Take to Upgrade Your Capabilities

Even if you figure out you need to upgrade your skills and those of your team’s, even if you posses a fair degree of human intelligence, you don’t know how long it will take. It’s not just buying a knowledge dump from a consultancy or giving your team a 5-day crash course, because knowledge that is not applied is not retained. There’s a reason College and University courses give assignments and projects as well as exams — the more you apply, the more you retain. If the imparted knowledge is not applied, it will not be retained. Until your team can start applying, repetitively, the new knowledge in improved processes, they won’t retain it and they won’t advance. The best training will be a day or two a month over months, not a week. And that’s for stage 1. It will take years to get your team from average to mastery. We’ve known for decades that major transformation projects take 5 to 10 years, and that the average journey to best in class for the committed is 8 years. Technology doesn’t change that. The longer you choose to ignore this fact, the longer you will fail.

To be continued in Part 2.