There are times when defining requirements for an ERP selection process that our client would question the effort and think that we are too much in the weeds and should save this detail when evaluating the systems and implementing the system. A leaner approach does make sense for standard requirements, but if the client has complexity and unique processes, then detailed requirements are worth the effort to: Avoid costly change orders when vendors discover what is needed during the implementation – It’s sometime called scope creep and you’re damned if you make the change as it will likely delay the […]