-
Decisions – Not Documents – Move ERP Implementations Forward
Information Alone Does Not Generate Value I grew up in a time when information was hard to obtain. Generating information was seen as a valuable exercise because information was a scarce resource. The first software development life cycle (SDLC) I learned was Waterfall. One of the key focus areas for the Waterfall SDLC was documentation… Read more
-
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. … Read more
-
ERP is Only Part of a Business Solution
Back in the 80s Enterprise Resource Planning (ERP) was deemed the panacea for business pains caused by operational inefficiencies and disjointed applications. Then came the realization that ERP was not the final solution but just one piece of the puzzle. In addition we learned that change was not just a software issue, that implementation is… Read more
-
Progressive Leadership for ERP
Knowledge transfer is only the beginning to enablement. Many implementation partners (including myself) have handled enablement as an event or milestone that occured as part of the cut-over to production. We as implementation partners too often assume that the traditional, informal “do what I do” approach between consultants and customer was sufficient for customer enablement. … Read more
-
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… Read more
-
Reverse Engineer to Business Requirements
A critical activity for any ERP implementation is gathering business requirements. The purpose of business requirements is to define the needs that will enable business activities to generate business results. The traditional school of thought is that if we capture all the requirements then we assume that we will develop a solution that will produce… Read more
Join the community! 16k Audience across 100 countries!
