365 Quotes for ERP Implementations

Brett's Hobby

Brett with his personal ERP library

I consider myself an ERP/Cloud implementation practitioner on the road to becoming a better ERP advisor and leader.  I have been on this path for 20 years and believe that I have much to share with my peers.  I also believe that I still have much to learn on this journey.  My hope is that you will partner with me in the never-ending quest for ERP implementation success.  During my ongoing research I have collected a database of over 3000 quotes on ERP-related topics (pains, success, best practices, failures, mistakes, implementations, selections).




# Quote Resource Author(s)
1 Often the problem lies not with the ERP concept. But in the demand for quick fixes and rapid cures to underlying structural problems. e-Business Roadmap for Success Dr. Ravi Kalakota & Marcia Robinson
2 Putting yourself on the same side as the customer is one of the best ways to avoid the massive rework caused by the customer deciding that the product you just spent 12 months on is not the right product after all. Rapid Development  Steve McConnell
3 Reliability is results driven.  Repeatability is input driven. Agile Project Management Jim Highsmith
4 One of the most important areas in enhancing the value added to clients is designing the presentation of information so that it can be readily assimilated and internalized as knowledge. Developing Knowledge-Based Client Relationships Ross Dawson
5 All of the work that goes into development is not adding value until the software is in the hands of the customer. Lean Software Development Mary Poppendieck & Tom Poppendieck
6 Iterations systematically reduce the trade space, grow the knowledge of the solution, and increase stakeholder buy-in.  At the same time, each iteration, or spiral, is planned to mitigate specific risks in the project. Evolutionary Process for Integrating COTS-Based Systems (EPIC) Carnegie Mellon – Software Engineering Institute
7 “Good people can make a bad system work; bad people can’t make a good system work”. The Reengineering Handbook Raymond L. Manganelli, Mark M. Klein
8 “The truth is, no organization plans to fail – rather, they fail to plan…” Control Your ERP Destiny Steven Scott Phillips
9 Many ERP implementations proceed without sufficient knowledge of the possibilities or potential in the new systems.  This relegates the design process to a discussion of repeating the current design (the only thing the client knows) or implementing a process that the consultants happen to know (limited to what the consultants have experienced). Maximize Return on Investment Using ERP Applications Worster, Weirick, Andera
10 There are literally thousands of decisions that must be made on these projects.  The project team must be empowered to make most of them.  That is one reason organizations must put their best people on these teams.


E-Business and ERP Murrell G. Shields
11 Achieving early wins and optimizing user buy-in can pave the way for controlling both political and fiscal costs down the road and increase the chances of delivery project on time and on budget. Total Cost of Ownership: A strategic tool for erp planning and implementation Richard West, Stephen L. Daigle – California State University
12 In making design decisions, the entire process should be considered, not just the individual steps, in isolation.  As in many things, the business process is only as good as its weakest subprocess.  Most of the attention should be focused on the process bottlenecks. Managing the Change Process


David K. Carr, Kelvin J. Hard, William J. Trahant. Coopers & Lybrand Center of Excellence for Change Management
13 To integrate business processes, there is a tendency to employ a bottom-up technical integration, stitching together application components that were never intended to work together at the business level. Business Process Management – the third wave Howard Smith and Peter Fingar
14 The “Train the Trainer” Pitfall: It is not realistic to assume someone can be trained several weeks before the go-live and expect him/her to deliver quality training. Control Your ERP Destiny Steven Scott Phillips
15 Requirements creep must first be differentiated from requirements evolution (elaboration). Agile Project Management Jim Highsmith
16 Two overriding criteria that mast be present if the implementation of a COTS solution are to be successful: realistic expectations and organizational flexibility. Successful Packaged Software Implementation Christine B. Tayntor
17 Every organization that implements an ERP system is, in effect, reengineering. Modern ERP Marianne Bradford
18 Remember that if you fail to implement, who cares what the software (ERP) does? Modern ERP Marianna Bradford
19 Not all process-integration problems are technical, and not all about IT.  Integrating computer systems is not the same as integrating the business. Business Process Management – the third wave Howard Smith and Peter Fingar
20 Having an ERP system is not a luxury but a necessity. It is a must for survival in this competitive world. ERP Demystified Alexis Leon
21 A major cause of this difficulty is that organizations building these systems tend either to assume that components can be simply thrown together or they fall back on the traditional engineering skills and processes with which they are familiar-skills and processes that have been shown not to work in the building of a COTS-based (ERP) system. Evolutionary Process for Integrating COTS-Based Systems (EPIC) Carnegie Mellon – Software Engineering Institute
22 The acquisition of the tools, of and by itself, will not make you proficient in their use and thus will not provide a competitive advantage. ERP: Making It Happen Thomas Wallace & Michael Kremzar
23 Inclusion of end users promotes acceptance of the solution and helps break down “us versus them” barriers.  Working together, the two groups will provide a balanced evaluation. Successful Packaged Software Implementation Christine B. Tayntor
24 “Planning can become mechanistic and succumb to a checklist mentality.” Balancing Agility and Discipline Barry Boehm, Richard Turner
25 Good design can’t fix broken business models – Jeffrey Veen Why New Systems Fail Phil Simon
26 When managers of a company select an ERP package to implement, they are “buying into” the ERP vendor’s view of a certain industry’s best practices and relying on the system to support their efforts to embrace these practices. Modern ERP Marianne Bradford
27 The gap between a person’s current knowledge level and the knowledge requirement associated with the change will directly impact the probability of success for those individuals. ADKAR – A Model for Change in Business, Government and Our Community Jeffrey M. Hiatt
28 Prototypes are generally designed to handle only the nominal cases; they aren’t expected to handle the exceptional cases. Rapid Development Steve McConnell
29 The development of knowledge is an iterative process, in which experience and lessons provide the basis for deeper understandings in ongoing feedback loops. Developing Knowledge-Based Client Relationships Ross Dawson
30 Organizations are now in a business environment where their success will depend on their ability to rapidly respond to changing business requirements. E-Business and ERP Murrell G. Shields
31 ERP is commonly misperceived as a computer system.  Not so.  It’s a people system made possible by the computer software and hardware. ERP: Making It Happen Thomas Wallace & Michael Kremzar
32 The starting step for business-driven implementation is the creation of business process maps. Secrets to a Successful COTS Implementation Nick Berg
33 It is better to know all the questions than some of the answers.  – James Thurber Why New Systems Fail Phil Simon
34 Ironically, customizations don’t add value by default.  By default they subtract value, at least in the short run through costs associated with analysis, design, and development. Modern ERP Marianne Bradford
35 In general, the more comprehensive the system, the more complex configuration will be. Successful Packaged Software Implementation Christine B. Tayntor
36 There is often a level of arrogance in ERP consultants who are taken with replacing existing systems, a level of arrogance that is generally counter-productive. Maximize Return on Investment Using ERP Applications Worster, Weirick, Andera
37 Companies should be careful not to automate non-value-added processes in the new system. Optimize Your ERP System: How to Avoid the Implementation Sins


