Implementing Dynamics NAV as your ERP system is not a turnkey project. Purchasing and implementing Dynamics NAV is not like installing Microsoft Office, for which you run the Setup.exe file and be done with it. Implementing Dynamics NAV is a process, and with such a process, you need people that are involved in the process to actively participate in all phases of the implementation. How involved the client's team is will affect the final result of the implementation.

In the preceding diagram, you can see that implementing Dynamics NAV on the partner side is a project that can be framed within a larger project—the implementation of Dynamics NAV at the customer's side. Depending on the scope of the project, the amount of work on each side may differ.

As in any project, the definition of goals is essential to measure whether the project succeeds or not. Goals have to be clearly defined at the beginning of the project and all parties must agree on them. If you don't define clear goals, you may find yourself working as hard as you possibly can and still never able to satisfy your boss or end users.

It not uncommon to define goals such as "improve the sales process". The question is by how much does it have to be improved? How is the improvement going to be measured? When are you going to measure it? Honestly, most of these questions do take more time than it's worth to measure. Most of the time, the measurement of these goals is just a gut feeling. However, if they are defined clearly by your customer, measurements can be achieved.