Chapter 4. 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 in which direction they are supposed to be leading the project. 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 2 included a brief overview of planning documents, such as MRD, vision, and specifications. This chapter focuses on the vision document, the most important of all 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).

Figure 4-1. A finalized vision document signifies the end of the planning phase, just as final specifications signify the end of the design phase.
But one note before I start: there are many different ways to divide the ground these documents cover. Some organizations don’t use MRDs or business justification documents at all, and instead roll that information into the vision document itself. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access