Sage ERP X3 Whitepaper
38 You give me good people and a great process, and we’ll beat any organization with the best technology but a poor process and under motivated people. Information Week – Focus on the Process Doug Patterson, VP and CIO
39 The longer a team, large or small, goes without delivering an integrated product to a review process, the greater the potential for failure. Agile Project Management Jim Highsmith
40 If you’re using a waterfall model, forgetting something can be a costly mistake.  You don’t find out until you get down to a system testing that one of the requirements was missing or wrong. Rapid Development Steve McConnell
41 A time-tested maxim in training is always to build on what you know. Principles of the Business Rule Approach Ronald Ross
42 Standardization is the key antidote to low productivity. Lean Six Sigma for Service Michael L. George
43 Off-the-shelf solutions also do not provide a competitive edge for long – any technology your company can buy today your competitors can buy tomorrow.  Senior executive must consider a new set of questions: What business processes bring us our identity and competitive advantage? e-Business Roadmap for Success Dr. Ravi Kalakota & Marcia Robinson
44 The way to reduce the impact of defects is to find them as soon as they occur. Lean Software Development Mary Poppendieck & Tom Poppendieck
45 Tools like Enterprise Resource Planning, Lean Manufacturing, Total Quality Management, and others are all essential.  Each one alone is insufficient ERP: Making It Happen Thomas Wallace & Michael Kremzar
46 Implementations must shift from “design and build” unique products to “buy and integrate” standard products. Secrets to a Successful COTS Implementation Nick Berg
47 It is recognized that information accuracy is not a system problem, but rather a management problem. Directing the ERP Implementation Michael Pelphrey
48 Do it once, right at the source. Principles of the Business Rule Approach Ronald Ross
49 At the end of the day a computer problem is probably a business problem. e-Business Roadmap for Success Dr. Ravi Kalakota & Marcia Robinson
50 There is an inclination when implementing packaged applications to use new technologies to implement the same old ways of doing things. E-Business and ERP Murrell G. Shields
51 ERP SaaS requires greater discipline and control for success than on-premise implementations. Cloud Can Bring Out the Best of ERP Brett Beaubouef
52 There is no such thing as a stand-alone ERP module.  ERP is designed to work in concert with other modules as part of a business process. ERP Business Solution Manifesto Brett Beaubouef
53 ERP systems will not exhibit their full potential unless they are properly integrated with other enterprise software applications. ERP Demystified Alexis Leon
54 Successful implementations are done internally.  In other words, virtually all of the work involved must be done by the company’s own people.  The responsibility can’t be turned over to outsiders, such as consultants. ERP: Making It Happen Thomas Wallace & Michael Kremzar
55 Chris Koch of CIO.com writes that “Blank sheet reengineering can lead to unrealistic business process designs that can’t be implemented through enterprise software. Why New Systems Fail Phil Simon
56 A common mistake made by many business leaders is to assume that by building awareness of the need for change they have also created desire. ADKAR – A Model for Change in Business, Government and Our Community Jeffrey M. Hiatt
57 Collectively employees do understand the processes, but individually, they do not. Control Your ERP Destiny Steven Scott Phillips
58 Optimizing a business function is futile and non-value-added if it is not part of a revenue/competitive business process. Maximize Return on Investment Using ERP Applications Worster, Weirick, Andera
59 Discipline creates well-organized memories, history, and experience. Balancing Agility and Discipline Barry Boehm, Richard Turner
60 Unsuccessful companies start their ERP implementation effort with automation, bypassing the critical steps of understanding and simplifying their processes.  These companies believe that automation alone will improve performance and lead to productivity gains.  Automating complex or nonvalue-added processes, however, will not increase productivity or provide measurable improvements in performance. e-Business Roadmap for Success Dr. Ravi Kalakota & Marcia Robinson
61 Teams proceed in a linear fashion with little reliable feedback – they have good ideas, but they don’t test them in the cauldron of reality.  Documents don’t work. Products do.  Effective simulations or models of the actual product. Agile Project Management Jim Highsmith
62 The Standish Group found that the number one reason that projects succeed is user involvement.  Easy access to end-users is one of the three critical success factors in rapid-development projects.  Good relationships with customers improve actual development speed. Good relations with customers improve perceived development speed. Rapid Development Steve McConnell
63 The four key characteristics or enablers of knowledge transfer in communication are: (1) Interactivity, (2) Bandwidth, (3) Structure, (4) Reusability Developing Knowledge-Based Client Relationships Ross Dawson
64 The underlying philosophy is that in smaller, less rigid structures, employees are closer to the customers and can respond faster. Managing the Change Process David K. Carr, Kelvin J. Hard, William J. Trahant. Coopers & Lybrand Center of Excellence for Change Management
65 Business rule solution:  Real-time delivery of business logic to knowledge workers as errors actually occur creates a seamless, never-ending, self-training environment. Principles of the Business Rule Approach Ronald Ross
66 (ERP) Service organizations are essentially big “people machines”, where having a high level of turnover is just as deadly as if a manufacturer was constantly asked to change machine parts. Lean Six Sigma for Service Michael L. George
67 The goal of an integrated enterprise is to reduce information float, that is, the time between when data is captured in one place in the system and when it becomes available and usable. e-Business Roadmap for Success Dr. Ravi Kalakota & Marcia Robinson
68 The advantage of the incremental approach is that the company can get feedback on the implementation and how it is received and possibly fin tune the implementation strategy. ERP Demystified Alexis Leon
69 ERP is a philosophy for operating a business model.  If your company does not want to adapt to this philosophy, save yourself the headache and don’t pursue ERP. Directing the ERP Implementation Michael Pelphrey
70 There is no such thing as an easy implementation of an ERP project. Enterprise Resource Planning (ERP) The Great Gamble Ray Atkinson
71 Selecting the consultants (and an implementation methodology) is as important as selecting the (ERP) package. ERP Demystified Alexis Leon
72 The big bang approach promised to reduce the integration cost in conditions of thorough and careful execution.  This method dominated early ERP implementations and it partially contributed to the higher rate of failure in its implementation. ERP Demystified Alexis Leon
73 There is no such thing as a competitive ERP implementation methodology.  Only thing competitive for implementation partners are its people. Self-Quote Brett Beaubouef
74 It may take months to adjust learning curves with an organization.  A major challenge in ERP implementation is the selection of the adequate training for the end-user and education. ERP Implementation Challenges & Critical Organization Success Factors Rajeshwar Vayyavur
75 Implementing the ERP system and realizing the promised benefits are two different ball games. Implementation can be a success, but if the operational phase is not planned and organized properly with the support of all the people involved, then the promised benefits will not materialize. ERP Demystified Alexis Leon
76 In the absence of knowledge and ability you can expect lower utilization throughout the organization, incorrect usage of new processes and tools, a negative impact on customers and sustained reduction productivity. ADKAR – A Model for Change in Business, Government and Our Community Jeffrey M. Hiatt
77 If the project should start to derail, consultants are the easiest to blame. Why New Systems Fail Phil Simon
78 The organizational culture and the nature of projects will be different from company to company.  Thus, two ERP implementations can never be identical. ERP Demystified Alexis Leon
79 Claims of ‘proven paths’, ‘best practices’, and simplistic implementations methodologies, that fail litter the ERP landscape as each software company seeks to gain some form of advantage over its rivals. Enterprise Resource Planning (ERP) The Great Gamble Ray Atkinson
80 Implementation audits are necessary to keep the project on track.  Audits should be conducted to compare project results, business objectives, systems objectives, and project objectives. Directing the ERP Implementation Michael Pelphrey
81 Information and intelligence are half of the equation.  The other half is flexible and adaptive production processes that can swiftly respond to threats and/or opportunities. ERP Lessons Learned – Structured Process Wayne L. Staley
82 The rule is efficiency never trumps effectiveness. ERP Lessons Learned – Structured Process Wayne L. Staley
83 “Paralysis through analysis” in a futile attempt to develop the perfect solution. Control Your ERP Destiny Steven Scott Phillips
84 Companies need a systematic method of analyzing the impact of business processes and a more reliable way of introducing new process designs. Business Process Management – the third wave Howard Smith and Peter Fingar
85 When failure is not blamed but considered part of the learning process, people feel secure in taking bold steps outside their narrow territory, and that is when things start happening. Managing the Change Process David K. Carr, Kelvin J. Hard, William J. Trahant. Coopers & Lybrand Center of Excellence for Change Management
86 Where knowledge transfer is a key objective, project handover should be formalized, rather than just letting the engagement end. Developing Knowledge-Based Client Relationships Ross Dawson
87 Some people mistakenly assume that agility connotes a lack of structure, but the absence of structure, or stability, generated chaos.  Conversely, too much structure generates rigidity. Agile Project Management Jim Highsmith
88 In order to manage these changes, it is important for the implementation team to document changes that must be made to individual jobs and execute plans to help people transition to their new jobs. E-Business and ERP Murrell G. Shields
89 ERP SaaS 101: Great customer service can overcome a multitude of software sins. Self-Quote Brett Beaubouef
90 ERP 101:  How you gather business requirements sends a message. Self-Quote Brett Beaubouef
91 On time, in scope and on budget means nothing if an ERP customer is not willing to provide a reference. Self-Quote Brett Beaubouef
92 Extracting and cleansing the data from the existing system can be the single largest task in the project ERP Demystified Alexis Leon
93 The goal should not be to fail fast but to learn fast. R “Ray” Wang: An interview by Bob Morris Ray Wang
94 “Certified consultants are able to translate business requirements into software configurations far more effectively than non-certified consultants. They can also provide a much more realistic forecast of what your CRM will entail in terms of time and resource requirements. “  

