Highlight reports
Information needs to flow freely in project management, whether that be to the project manager or from them. One flow of information must be from the project manager to the Executive, and other senior interested parties. These updates are highlight reports.
A highlight report is exactly what it sounds like – a report that only mentions the highlights. It should be a brief document which (hopefully) mainly confirms that progress has been as expected. Where there have been variations from what is expected, you should mention that corrective action has been taken.
What you don’t want to do is to turn these reports into a running commentary on the project management. There is a temptation both to demonstrate that you are actually doing something, and also to cover your back a little by setting out everything that you have done over the week.
The truth is that your Executive really shouldn’t want this level of detail. You have been hired to do a job, to manage the project. If you start sending a full commentary of the project up to the Executive, of every little thing that has happened, of every small decision you have made, you are essentially making him also manage the project by proxy.
The Executive doesn’t need to know all the details. He needs to know you have the project under control. He needs to know if problems come up that you can’t solve. He needs to know if you have to go over tolerances. He doesn’t need to know that you are just doing your job, that you are just getting on with it.
So free up his time, and yours – just the highlights.
Good comment. From my experience though it isn’t usually the project manager that is causing the problem with clogging up the executives time but the executives themselves. This could be because they’re either the controlling type (read control freak) or they don’t fully understand their role as a project executive.
For example, a good project manager could start a project off with just the highlights reported as you’ve outlined but the executives start demanding more and more information because the report doesn’t detail what they think/expect to see – that work is being done everyday to progress “their” project. The primary challenge in my mind isn’t for the project manager to get the report content right but for them to manage the interaction with the executives more effectively. This includes being up front at the start of the project on exactly what the purpose of a highlight report is/isn’t and what the executives roles and responsibilities are.
John
Agreeing with the above commenter here. While this is really good advice to take for the project manager, most of the time it’s micromanaging executives that slow things down the most. It’s best to lay down clear roles and responsibilities, as well as explain exactly what a highlight report is, so there’s no misunderstandings.
Hi admin, i must say you have high quality content here.
Your blog should go viral. You need initial traffic boost only.
How to get it? Search for: Mertiso’s tips go viral