ERP consulting experienceIn the first part of this series, we discussed how a collapsed civilization allowed the Egyptian pyramids—complex, incredible structures—to fall into ruin compared to their original glory. Enterprise resource planning (ERP) systems are similarly grand in size within the software world and incredible in terms of functionality (indeed, vitality) to one’s business. The pyramids are our metaphor for “Hey, pay the bucks for a qualified ERP consulting team to help you maintain your structure,” a point made by one IT insider earlier on www.itworld.com. Today, we’re talking about why you should pay, in particular, for experience.
ERP CONSULTING: BEEN THERE, DONE THAT
Experience, of course, gets touted so much that we’ve all become deaf to the cheers, but there are reasons to start listening—and thinking. First, at least some experience in the field is necessary to avoid repeating problems. Failed solutions to similar past challenges are the licks earned by those who are more than a few months out of college. Each attempt to solve an IT problem is money out of your pocket, and you’re already paying heftily for this pyramid of code and databases. Let experience save you money in the long run even if it costs you upfront for a veteran team.
Second, those same lessons against repeating problems seen by our veteran ERP consultant has earned him or her an arsenal of possible solutions that can be brought to bear for your benefit. Some college grad just hasn’t had the chance to confront—and learn from—a wide array of problems to gain a wide array of solutions. The more experienced consultant is going to reach immediately into his or her mental toolbox and try a past successful tactic. And even if that tactic fails, the veteran’s next solution will be attempted more quickly than with a newcomer’s empty playbook.
Third, and most importantly, a seasoned player knows the most valuable non-technical fact about professional life: relationships matter. Instilling trust, putting oneself at the service of another, and conveying commitment earn you and your team another contract, another job, and—when in the worst-case scenario—another chance. Be willing to pay for people who know the value of people and getting the job done.
The pyramids were not built by one person alone and neither is a great company or a great ERP implementation, upgrade, or IT solution. And while the pyramids probably involved more whippings than we’re comfortable with, they do remind us that good ERP consulting teams make for great accomplishments. If you’re not willing to pay for that great team, then the pyramids have another lesson for your business: they were built as tombs.