The New ERP - Part 2

So, what's wrong with traditional approaches to ERP? Why do so many ERP implementations lead to disappointing results? Why do so many companies spend so much money on new technologies and then end up reaping so little return on their investment?

Failure No. 1: Not achieving the planned return on investment (ROI)
It remains today a regrettable fact that many small to mid-sized companies considering new technologies have only the vaguest of notions about the ROI that their new investment should deliver. This is not to say that executives and managers haven't thought out ROI, or even that they may not have already "pinned a number" on the ROI that they'd like to see from the expenditure of their time, energy and money.

What they do not know -- far too frequently -- is precisely how the new technology will deliver results. They have not tied the expected results to specific improvements in Throughput, specific reductions in Investment, or specific savings in Operating Expenses. Rather, there appears to be a general consensus among executives and managers -- despite considerable evidence to the contrary -- that investments in information technologies (IT) sort of auto-magically deliver a return on investment (ROI). That, somehow, IT and automation investments bear an inherent capacity to make the company better and more profitable.

Over the more than 25 years that I have been working with IT from both sides of the desk -- as an executive and as a consultant -- there have been fewer than a handful of companies with which I have worked that actually calculated an ROI for their investment in technology. Fewer still had any measurable objectives for specific IT investments beyond some number clearly picked from the air like "increase revenues by 5%" or "cut manufacturing costs by 7%." Almost none of these firms could tie specific technology functional deployments to the expected ROI.

Given these facts, it is no wonder that traditional ERP (Everything Replacement Project) fails to deliver ROI. The executives and managers deploying the new ERP have not based their ROI expectations on much more than "gut feelings" and some vague sense that having more data will make them better managers.

Failure No. 2: "Go-live" delayed inordinately
Substantial delays to "go-live" in Everything Replacement Projects (traditional ERP) are generally attributable to one or more of the following factors:

• Poor decisions related to customizations or modifications -- when they are selected; how the program code is designed, developed and managed; and the methods chosen for testing and deployment
  
  
• Executive management's improper view of the goals and objectives of a valid ERP project -- thus leading to out-of-control scope creep, usually with absolutely no correlation to project ROI
  
  
• The organization being overwhelmed by an Everything Replacement Project -- rather than being focused on leveraging specific technologies for the benefit of the "system" (i.e., the organization) as a whole

[To be continued]

Contact me!

...

Extending the Power of Your Information Technologies

In today’s exceedingly challenging business environment, it is becoming increasingly important for executive management to establish corporate strategies that include extending the reach and power of the organization's information technologies beyond the four walls of the firm. If your company is not building "communities" of customers or con-necting with your vendors and customers in real time up and down your supply chain, then it is likely that you are falling behind your competition.

No Technology for Technology's Sake

I am not advocating new "gee-whiz" connections beyond your enterprise just so the CEO can brag about them on the golf course or in the steam room at the club. Before embarking on a spending spree to extend your IT systems beyond the walls of your enterprise, it is important that you determine what you want to accomplish by moving forward with such efforts. Generally speaking, the valid reasons for investing in the extended enter-prise may be reduced to three fundamental categories:

1. Increasing throughput,

2. Reducing inventories or the need for new investment, and

3. Slashing or holding the line on operating expenses.


Let's consider some of the thinking that might go into such an analysis.

Increasing Throughput

When considering increasing throughput, your team should ask questions like these: Could a CRM (customer relationship management) system, a corporate blog or forum, or other enterprise extensions improve our ability to connect with our customers? Could such efforts improve our comprehension of our customers' needs enough that fresh new insights would result from understanding them better? Could the new insights lead to improved products, enhanced market segmentation, and the ability to create superior win-win offers?

If the answers to any or all of these questions are affirmative, then the next step would be to quantify the estimated impact and to set specific goals for any investments in new technologies. Each individual part of the IT investment plan should be directly correlated to expected quantifiable results. How many new customers will be added? How many additional sales to existing customers are to be expected? What additional market share are we likely to gain as a result of these efforts and investments?

Reducing Inventories or the Need for New Investment

