Enterprise System Spectator blog: ERP and enterprise system vendor evaluation, selection, and implementation.

The Enterprise System Spectator

Saturday, May 22, 2004

Solving the four problems with ERP

I received quite a bit of feedback on my post last week regarding the four problems with ERP. Most of the responses were quite positive, but some did suggest that I missed some problems, such as, "quality of the systems integrator," "turnover of user personnel," and "lack of user ownership." However, my feeling is that these all may be legitimate causes of ERP problems, but they are not separate categories or types of the problems themselves.

There's nothing wrong with looking for causes. Good problem solving techniques from six sigma to the theory of constraints teach us to fix the root causes, not just treat the symptoms. But if we don't understand the nature of the problem itself, how on earth will we ever find the cause? Too many managers immediately want to jump to solutions, without really understanding the nature of the problem.

So, I believe that my list of four types of ERP problems is an exhaustive list of the nature of all ERP problems. You could have dozens of possible causes, but the problems themselves only fall into these four types:
  1. The system itself is bad

  2. The system is good, but it's set up incorrectly

  3. The system is good, but it's not being used

  4. The system is good, but it's being used ineffectively
Now, having said that, one reader did suggest that it would be best not to just categorize the problems but indicate how to solve them. Fair enough. Once you understand the nature of the problem or problems with an ERP system, how should you go about finding solutions? Of course, each company will have different problems, different causes, and different solutions. But there are some common approaches that you can take:

1. If you've got a bad system...
You need to ask, can the system be fixed (e.g. is there a newer version, a vendor patch, or a modification you can make?). Can you work around it (i.e. can you use a procedural method to bypass the system problem)? Can you use some other piece of software instead of the part of the system that is bad? Or, should you replace the system?

But too many executives ask that last question before asking any of the others. Just because a system is bad doesn't mean it needs to be replaced. It depends on how bad it is, and whether the bad parts are fundamental or superficial.

For example, a system might have an unfriendly order entry screen. Perhaps the order entry screen could be modified to remove unneeded data elements, or it could be reconfigured to be more natural to the way your company takes orders. If the rest of the system is good, it would be foolish to replace the entire system just because of an isolated user interface problem.

On the other hand, if a company operates on an actual cost basis, and the system only supports standard costing, it is unlikely that the system could be fixed, or a work around would be viable. Or, if a process manufacturer finds itself stuck with an ERP system that is designed for discrete manufacturing, it might be advisable to bite the bullet and get a system that works for the process industry.

2. If the system is set up incorrectly...
I find it most helpful to find out why the system was set up in the way it is. That will lead you to the possible root cause. Was it just ignorance of the original implementation team? That would point to a need for training on the system. Was it because the company was trying to make the new system look like the old? That would point to a need for business process redesign, or at least to address assumptions about how the business should operate.

Recently I saw a company that was having a hard time keeping up with inventory transaction volumes. We found that the problem was that the system had been set up to serialize each unit of finished production. The company thought that this was necessary to provide full traceability of products for FDA regulatory compliance. Of course, it also exploded the number of transactions that would need to be entered every time a finished product was transacted. When we investigated, we found that the system was fully capable of providing traceability by means of lot or batch numbering, which would greatly improve productivity while maintaining compliance. We then asked why the system had been configured for serial unit control, and we found that it was because that was how the previous system had done it. When management understood the weak basis for the original decision, it was a simple matter for everyone to agree to change it.

3. If the system is not being used...
Again, you have to ask why. Is it because parts of the old system are still in use, in parallel with the new system? A client once brought me in to determine whether their new system was in fact the right system for them. Users had many perceptions about the inadequacy of the new system, most of which I suspected were incorrect. Soon I found the reason. The old system was still running for many functions that the new system could have performed. As long as management was not committed to abandon use of the old system, which users had grown accustomed to, there was no hope that they would learn to use and appreciate the new system.

There can be any number of reasons that a perfectly good system is not being used. It could be a lack of training, or a lack of resources to do the implementation, or resistance to change. I have seen cases where certain users prefer their little Access systems, Excel worksheets, or cumbersome manual systems. Why? Because those little informal systems represent job security. As long as the company depends on those users for their personal knowledge of "how things get done around here," those users are unlikely to embrace an ERP system that promises to formalize and make transparent the business process.

