8.5 Conclusion

---

8.5 Conclusion

In Chapter 7, I covered the preferred approach for documenting status, so I will refer you specifically back to the sections named "Status Report - Smooth Sailing," and "Status Report - Rough Sailing Ahead" for tips on appropriate style and approach. Just keep in mind that this process is something you want to lock into from the outset, and stay with on a regular and ongoing basis. As far as I am concerned, other than recording facts, the key to documentation is your understanding that it is:

• The project's official organ

• The means by which decisions and issues are clarified

• A recording of decision rationale

• An audit trail useful for many reasons down the road

The key to effective documentation is that its consistent brevity and clarity is such that people read it and respond in kind. If you find yourself juggling a controversial topic, get it out there in writing, and react to the flurry of responses it may generate by holding follow-up meetings. Do not attempt to resolve such matters via e-mail because you end up either with a chain letter or waging a war of words from which it is difficult to escape without many pointless or unfortunate avenues explored. If you understand how to use documentation as a tool, you will get that much further ahead of the game. In our business, that should be one of your biggest priorities.

---