Top 50 CRM Quotes


Jim McPeak, vice president, Envoy Corporation

95 content without the context of business process is meaningless Twitter Quote Dennis Howlett
96 End results modeling and pilot room testing with the company can eliminate surprises and uncover almost all “invisible” ghosts in the closet ERP Readiness Checklist Gerry Poe
97 ERP is a semi-finished package.  The user organization must configure to meet their needs. Enterprise Resource Planning Jyotindra Zaveri
98 A good ERP is more than just good software. It involves an institutional commitment to connecting people, processes, and resources Twitter James Young
99 The data migration phase of a project can consume up to 30% of the total project resources.  The most common flaw in data migration planning is that too few resources are invested in it Top 10 Reasons Why Systems Projects Fail Dr. Paul Dorsey
100 Implementing ERP well is a difficult, but not impossible task. It requires not only that you work hard, but that you work hard on the right things. Website ERP Focus
101 Before buying into a new cloud-based web development methodology, understand that the new development environment will not help with long-established problems characterized by poor project management. Transitioning the Enterprise to the Cloud Ed Mahon, CIO at Kent State University
102 The cost of fixing a service defect may be as small as a keystroke, but the opportunity cost downstream may be enormous, such as losing a customer to a competitor. Lean Six Sigma for Service Michael L. George
103 As an adult, I often see software projects that fail merely because the developers and managers who work on them don’t follow the instructions. Rapid Development Steve McConnell
104 But technology is not reengineering.  Reengineering changes the business processes – the way the work is done. The Reengineering Handbook Raymond L. Manganelli, Mark M. Klein
105 During a period of organizational change, a company’s reward structure should be linked to achievement of the goals mandated by the change.  The policies and procedures for rewards and censures must be made known to all employees at all levels, and must be implemented fairly and impartially. Managing the Change Process David K. Carr, Kelvin J. Hard, William J. Trahant. Coopers & Lybrand Center of Excellence for Change Management
106 Process is not a substitute for skill. Agile Project Management Jim Highsmith
107 Many of the major decisions and actions that ultimately determine whether a project is a success or a failure occur very early in the life of the project. E-Business and ERP Murrell G. Shields
108 What businesses need is not a one-time fix for individual processes but an environment that combines business and technical systems to produce processes that flex and recombine as required by changes in the market. Business Process Management – the third wave Howard Smith and Peter Fingar
109 The cost of complexity isn’t offset by what you can charge.  Complexity creates opportunities for you to fail your customer. Wall Street Journal, 9-17-2002) Gerand Arpey – American Airlines President
110 Projects that skimp on upstream activities typically have to do the same work downstream at anywhere from 10 to 100 times the cost of doing it properly in the first place (Fagan 1976; Boehm and Papaccio 1988). Rapid Development Steve McConnell
111 Decreasing variability early in the process has larger impact than decreasing variability late in the process. Lean Software Development Mary Poppendieck & Tom Poppendieck
112 ERP packaged solutions, however, come at a price.  These apps require organizations to reengineer established business practices to accommodate application constraints. e-Business Roadmap for Success Dr. Ravi Kalakota & Marcia Robinson
113 Applying knowledge is the final step that makes the knowledge valuable. Developing Knowledge-Based Client Relationships Ross Dawson
114 Agile methods universally need close relationships with the customer and users of the systems under development. Balancing Agility and Discipline Barry Boehm, Richard Turner
115 Process thinking is a discipline. Maximize Return on Investment Using ERP Applications Worster, Weirick, Andera
116 The less you know the more money they (consultants) make. Control Your ERP Destiny Steven Scott Phillips
117 Are the business processes that will be automated clearly understood and documented?  An adage says, “If you don’t know where you’re going, any road will take you there.” The software equivalent is less positive “If you don’t know what it is you’re automating, no system will help”. Successful Packaged Software Implementation Christine B. Tayntor
118 Deliver sooner rather than later.  It is rare to get 100% support for any project; “fence sitters” will wait to see how things turn out before giving their support. Modern ERP Marianne Bradford
119 the success or failure of a new system hinges directly on the acceptance of that system by the organization’s end users Why New Systems Fail Phil Simon
120 Although consultants may participate in testing to some extent, employees should drive the majority of testing.  Doing so maximizes knowledge transfer and readies them for real life under the new system. Why New Systems Fail Phil Simon
121 Training and education of users, customers and suppliers is an important part of adoption and satisfaction of the ERP system. Critical Success Factors in ERP Implementation Tammy Bahmanziari
122 Optimizing individual function areas generally does not result in optimization of the whole process because, within departments, only individual activities are goal oriented. Business Process Oriented Implementation of Standard Software Mathias Kirchmer
123 If you do not define the lowest level of detail required for reporting, you will not be able to design the transaction input to achieve that result. ERP Implementation Best Practices Success And Cautionary Tales Valerie Campbell CPA CGMA
124 The first comprehensive picture of whether the accounting numbers balance and make sense will arise during the month end process. ERP – The Implementation Cycle Stephen Harwood
125 Overspend on consultancy is often compensated for by a cut-back in training.  This is not helped by the fact that training costs tend to be under-estimated in the first place. ERP – The Implementation Cycle Stephen Harwood
126 Users only care about their experiences. Transitioning the Enterprise to the Cloud Ed Mahon, CIO at Kent State University
127 Data migration/conversion is always customer specific. Self-Quote Brett Beaubouef
128 When implementing a new ERP system you need to start data migration from the existing legacy business systems as soon as possible. ERP Demystified Alexis Leon
129 The ability to trace requirements flow from their source (originator), through the various project phases (design, prototyping, customizations, testing, piloting, and delivery) is a requirements generation best practice. Directing the ERP Implementation Michael Pelphrey
130 Bait and switch.  This is the practice of displaying certain consultants, during the sales process, to show the sales company understands business and the ERP implementation process to ensure a successful outcome. Enterprise Resource Planning (ERP) The Great Gamble Ray Atkinson
131 If you want to achieve “exceptional” results, the ERP implementation project must be a top priority for senior management. Directing the ERP Implementation Michael Pelphrey
132 The cost of control obviously should not exceed the cost of inaccuracies. ERP: Making It Happen Thomas Wallace & Michael Kremzar
133 Utilize a “test first” approach.  Test scripts are written in advance of any configuration or development. Secrets to a Successful COTS Implementation Nick Berg
134 Visibility promotes accountability. Self-Quote Brett Beaubouef
135 Success is not to be found in excellent project management alone. ADKAR – A Model for Change in Business, Government and Our Community Jeffrey M. Hiatt
136 When data lacks high quality, it is useless regardless of the supporting IT infrastructure in place.  There is where data governance comes in.  Data governance involves the creation and management of the organization structures, policies and processes needed to define, control, and ensure the quality of enterprise data. Modern ERP Marianne Bradford
137 The rumor mill and grapevine are active in most companies, and it is in the project team’s best interests to preempt them by providing clear, consistent, targeted, and ongoing communications. Successful Packaged Software Implementation Christine B. Tayntor
138 In order to increase the chances that the conversion will go smoothly, do a dry run test of the conversion plan prior to the real go-live. Control Your ERP Destiny Steven Scott Phillips
139 A common mistake is to design and configure the system for only the first site and worry about the others later. Control Your ERP Destiny Steven Scott Phillips
140 The proposed process designs should always be designed within the logic of the ERP systems. Maximize Return on Investment Using ERP Applications Worster, Weirick, Andera