4. If the system is being used ineffectively...
You need to do more analysis. In this category, I like to group problems into four sub-categories.
  • Data problems. For example, inventory inaccuracy can make MRP systems all but useless. There are dozens of other examples of how data problems can undermine ERP systems and force users to work around the system. Many companies I visit have problems with duplicate part numbers, duplicate vendor numbers, and inaccurate costing data. All of these make ERP ineffective.

  • Discipline problems. Invariably, organizations making ineffective use of their ERP systems have poor or nonexistent disciplines in engineering change management, inventory control, and planning. Procedures may not exist, or if they do exist they are not followed. I once saw a company where users were complaining that the planning system didn't work. Later I found out that the VP of Sales routinely called the plant and forced them to change the day's production schedule when an important customer had a rush order. The planning system was being used, yes. But it was being used ineffectively because of poor disciplines in planning and scheduling.

  • Integration problems. Enterprise systems by definition are integrated systems. But the organizations that implement them may not be integrated. Rather, there may be a strong functional orientation that creates isolated "silos" with walls between departments. ERP systems work best when they automate cross-functional processes. But if sales does not talk to production, and production does not talk to engineering, it is unlikely that the ERP system will be used effectively.

  • Measurement problems. Too often companies ask managers to do one thing but measure them on something else. If you ask a factory to ship product according to customer delivery dates, but you measure the plant on "tons produced" each month, it is likely that the plant will maximize tonnage by shipping the largest orders first, instead of the ones with the earliest due dates. Yet, it is easier for management to blame the system instead of their own out-dated measurement systems. There are dozens of similar examples.
Making effective use of ERP generally mean solving problems with business processes and organizational design. This can take you far outside of the IT department and deep into change management in user functions. Although such change can be difficult, the pay off can be huge.

Over the past 15 years, many companies have made enormous investments in enterprise systems. Yet many are unhappy with the results. The temptation is to blame the system and even entertain the thought of replacing it. But, as we have seen, good systems can be saved, as long as management is willing to face the nature of the problems.

Related posts
Four problems with ERP

by Frank Scavo, 5/22/2004 07:57:00 AM | permalink | e-mail this!

 Reader Comments:

Post a Comment

Links to this post:


Powered by Blogger

(c) 2002-2016, Frank Scavo.

Independent analysis of issues and trends in enterprise applications software and the strengths, weaknesses, advantages, and disadvantages of the vendors that provide them.

About the Enterprise System Spectator.

Frank Scavo Send tips, rumors, gossip, and feedback to Frank Scavo, at .

I'm interested in hearing about best practices, lessons learned, horror stories, and case studies of success or failure.

Selecting a new enterprise system can be a difficult decision. My consulting firm, Strativa, offers assistance that is independent and unbiased. For information on how we can help your organization make and carry out these decisions, write to me.

My IT research firm, Computer Economics provides metrics for IT management, such as IT spending and staffing benchmarks, ROI/TCO studies, outsourcing statistics, and more.

Go to latest postings

Search the Spectator!
Join over 1,700 subscribers on the Spectator email list!
Max. 1-2 times/month.
Easy one-click to unsubscribe anytime.

Follow me on Twitter
My RSS feed RSS News Feed

Computer Economics
ERP Support Staffing Ratios
Outsourcing Statistics
IT Spending and Staffing Benchmarks
IT Staffing Ratios
IT Management Best Practices
Worldwide Technology Trends
IT Salary Report

Get these headlines on your site, free!


2014 Best Independent ERP Blog - Winner

2013 Best ERP Writer - Winner

Alltop. We're kind of a big deal.
Constant Contact 2010 All Star Technobabble Top 100 Analyst Blogs

Key References
Strativa: Business strategy consulting, strategic planning
Strativa: IT strategy consulting
Strativa: Business process improvement, process mapping, consultants
Strativa: IT due diligence
Strativa: ERP software selection consulting and vendor evaluation
Strativa: CRM software selection consulting and vendor evaluation
Strativa: Project management consulting, change management
StreetWolf: Digital creative studio specializing in web, mobile and social applications
Enterprise IT News: diginomica

Spectator Archives
May 2002
June 2002
July 2002
August 2002
September 2002
October 2002
November 2002
December 2002
January 2003
February 2003
March 2003
April 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
July 2008
August 2008
September 2008
October 2008
November 2008
December 2008
January 2009
February 2009
March 2009
April 2009
May 2009
June 2009
July 2009
August 2009
September 2009
October 2009
November 2009
December 2009
January 2010
February 2010
March 2010
April 2010
June 2010
July 2010
August 2010
September 2010
October 2010
November 2010
December 2010
January 2011
February 2011
March 2011
April 2011
May 2011
July 2011
August 2011
September 2011
October 2011
November 2011
December 2011
January 2012
February 2012
March 2012
April 2012
May 2012
June 2012
July 2012
September 2012
October 2012
December 2012
January 2013
February 2013
March 2013
May 2013
June 2013
July 2013
September 2013
October 2013
December 2013
January 2014
February 2014
March 2014
April 2014
May 2014
June 2014
July 2014
August 2014
September 2014
October 2014
November 2014
December 2014
February 2015
March 2015
April 2015
May 2015
June 2015
July 2015
September 2015
October 2015
November 2015
February 2016
May 2016
June 2016
July 2016
August 2016
September 2016
October 2016
Latest postings