Lean ERP


If a successful ERP implementation means on time, on budget, and delivering expected functionality, then all ERP implementations fail. They fail by degrees. Some spectacularly, bringing down entire companies, and others mundanely by slowly wasting time, money, and human potential.

Everyone knows this fact but no one addresses it. In the sale and implementation of new systems, everyone uses the same tools and methodologies that fail time and time again. At TurnOnDynamics we are committed to identifying new processes, tools, and attitudes to improve the selection and implementation of ERP systems.



Lean Implementation Methodology

Lean implementation methodology is predicated on the following principals:

  • Vanilla software – do not reinvent the wheel
  • “Wish list” items on the back burner
  • Minimal guidance needed—deep industry and functional experience
  • Immersive training



Most ERP projects go over budget and fail to meet critical deadlines because of a lack of project discipline. Our goal will be to focus on critical business functionality and process flows and implement them as quickly as possible using vanilla software.



After the successful implementation of critical business functionality and process flows, we find it is best practice to run the business without any changes for a three- to six-month timeframe. At the end of that period, it is our experience that “wish-list” items take on two characteristics:

  • They are fewer in number as familiarity with the system identifies work arounds or better solutions.
  • They are more sophisticated in nature as users are a more mature consumer of the software.

Keeping modifications and special requests to a bare minimum will aid in the speed of the implementation and in keeping costs within budget.



ERP implementations are slowed dramatically as management teams struggle to find the time and resources to pass critical knowledge to the implementation team. The partner level TOP implementation partners will need a minimum of guidance as we have assembled a team with deep knowledge and experience in all facets of the project.



Learning a new software application is very like learning a new language. The best way to do it is move to that country and be forced to use it continuously. Our lean implementation plan relies heavily on this training methodology.



Why do sophisticated ERP projects require an “ERP Architect”? And why are ERP Architects the difference between sitting at the starting gate of the Kentucky Derby on either Secretariat or on a camel? Think about your current ERP implementation or any other that you have been...

Does it? I bet it does! A lot. How do I know? Experience. Nothing adheres to the old adage that “A Camel is a Horse Designed by a Committee” quite like ERP software implementations. The problem typically starts with the RFP. Or as I liked to call it in a...