It really doesn’t matter how often you communicate with the project team, don’t forgo the weekly status report. I can, and do often think of several reasons why I “can’t” get to it, but having that status report has several key benefits.

1. Aligns everyone to progress and issues – Many times progress and issues can get lost in the smaller, tactical project team. However, a software implementation can be quite a big investment and therefore impacts people outside the immediate project team. The weekly status report provides that source for where we are now, and where we are going.
2. Ensures broader audience keeps your project in mind – While lots of people may need or want to keep the pulse on your software implementation project, other priorities can get in the way. By distributing your weekly status report you are managing multiple layers of stakeholders, and ensuring that your project isn’t forgotten.
3. Credibility – building on the theme of the last blog post, status reports build credibility. If done in a way that gives an honest account of where the project is, regardless of whether it is going well or where there are opportunities for improvement, you are building credibility to you as a project manager and your organization (vendor, department, etc) as a partner.

I generally am on the side of streamlining process, and reducing administrative nonsense. In the case of status reports, they really are a critical tool in keeping everyone in the loop about where you are. If the stakeholders are new to you as a project manager, you may need to redirect people to your status reports, but generally, people jump on the bandwagon and like the more formal approach.