Decision-making is an ongoing task on every project engagement.  Key decisions have to be made throughout by everyone including the project manager, the project team members, the customer, executive management, and usually other stakeholders.  They may be as simple as when to hold a meeting or as difficult as making a go- no-go decision on a phase of the project or the entire project.

What we often lack when making some key decisions is the right information at the right time.  We all know that making what seems to be the right decision based on information that ends up being inaccurate or out of date can be fatal to the project.

What if you could only make decisions on when to cross the street based on a snapshot taken five minutes ago?  Would this help?  Would you have any confidence in whether or not you should cross the street?  After all, it could be a life or death decision.

Well, that’s often how organizations are continually making business and technology decisions.  Many decisions we make on projects are based on what we knew two days ago or two weeks ago or what someone told us last Thursday.  Ideally, information would be flowing to all key personnel constantly and we would be making key business, project, and technology decisions based on what we just learned – not what we knew last week.  What if you could make sense of what you learn as fast as you learn it and put that into play?

There is no magic wand to wave to make this all happen.  However, since the project manager is the key focal point for all communication on the project, there are some things – or at least some actions – that can be put into place that will help ensure that the right information is getting to the right people as quickly as possible.  And that, in turn, should help ensure that the project decisions that are made are based on the most relevant and accurate information possible.

These are:

Develop and distribute a communication plan

The key to getting all of this communication off on the right foot is to publish a communication plan for the project at the outset.  Produce this document shortly after kickoff and let it document and set the tone for all communication that will flow on the project. 

This document will correctly set expectations of how, when, where and through who communication will happen. For more information on the project communication plan, please read an earlier article of mine on the topic here.  You can also download a copy of one of my actual project communication plans to use as a template.  Go to and navigate to the Templates & Downloads page to access the sample plan.

Funnel all communication through the project manager

Communication is key and is probably the most critical function that the project manager performs.  The PM must be responsible for all project communication and the best way to make that happen is to be sure to funnel all communication through the PM.  Set that tone in the project communication plan mentioned above and stick to it.

Distribute weekly status reports and conduct weekly status meetings

As part of that project communication responsibility, the PM must be consistent and thorough in producing weekly status reports and holding weekly status meetings – both internally with his project team and with both teams together on a joint call or meeting session.

Distribute revised project schedules frequently

At a minimum, the project schedule needs to be revised and redistributed on a weekly basis to all key project personnel.  However, anytime there is a major issue or action that affects the project and the schedule, the project plan must also be updated and redistributed at that point as well – even if that is sometimes daily during critical points in the project.