Process Implementation

Support your solution

Supporting your solution sounds like a no-brainer, but think back to your childhood and the "because I said so" moments you had with your peers. While it may be true that your project was initiated by an idea or need, it's your job as an analyst to build support for the change. This can be accomplished by a number of ways, but the simplest method is to develop a strong business case to support the change. Lacking this simple bit of documentation is one of most common points of failure for a process change or implementation. Despite the simplicity of this step, it's also one of the most skipped.A business case is a simple and direct documentation outlining the need for the process change or improvement you are attempting to implement. If the goal is to increase order accuracy the business case would simply outline the need of the organization and explain how success should be measured. For instance, in our example above the business case may be:

The accuracy of our orders continues to present a problem for quality assurance. In order to address this problem we plan to implement an electronic tracking system to monitor order accuracy. Successful implementation of this system is expected to raise our order accuracy from 92% to 98%.

In this brief paragraph you've outlined what the problem is, what the organization plans to do about it, and at what point we consider the plan a success. This rudimentary step answers the most important questions you'll hear from a change averse organization member, "Why are we doing this?"