Project Management Books from the Project Management Advisor™ |
Part
V: The Truth About Writing Status Reports |
|
| |
|
This part contains five truths, as follows:
Truth 22: Focused status reports get read; random ones don’t - Getting your point across when reporting status on activities in your organization means keeping it concise, relevant, and focused. Rambling status reports which try to pass the weight test only confuse recipients or, even worse, turn them off to where they don't read your status reports.
Truth 23: Communicate status in less than a minute - Using a series of indicators and a structured format will minimize the time your recipient spends trying to understand how you're communicating status and focus on what you're trying to communicate.
Truth 24: Know who, when and how - Understanding your recipients' need for status information, when they need to receive the information, the frequency it needs to be received, and the most efficient method of transmittal is crucial to getting your status report point across.
Truth 25: No one reads yesterday’s news - Creating a well-written status report is great. Sending it out with stale information makes it a waste of time. Sending timely information gives recipients time to react to issues and boosts your credibility as an effective manager.
Truth 26: Status reports aren’t code for cover your butt - Hiding behind a status report or using a status report as a vehicle for absconding responsibility can label you as a cowardly lion. Status reports are meant to inform recipients and solicit help; not something which you can hide behind.
Order The Truth About Getting Your Point Across here.