141 It’s impossible to meet expectations when a turn-key, customized solution is setting the expectation. Self-Quote Brett Beaubouef
142 Customers tend to interpret requirements broadly, and developers tend to interpret them narrowly. Rapid Development Steve McConnell
143 The training in a rapid implementation should be hands-on. E-Business and ERP Murrell G. Shields
144 Benchmarking has its limits. The Reengineering Handbook Raymond L. Manganelli, Mark M. Klein
145 Information technology provides two distinct capabilities for improving the performance of work.  The first, and more familiar, capability is automation: The second capability is information. The Reengineering Handbook Raymond L. Manganelli, Mark M. Klein
146 Interaction drives innovation.  Innovation emerges from the interaction of diverse individuals. Agile Project Management Jim Highsmith
147 In an organization undergoing change, building a resilient work force by widely disseminating the change vision and strategy and by minimizing disruption is essential. Managing the Change Process David K. Carr, Kelvin J. Hard, William J. Trahant. Coopers & Lybrand Center of Excellence for Change Management
148 Business process redesign must incorporate management process redesign. Personal Quote Brett Beaubouef
149 The success of the Go Live day is measured by the lack of problems. ERP – The Implementation Cycle Stephen Harwood
150 One guiding tenet is every present: any change we administer should add more value, cost less, or deliver services more rapidly. Transitioning the Enterprise to the Cloud Ed Mahon, CIO at Kent State University
151 No company, no manager is sufficiently brilliant to think about all of the complexities and complications inherent in a cross-functional ERP project. Mission Critical – Realizing the Promise of Enterprise Systems Thomas Davenport
152 With ERP you always implement across a business process, regardless of the product scope.  #stopsilothinking. Personal Quote Brett Beaubouef
153 If you think education is expensive, try ignorance. Personal Quote Derek Bok
154 One dollar of prevention spent on fail proofing strategies can be worth several thousand dollars of expensive fixes and rehabilitation. ERP A-Z: Implementer’s Guide for Success Travis Anderegg
155 You can succeed with any ERP methodology.  You can fail with any ERP methodology.  The key is correctly applying the methodology. Personal Quote Brett Beaubouef
156 An information system only has value when people use it correctly. ERP – The Implementation Cycle Stephen Harwood
157 The best people for the project are likely to be those who have the least free time, since they are already in key positions. ERP – The Implementation Cycle Stephen Harwood
158 Train and then re-train: The best approach to training is to do it several times. Once is not enough. Three recommend points of training are follows are: On Design, Before test, Post go-live. Top 5 Recommendations to Ensure Your ERP Implementation is Successful Sandeep Walia
159 Digital Darwinism is unkind to those who wait. R “Ray” Wang: An interview by Bob Morris Bob Morris
160 A company may employ the most sophisticated software in the world, but unless information is managed, timely, accurate, and complete, the system serves little purpose. ERP Lessons Learned – Structured Process Wayne L. Staley
161 Have successful project managers who are capable of anticipating what can go wrong. ERP Demystified Alexis Leon
162 ERP is first an attitude; second, a process, and only third, a set of tools. ERP Demystified Alexis Leon
163 Using an ERP system simply to run things in the same way as before implementation is a guarantee of disappointment. Enterprise Resource Planning (ERP) The Great Gamble Ray Atkinson
164 Deferring decision(s) will cause significant risks to the (ERP) project success. Directing the ERP Implementation Michael Pelphrey
165 There are limits to how much change an organization and its end users can stomach at once. Why New Systems Fail Phil Simon
166 How can one manage change if one does not understand exactly what is changing. ADKAR – A Model for Change in Business, Government and Our Community Jeffrey M. Hiatt
167 One means of ensuring that a fresh approach will be taken to the problem is to eliminate all previously existing reports. Mission Critical – Realizing the Promise of Enterprise Systems Thomas Davenport
168 If an organization does not have process owners then they are not process oriented. Personal Quote Brett Beaubouef
169 Plans are worthless, but planning is everything Personal Quote General Dwight Eisenhower
170 The more the consultants know about the company the better they will be equipped to provide good advice. ERP A-Z: Implementer’s Guide for Success Travis Anderegg
171 Resistance, in many cases, is simply a sign of a lack of communication. ERP A-Z: Implementer’s Guide for Success Travis Anderegg
172 Whilst technology is a great enabler, it is not a panacea in itself. ERP – The Implementation Cycle Stephen Harwood
173 Slow processes are prone to poor quality. Lean Six Sigma for Service Michael L. George
174 Rapid implementation cannot be done with a massive project team. E-Business and ERP Murrell G. Shields
175 Rapid Implementations: The data cleanup must start early in the project for the organization to be prepared for the data conversion. E-Business and ERP Murrell G. Shields
176 In order to do rapid implementations, trade-offs must be made. E-Business and ERP Murrell G. Shields
177 The longer the timeframe and the further apart the milestones in a project, the harder it is to create a sense of urgency. E-Business and ERP Murrell G. Shields
178 Customers define value. Agile Project Management Jim Highsmith
179 Adaptive approaches are good when your requirements are uncertain or volatile. Agile Project Management Agile Software Development
180 Prototypes also provide early feedback on design problems and customer preferences. Lean Software Development Mary Poppendieck & Tom Poppendieck
181 Iterations provide a dramatic increase in feedback over sequential software development, thus providing much broader communication between customers/users and developers. Lean Software Development Mary Poppendieck & Tom Poppendieck
182 There must be awareness throughout the organization of the importance of scope management. E-Business and ERP Murrell G. Shields
183 Ambition can be as powerful a motivator as pain and fear. The Reengineering Handbook Raymond L. Manganelli, Mark M. Klein
184 An individual’s gain or loss of power within an organization also has a tremendous effect on the change management process. Managing the Change Process David K. Carr, Kelvin J. Hard, William J. Trahant. Coopers & Lybrand Center of Excellence for Change Management
185 Rules build on facts, and facts build on concepts as expressed by terms. Principles of the Business Rule Approach Ronald Ross
186 The user community is frequently the largest variable in the ERP implementation. ERP Information at the Speed of Reality Wayne L Staley
187 The more comprehensive the package, the greater the expense and complexity. ERP Information at the Speed of Reality Wayne L Staley
188 Integrating separate ERP systems is hard.  Each ERP system wants to be the master. Personal Quote Brett Beaubouef
189 Competitive advantage comes not from systems, but from doing something better than competitors. Mission Critical – Realizing the Promise of Enterprise Systems Thomas Davenport
190 Business factors create the need for technical functionality; technical limitations create business risk. Mission Critical – Realizing the Promise of Enterprise Systems Thomas Davenport
191 There is a misconception that ERP is only for big companies. ERP Demystified Alexis Leon
192 Without change, performance would never improve. Modern ERP Marianne Bradford
193 There is a misguided belief that experienced consultants face no learning curves with the software. Control Your ERP Destiny Steven Scott Phillips
194 Not all process-integration problems are technical, and not all about IT.  Integrating computer systems is not the same as integrating the business. Business Process Management – the Third wave Howard Smith and Peter Fingar
195 Software programmers often think they have better solutions than users. ERP Information at the Speed of Reality Wayne L Staley
196 Due diligence may feel like a waste of time and money, but weighed against the high cost of failure, it is imperative. ERP Information at the Speed of Reality Wayne L Staley
197 Nothing is more irritating than being forced to serve the system instead of the system serving the customer. ERP Information at the Speed of Reality Wayne L Staley
198 Be open to new ways to accomplish the same goal. The Executive Guide to Implementing Accounting Software Ken E. Sebahar
199 Every single software implementation project is unique. The Executive Guide to Implementing Accounting Software Ken E. Sebahar
200 Cloud ERP: Good, fast, and cheap.  Don’t expect all three! Personal Quote Brett Beaubouef


