Chapter Four. Writing the good vision
One challenge in leading teams is keeping people focused on the same goals for long periods of time. All leaders fear that decisions they make won’t be remembered. It’s possible that the reasons people had for listening to them today will be forgotten or ignored tomorrow. Perhaps worse, managers themselves may forget which direction they are supposed to be leading the project in. So, the challenge of project management is not only to get things started in the right direction, but also to keep it headed that way.
Chapter 3 included a brief overview of planning documents, such as MRD, vision, and specification. This chapter will focus in on the vision document, the most important of all early planning materials. I’ll explain why vision documents are worth the effort to write, what qualities good ones have, and how to continually get value from them over the course of a project. When they are used properly, they conclude the initial planning phase of a project (see Figure 4-1).
But one note before I start. There are many different ways to divide the ground that MRDs, visions, and specifications cover. Some organizations don’t use MRDs or business justification documents at all, and instead roll that information into the vision document itself. I’ve seen other teams divide what I call the vision document into four or five smaller documents and give them fancy names. A few times I’ve been on very small projects where vision-type information was collapsed down into the specification itself. So, don’t worry about how many documents you should have or what they’re called: I don’t think that’s particularly important. The advice that follows should apply well to any planning process you choose to use.
Taken From:The Art Of Project Management