The questions that should arise regarding inventories or investments should be along these lines: Will improved supply chain visibility with our customers allow us to better manage and reduce the volume of inventory lying between our manufacturing plants and our products' end users? Will linking our inventory systems with those of our suppliers allow us to reduce lead times and, as a result, reduce the amount of inventory we keep on-hand? Will improved end-to-end supply chain linkages reduce losses due to obsolescence and shrinkage?Again, if asking these questions leads to some "yes" answers, then the organization should take steps to quantify the benefits that are likely to accrue to the organization from reduced carrying costs, managing and handling less inventory, and (if true) the reduction in a potential investment in additional warehouse or production space, for example.

Slashing or Holding the Line on Operating Expenses

Generally, this area faces a two-fold battle: First, most organizations today have already done all the cost-cutting that they really can (or should) do. This is no longer the 1980’s – the heyday of cost-cutting as U.S. industry was struggling against the onslaught of Japanese products. Second, when you are talking about implementing new technologies, it is really difficult to get buy-in from your organization if the move is likely to lead to a significant reduction in the workforce.
However, results stemming from efforts to increase throughput (revenues) and reduce inventories are likely to drive growth, on the one hand, and internal improvements, on the other. Normally, then, a case can be made on the basis of these combined factors (i.e., growth and internal improvements) that your organization can support 30%, 60% or even 100% growth in the near future with little or no growth in operating expenses. The net result is often estimated and stated as savings in FTEs (full-time equivalents, i.e., the average cost of a full-time employee). In this way, the effect of “holding the line on operating expenses” may be properly factored in to the benefits accruing from investments in new technologies.

Conclusion

There is no longer a place for business as usual. In today’s highly competitive markets – driven to a significant degree by the international reach of the Internet and other technologies – every business owner, CEO, and CFO should be considering how extending their information technologies beyond the four walls of their enterprise might lead to in-creasing throughput and reducing inventories, while holding the line on operating expenses. However, every investment in technology should be carefully planned, be geared to achieving measurable goals, and fully aligned with the enterprise’s strategic and tactical objectives.

©2008 Richard D. Cushing

Information Is Not Knowledge

"Information is not knowledge. Knowledge comes from theory."
-- W. Edwards Deming

When Sir Isaac Newton was conked on his head by the falling apple (as the story goes), he had information. The information was, "apples fall from trees" or, put more generically, "things fall to the earth."

However, Newton still had no "knowledge."

Newton's comprehension of the facts did not provide "knowledge" that would be useful in any significant way. After all, people had known for centuries that things fall to the earth and, if one didn't want them falling to the earth, one must be certain that the objects are held securely in their present location.

Once, however, Newton began to construct "theory" around the fact that things fell to the earth, valuable "knowledge" began to spring from the "information" at hand.

For example, based on the "theory" that gravity was a force that always acted in precisely the same way, experiments could be set up to measure just how gravity functioned. From these experiments and calculations, we now know that the gravity of the earth accelerates objects at ~ 32.2 feet per second-squared.

This principle applies in business as well.

Having worked in the world of business management and computers since the time of the introduction of the personal computer (PC) in the early 1980s, I have found that many, many business people -- from owners, to CEOs, to CFOs, to middle managers, and on down the line -- confuse "information" with "knowledge". In fact, a very common fallacy is the belief that more "information" will lead to better management which will, in its turn, lead to better results.

Therefore, organization spend a considerable amount of some very limited resources (namely, time, energy, and money) acquiring or creating systems to give them more "information."

When all is said and done, however, these business folks often are not significantly better off than they were before they spent their precious time, energy and money, simply because, like the world before Newton, they have no "theory" by which to interpret the information they have. Without this theoretical "framework" in which to fit their body of information, many of their management actions are not much more than flailing at the wind. Some of their efforts work and some do not, but they generally cannot tell you (specifically or accurately) why one initiative worked and another similar one failed.

There are three required steps to gathering what one needs to take timely and effective action:

1. One must take the data (the raw, undigested facts -- perhaps line upon line of numbers) and convert the data into "information."

2. "Information" is data "digested" and put into a form (i.e., a chart, a graph, summed, analyzed statistically) that allows the user to quickly assess the essential implications of the underlying data.

3. The resulting "information" must be placed into a theoretical context -- a "framework" -- whereby the potential outcomes of any actions that might be indicated by the information may be fully comprehended.

Without these three steps, your organization may drown in data or become infatuated with "information" and, yet, never be able to move effectively when times are the most challenging.

©2008 Richard D. Cushing