Why You Need a Champion for a Successful Microsoft Dynamics GP Implementation, and Why That Person Isn’t Who You Think It Is

I've been involved in countless Microsoft Dynamics GP implementations over the years and have come to realize that there is one little-recognized key to both a successful implementation and long term usage. That key is a champion.

By champion I don't necessarily mean a key executive sponsor, though without that you'll probably fail. I'm not referring to a strong administrator or a project manager, though they are important, too. For me, a true champion is a user who embraces the system and becomes the go-to person internally for Dynamics GP.

The ideal champion in my experience is a mid-level accounting person with a strong technology background. Occasionally it's a DBA with a passion for business. In a few lucky organizations, it's someone with prior GP experience. Generally, the best way to find the champion is to walk into a business running GP and ask who writes GP macros--very quickly, you'll find the champion.

A champion is important because this individual finds ways to make the system work within a particular company's unique culture. He or she can talk to support with a clear idea of the problem and apply the solution. The champion can help users who don't embrace the system work through issues.

Champions figure out little things, like how macros work, to make user's lives easier. Finally, a champion reduces the involvement of partner organizations. Not only does this save money, but it actually improves relationships with partners. Being called out for an hour to deal with a stuck check back isn't efficient for most partners and calling for outside help always takes longerthan walking down the hall with a question.

You don't hear about champions during project kickoff meetings. Partners talk about project sponsors, the importance ...