The Next Evolution of ERP: Adaptive ERP

With the initial release of ERP, one of the key “game changers” was the ability of business users to access data and generates reports without direct IT involvement. This empowerment of the business user had a significant impact on business agility. Today, we continue to see ERP vendors focus on providing business-friendly tools for reporting and analysis.  Yet, I can see a new evolution brewing in the ERP industry what I like to call “Adaptive ERP” where business users can perform on-demand actions to meet business changes real-time.  In the next sections we discuss the key capabilities of Adaptive ERP and a practical assessment of where the ERP industry is today.

What is Adaptive ERP?

Adaptive ERP would enable business users to configure, simulate, test, and implement business technology changes with limited traditional IT services (ex. software development).  Predictive analysis will become a reality.  Logical thinking and search methods will be more valuable than technical syntax. Information will become context and even transactional specific.   Following is an illustration of the major domains that Adaptive ERP should address:

Adaptive ERP

Conceptual Model of Adaptive ERP

Domain:  Logical Development

Too often a change in the business model requires an IT development effort.  Any competent IT development will require the following activities:

  • Business requirements gathering
  • Technical design
  • Technical construction
  • Unit, System testing

In general, the greater the number of individuals involved in a project the greater the coordination/communication effort resulting in a greater time commitment.  Enabling business to become agile will require an evolutionary change in how ERP supports business activities.  However, simply removing people out of the equation is not the answer.  What is required is providing business owners the tools and experience required to become more self-sufficient.

Logical Development

Logical Development for ERP

Following is a brief list of the capabilities required to enable business users to perform logical development

  • Business models must be defined as metadata within the ERP software.
  • Business rules are separate from technical components and are exposed directly to business users.
  • Business scenarios are defined separate from the respective business models. Business exceptions are variations to a specific business scenario.
  • Business users should have the ability to run simulations in production (i.e. parallel testing)
  • ERP must provide automated testing support
    • Automated unit and system testing (self-learning via business model metadata).
    • Automated business process test scripting.
    • Test scripts are a results-oriented view of business requirements.
    • Automated impact analysis with logical development change.
  • Business users should be trained in logical and structured thinking.  There has to be a prescribed process to effectively conduct knowledge transfer with the ERP software.  Business users should be able to directly educate (i.e. configure) the ERP software on how they run their business.

Remember that a key value proposition for ERP is to reduce software development.  This is not an argument to eliminate IT but rather to refocus IT from tactical support to strategic activities.  IT will play a very important role in enabling business users in logical and structured thinking.

Domain: Predictive Analysis

Today, there is interest in Big Data and Enterprise 2.0 technologies but they are not the final destination.

Predictive Analysis

Predictive Analysis

At the end of the day, business decisions have an impact on business results. Enterprise 2.0 and Big Data are supportive technologies.  Enterprise 2.0 focuses on the utilization of Web 2.0 standards in developing collaborative technologies like blogs, RSS, social bookmarking, social networking and wikis.  Enterprise 2.0 emphasizes employee, partner and consumer collaboration for creating knowledge.  Big Data is the next evolution in Knowledge Management where it is now viable to manage and utilize both structured and unstructured data.   However, the key challenge remains – how to effectively leverage all the information we are collecting.  We need to flip the following time paradigm:

Data Analysis Cycle

Business Information Cycle

Changing this paradigm will require inference engines that streamline analysis generation and enable predictive analysis.  Following is a brief list of capabilities that will support predictive analysis:

  • Case-Based Inference will provide recommendations based upon data and transactional patterns.
  • Rules-Based Inference will provide tactical, operational decision support based upon standard business principles.
  • Big Data will facilitate the assimilation of structured and unstructured data to identify patterns and provide operational context.
  • Collaborative ERP 2.0 will support collaborative discussions and provide transactional context for decision support.

Advancements like this in analytics will enable business users to focus on the value-add activities of reviewing analysis and drawing conclusions for effective business decisions. 

Domain: Open

