VISION LOSS

Is having a "Vision" important only for strategic planning? We are taught that a person can't possibly know where they are going without a Vision. What is the goal? The purpose? In other words, what's the point?

It's easy to develop a Vision for any project, especially when the desired result is known. For example, if a company requires a functional payroll system; then, the Vision could be: "To have a payroll system that fulfills the needs of the employees, management, and the company in perpetuity."

Having a Vision provides a focus for projects and a "landing place" to return to when needed—going back to the Company Payroll Project, what if a group began discussing medical insurance record-keeping during a project meeting? A simple "Vision" reminder could sway the discussion topic back to where it belongs—Payroll.

The project's Vision is an integral part of a project plan. Even if the Vision may seem "obvious." It must be stated and in writing. Too often, when beginning a new project. The Vision get's left out because it is assumed that everyone is on the same page. This assumption is dangerous and can lead to confusion and conflict down the road.

So, take the time, write down, and post your project Vision. If it's possible, create the Vision as part of a consensus meeting. It's a great way to begin a project as a cohesive group.