Whether or not you are sold on open source ERP,  you have to admire the new paradigm and simplicity that open source ERP promotes.  As we continue to see the consumerization of legacy ERP technologies, the market will continue to drive individual user enablement and vendor independence.  Following is a brief list of capabilities that will promote a more open ERP industry

  • BYOD (Bring Your Own Device)will enableemployees are able to bring their own computing devices – such as smartphones, laptops and PDAs – to the workplace for use and connectivity on the corporate network.
  • BPMN compliance will ensure that ERP business process definitions will agree with business process definition standards outlined in the Business Process Modeling Notation (BPMN) model.  This model is governed by the Object Management Group (OMG).  In my humble opinion, the OMG is in the best position to define a global standard for business process models.  This advancement will be a key enabler to the holy grail of true enterprise system interoperability.  This is no small task and will require significant market demand to promote this standardization initiative.
  • Collaborative Shared Development is a key benefit of an open community.  Sometimes it takes a village of developers to support an ERP solution.  Today, I can go to the Apple App Store to purchase an app for my iPhone.  In the future, we should see an ERP App Store when a customer or an individual business user can download an object (software, report, role-based feature) to customize their ERP experience.
  • Open Partner Network.  The more integrated your ERP is within your business value chain (suppliers, vendors, customers, providers) the more powerful your ERP system can be.  I expect we will see the ERP market put more value in delivered integrations with partner, supplier, and provider networks over software product features.  SOA will be a key enabler for making open partner networks a reality.

Openness is about creating flexibility and the freedom for a customer to respond to the changing business environment in the most effective manner.

Domain: Viable Solutions

A profound lesson I learned the hard way is that regardless of how many features and products an ERP vendor can provide (even for free); it will all be all in vain if the software is unmanageable.  It is unacceptable that a customer has to pay triple and even quadruple the original software cost to maintain their ERP investment.  Some may argue that ERP vendors have not acted in the best interest of their customers by building features upon features without providing tools to significantly reduce the Total Cost of Ownership (TCO).

Simplifying Technical Support

Simplifying Technical Support

Following is a brief list of capabilities that will significantly reduce TCO:

  • Automated testing (self-learning tools).
  • Automated master data management (information awareness tools).
  • Eliminate the need for multiple instances.
  • Assimilated, holistic solutions– loosely coupled point systems will not work and result in greater costs and possible failures.
    • Minimize the technical stack.
  • Higher Quality Assurance
    • Upgrades/Software Maintenance releases included the test cases and results performed by the ERP vendor.
  • Implementation Wizards
  • Support for Hybrid Deployments
    • Software architecture can support either single or multiple tenants.
    • On-Premise, Hosted, Public Cloud, Private Cloud for either applications and/or data.
      • Example:  Customer decides to store mission-critical data on-premise and internal data on the public cloud.

It should no longer be acceptable that an ERP customer has to totally shoulder additional implementation and upgrade costs.  This is not indicative of a true partnership.

Challenge to ERP Industry for Adaptive ERP

Today, we continue to see a consolidation of the ERP industry.  With these acquisitions some ERP vendors provide some limited capabilities of Adaptive ERP but these capabilities are spread across multiple software products and platforms.  An ERP solution is only as strong as its weakest link (integration).  More technologies loosely coupled together usually mean (a) more IT resources, (b) additional points of failure, and (c) a more complicated experience for business users. We have witnessed where ERP software has become bloated with features upon features without any logical progression.  ERP customers are forced to deal and pay for unused features resulting in more frustration than simplicity.

Many top-tier ERP software solution packages use a systems configuration concept to set up the business environment for some time but please allow me to challenge the industry a little more. I agree that several ERP software packages provides configuration concept yet there is no clear decrease in implementation schedule (ex. SAP) or cost savings associated with this approach because the currently exposed configurations do not change that frequently (ex. Earning Codes, GL Accounts). Objects like business rules, scenarios, and exceptions change more frequently. This is a challenge for some ERP software (ex. PeopleSoft) where many business rules are encapsulated within the technical object. Pre-configurations are only a beginning – it adds value in the short-term but ERP is a long-term proposition. In my humble opinion, the key is to expose the underlying business model to business users for greater real-time interaction.

Also, there are Master Data Management (MDM) solutions available to support a tactical level of data governance by removing duplicates, standardizing data and, incorporating rules to eliminate incorrect data from entering the ERP system.  For Adaptive ERP, MDM must advance in what I call “information awareness”.   Information awareness means two things (1) MDM is able to automatically detect and define new information sources within the enterprise ecosystem via data polling, and (2) MDM is able to determine how data is used.  These capabilities will be key enablers for automated impact analysis.

What we need to have is a mature, open, holistic solution where all the individual software platforms are assimilated into a robust, uniformed solution.  This is not simply building a dashboard that brings together two separate user sessions together or an orchestration level that adds another level of technology abstraction and performance overhead.  A viable solution is a manageable solution.


I’m a firm believer in performing non-competitive business activities as competent and cheap as possible.  In that end I am a firm believer in ERP.  However, the ERP industry has come up short in the areas of total cost of ownership and business adaptability.  Many on both sides of the aisle have wrongly concluded that more software features and increasing the technical stack are the answers for making ERP adaptable.  Putting more power in the hand of business users is the strategic answer for business agility.  People are the most important and adaptive component of a business solution.

Best of Breed vs. Integrated ERP

We have all heard the proverb “A chain is only as strong as its weakest link.”   Applying this concept to business software, we would conclude that a business solution is only as strong as its weakest integration.  Usually overlooked and underestimated, integration is one of the most important factors to consider as part of a best of breed vs. integrated ERP solution.   The benefit of richer functionality is limited by partial integration.   In the next sections, we will discuss all the factors to consider as part of making an informed decision regarding best of breed vs. integrated ERP.

Best of Breed versus Integrated ERP

The typical value proposition for best of breed software is the deeper and industry-specific functionality provided.  This advantage is especially important for generating competitive advantage.   It is vital that an organization’s revenue-generating business processes are competitive.  However, it is not strategic to an organization to be competitive in non revenue-generating business activities.  Consider the following:

Advantages and Disadvantages with Best of Breed vs. Integrated ERP

Advantages and Disadvantages with Best of Breed and Integrated ERP

Allow me to expound on a few key facts expressed above:

  1. Integrating a best of breed application with ERP software will result in additional cost and maintenance (ex. dual upgrade and maintenance cycle).
  2. Developing integration between a best of breed application and ERP software will not be as robust as the delivered ERP integrations between its applications.  Part of result has to do with the total integration cost over the life of ERP and the other area is the simple fact that the underlying data models are different.

The question I challenge my customers with is “Will having a best of breed software versus integrated ERP worth the cost?”  Will the additional investment generate a significant impact to competitive advantage?

Allow me to provide a real life example.  I was working with a large insurance provider with their ERP implementation.  As part of the ERP implementation, the customer was considering a best of breed software package instead of utilizing delivered ERP functionality to support IT project management activities.  Following is the case I presented to advise the customer in making their decision:

Outlining considerations for best of breed and integrated ERP

Building the Case for Best of Breed vs Integrated ERP

Ultimately, the business makes the decision but as business technology advisors (IT, Consultants) it is our responsibility to present all the relevant information in the appropriate content so an informed decision can be made.  There is one area in particular that is generally not fully elaborated – the true cost of integration.

The True Cost of Integration

When we think about integration between two different software packages we usually only focus on transactions.  To continue with the example I provided in the previous section, following is a representation of the required integrations between ERP and the best of breed packaged software.

Integration points for Best of Breed with ERP

Integration points for Best of Breed with ERP

Each packaged software has business rules and control data (ex. Project types) that govern how software functionality supports business activities.  Also, consider that the underlying data models for each packaged software are different.  There must be a process (either manual or automatic) in place to keep the respective business rules and control data in sync.  Business transactions must also be replicated between the ERP and the Best of Breed packaged software.  It is worth considering the amount of data that must be replicated between the two software packages.  I understand that replication sounds much worse than integration; however, when we need to integrate transactions between different data models, replication is typically the approach taken.  Even when an ERP vendor indicates they have delivered integration with a best of breed packaged software we need to ask whether the integration is services-oriented or data-oriented (replicated).

There are also strategic considerations for a customer’s IT organization.  Consider the following sources:

Costs required to integrate a best of breed software with ERP

Total Integration Costs for business software

Making the decision to implement a best of breed approach for supporting business activities will increase the total cost of IT as well as put the underlying technical architecture is not flexible and adaptable to meet emerging requirements.

Does Best of Breed Make Sense?

Let me say this loud and clear “ABSOLUTELY”.  ERP can be a good integrated solution to support revenue-supporting, compliance, and generally accepted best practices.  However, ERP does not support competitive practices (if it did then the business practice would no longer be competitive because it is generally available to everyone).   Generally speaking, a best of breed software vendor may be more open to active collaboration and co-development with customers in developing solutions for emerging requirements – which is the nature of revenue-generating business processes.   Yes, there will be the additional cost and support but the payoff is far more significant in terms of the potential for increased revenue and market share.


Business processes, not individual business functions, generate business results.  Too often, we only focus on business activities and the specific software functionality that supports these activities without holistically addressing the entire business process.  This limited view typically results in a short-sighted decision resulting in a higher Total Cost of Ownership (TCO) and a less flexible software solution.

Best of breed software may be the best decision for supporting revenue-generating business processes.  There are times were integrated ERP is the right choice given the potential return.  What is most important to consider is which choice will enable the customer to be in the best position to take advantage of future opportunities.

Creating a Flexible and Adaptable ERP Solution

Every customer I assisted in their ERP implementation wanted an ERP solution that would be flexible and adaptable.   One of the key challenges and disappointments customers have with ERP are around flexibility and adaptability.  We also need to address the common misinterpretations associated with the concepts of a flexible and adaptable ERP solution.  Referring back to a previous blog we know that ERP is only one component of a business solution.  There are three key areas to address as part of developing a flexible and adaptable business solution.

Know The Limitations

Technically speaking, there are two key methods to enable packaged software like ERP to be flexible and adaptable:

  1. Programming (addresses flexibility or the ability to change)
  2. Configuration (addresses adaptability or the ability to easily change)

Each of these methods has inherent advantages and challenges associated with them.  Configuration has been a key area of focus for ERP vendors to create greater software adaptability.  Configurations enable less technical, business-oriented users to determine how ERP behaves to specific events and conditions.  Configuration provides the opportunity for cost-effective flexibility to meet the unique business requirements.  However, where there is no option for configuration then programming must be used to enable ERP software the flexibility to meet the unique requirement.

Programming provides an exact prescription to address a specific business event, condition, or activity.  There are programming techniques and add-on utilities that provide some level of technical flexibility (examples: object-oriented programming, services-oriented architecture) but business flexibility is extremely limited at best (unless an ERP vendor can devise a practical means of applying artificial intelligence – fuzzy logic to their software).   There are limitations with the amount of flexibility and adaptability you can create via software.  What is important to remember is that there are other components of a business solution that better suited to address flexibility and adaptability.

Know Your Strengths

Let’s revisit the components of a business solution along with their inherent strengths.

Strengths of Business Solution

Business Solution Strengths

Too often we do not effectively utilize the strengths of the key components of a business solution.  ERP software is good at automating consistent, repeatable activities based upon a prescribed logic (business rules).  ERP software is not a sustainable, cost-effective option for dynamic activities based upon fuzzy logic (business rules).  People are more flexible and adaptable than ERP software.  Please do not take the above statement to an extreme and infer that every customer should conform their business activities to the ERP software.  ERP implementations should include software enhancements to address the unique value-add requirements of a customer.

Flexibility and adaptability only have value within the context of enabling ERP to position itself optimally in supporting key business drivers.   Next, we will discuss the common drivers that must be coordinated as part of addressing flexibility and adaptability.

Finding Balance

Every customer will have unique business drivers that must be managed in a balanced approach.  Given my implementation experience following are what I consider the common business drivers that we might address as part of an ERP implementation

Balancing ERP

A balanced ERP solution

Can we have a flexible and adaptable ERP solution?  I believe that the answer is yes.  Can we have an efficient and effective ERP solution?  Yes.  Can we have a scalable and efficient solution?  Yes, however we can only experience both characteristics to a certain level.  The challenge I observed is when an extreme position is taken in one of these areas.  Like a ball on a flat table once we start tilting the table (taking an extreme position) the ball will roll off the table – – along with your ERP implementation.

Finding balance is an ongoing exercise to find the right level of applying the influence of the specific business driver upon the ERP project.  It is also important to know and understand at what level of influence will business drivers start conflicting with one another.


Flexibility and adaptability are reasonable expectations for a business solution.  The key challenges in this area tend to be around inaccurate expectations and not effectively utilizing the individual components of a business solution.  What is required is a practical analysis of the strengths, weaknesses, and business drivers to develop a balanced approach for success.  This analysis is not a one-time event but a continuous effort that is triggered when emerging pain is experienced.  Experiencing pain provides the opportunity for rebalancing your ERP solution.

Customers – Insist on an ERP Knowledge Transfer Plan

What Gets Tracked and Measured Gets Done

How do you measure knowledge transfer?  Customers – have you ever received a report or completed checklist that demonstrated the Implementation Partner conducted knowledge transfer?   Knowledge transfer is a process, not just a milestone task on a project plan.  Consider the following illustration to identify the importance of knowledge transfer.

ERP Business Solution

Business Solution Defined

In a previous article I referred to this view and also identified people as the component with the largest impact to a successful business solution.  A key enabler for people being successful is Implementation Partners conducting effective knowledge transfer.  For many ERP implementations, knowledge transfer is a process that is loosely managed which results in the Implementation Partner providing support long after the go-live date. For an area so important it demands that we formalize this process to ensure completeness.

Best Practice: Knowledge Transfer Plan

Simply put, if you want to ensure that an objective is reached then you need a plan.  A knowledge transfer plan first defines the knowledge transfer process and the methods that will be used to conduct knowledge transfer.    Second, it defines all the customer’s roles & responsibilities that are required to support the entire business solution – both from a functional and technical perspective.  Third, the knowledge transfer plan should act as a checklist for each individual role validating that effective knowledge transfer has taken place.    Following is an example of a knowledge transfer plan.

Knowledge Transfer Process for Consultants

Knowledge Transfer Plan

Effective knowledge transfer is more than just training or having a user sit next to a consultant.  It requires a holistic approach in using several methods (training, mentoring, knowledge generation, and interactions) to be successful.  The end result of knowledge transfer is enabling the customer to support their new business solution.  

Implications for Implementation Partners

Knowledge is power!  Knowledge can be money and a key source of competitive advantage for an Implementation Partner.  For an Implementation Partner a key concern is balancing knowledge transfer to ensure customer success versus providing too much knowledge resulting in the customer terminating services early.  It’s important for customers to keep in mind that knowledge sharing happens more freely in a trusted environment.

There are two broad categories of service that an Implementation Partner can provide: staff leadership and staff augmentation.

Broad categories for ERP implementation services

ERP Implementation Service Spectrum

To achieve greater customer enablement Implementation Partners should play more of a staff leadership role during the implementation.  Customers, there is a price associated with effective knowledge transfer.  Also keep in mind that there are greater resource requirements (i.e. knowledge, experience, advisory) for staff leadership services.  Price should not be the only consideration when comparing staff leadership versus staff augmentation services.


True enablement is based upon customers selecting consulting firms that act as a true partner and not just staff augmentation.  If customers only require staff augmentation then I suggest customers get it as cheap as possible, yet don’t expect any reliable knowledge transfer to occur. If this is the first ERP implementation for the customer then I would recommend that the customer selects an Implementation Partner that not only assist your project team but more importantly train and enable your project team to be successful on your own.  That is what a true partner would do.  To maximize knowledge transfer the customer needs to foster a trusted work environment.  Customers – it’s in your best interest to take the lead in creating this environment.

Business Leads and Technology Supports

There is a misconception in the ERP market that says technology is the key enabler to business maturity.  In a previous blog (ERP is Only Part of a Business Solution) I discussed the supporting role ERP plays in a business solution.  Business processes and people have a far greater influence on business process maturity and business results.  Let’s clear up this misconception by examining two areas that have driven its general adoption.


Is Technology changing Business?

I do not believe that technology is changing business but rather technology is finally catching up with leading business practices.  For example, back in the early nineties I read a book on the e-business revolution.  The major premise of the book was that technology was transforming existing business models into an e-business model.  The book provided an example where inventory stocks could now be checked in retailer stores and inventory orders could be generated to maintain a desired stock level.  The book explained that this is an emerging requirement due to new e-business technology.

I have to humbly disagree with this analysis.  The above requirement had always been a desire of business.  I remember back in the early fifties when my father would make the rounds as a salesman to his retailer customers to see their inventory and manually created orders to maintain the retailer’s inventory levels.  Many businesses did not perform this process because (a) it was manually intensive work, and (b) it reduced focus on higher priority business activities.   Technology is now providing a cost-effective vehicle to accomplish this business requirement.

Build It and They will Come

Everyone has heard the phrase “build it and they will come”.  Several internal IT and external Implementation Partners & ERP vendors have used new technology as the value proposition for ERP implementations.  This philosophy may have worked in the era of “green screens” and emerging client/server technologies but it does not work in today’s world.  Technology driving Business is like putting the cart before the horse.  I recently talked with a customer where the IT organization and ERP vendor took the above approach for implementing new Business Intelligence (BI) software.  The business users felt limited and constrained by the technology.  Results – user adoption was low and now business users are looking at implementing their own BI solution(s).  Needless to say that the ERP vendor, the Implementation Partner, and their own internal IT organization are no longer considered trusted advisors.

What Drives Business Results?

Technology is a great enabler that can play a role in supporting the generation of business value.  However, technology is not always the best approach to address problems that may be inherent in the business model.  Example: automating non-value-add business activities will not generate business value for the customer.  Also consider that most business value is generated outside the ERP software.    “Making decisions and implementing them is where business value is created in an organization.” (Dawson, Ross. Developing Knowledge-Based Client Relationships. Butterworth Heinemann, 2000).   ERP does not have the capacity to make decisions having considered a diverse range of issues, and will not have the capacity to do so in the near future (maybe in our lifetime we should have artificial intelligence capabilities embedded within ERP).  Knowledge is only an attribute of people.  Technology stores information.    So how should we leverage ERP to support greater business results and business maturity?   Consider the follow illustration:

Key Drivers for Business Results

Key Drivers for Business Results


It is important to note that business processes and people have a far greater impact on business results than technology.  Technology can be a cost-effective solution in automating consistent rules and activities.  However, technology like ERP can only utilize information that has been codified.  There will always be tribal business-related knowledge and experience that exists outside technology.  Some of this tribal knowledge is leading or emerging business activities/rules.  In this situation where business rules and activities are radically evolving then technology is not a cost-effective solution for automation. 


It is important to understand and appreciate what technology can and cannot do for a customer.  Often the true problem lies not with the ERP software itself (granted there always software bugs and fixes to apply) but rather the demand for quick fixes and rapid cures to business challenges.  If the ERP software did not improve the performance of the underlying business model then executive management would conclude that the ERP implementation was a failure. 

Technology like ERP can be an enabler and a limitation for customers.  To ensure enablement over limitation you must first understand the right relationship between business and technology.  Once you understand the key strengths and weaknesses of both areas then you will have a greater insight to the right application of technology to support the customer in driving valued business results.

Get it wrong the first time! The case for ERP iterations.

We have all heard the phrase “Get right the first time” used as part of an effort to reduce costs and accelerate implementations.  Unfortunately, many have interpreted this to mean doing an activity once.  We attempt to run ERP implementations as a production process.   Good production processes deliver the anticipated result (a known result), for a standard cost, within a given time.  In contract, ERP implementations are more of an exploration process given the customer variability.  Consider the following illustration:

Every ERP Implementation is Unique

Unique Factors for ERP Implementations

A recurring problem we have with ERP implementations is that we try to “big bang” activities and do not provide an opportunity to learn, adjust, and correct for success.   Iterating certain implementation activities will give us that opportunity.  Let me provide you with a just a few examples.

Project Estimating

 As stated in the Project Management Institute’s (PMI) Project Manager’s Body of Knowledge (PMBOK) there are three types of estimates or what I like to call “levels of understanding”.  Estimating is based upon our level of understanding regarding effort, scope, assumptions, constraints, and objectives.

Estimating for ERP Implementations

ERP Estimates

As you move further into an ERP implementation the better we are able to estimate. Why?  The key reason is that you have more proven information to base your estimation.  I worked on generating ERP implementation estimates for the last 10 years and I can safely say that I could never generate a definitive estimate without first going through a detailed fit/gap.  Yet, we expect to hit an implementation estimate that was created before any implementation work is done.  There should be no surprise to the fact that most ERP implementations do not hit their budget given the level of accuracy associated with the estimate. 

Gathering Requirements

Another area for an iterative approach is in requirements gathering.  Recently, I was asked what the best approach for gathering requirements was and my response was that there is no one good approach.

Gathering ERP requirements

Methods for gathering ERP requirements


Do not limit yourself to one method for defining requirements.  The more methods (perspectives) you employ to gather requirements the greater the probability for success because the project will have the opportunity to create a holistic requirements definition.


I firmly believe that every customer’s ERP implementation is unique.  Because every ERP implementation is unique there are a large number of unknowns that we try to address given the limited information we have.  We should take a risk-adverse, iterative approach to remove implementation uncertainty.  Do you think this cause and effect could apply to other areas of an implementation (example: testing, development)?   I am interested to hear your thoughts.

%d bloggers like this: