jump to navigation

How Much Information Should a Manager Give To Their Team? February 4, 2013

Posted by Tim Rodgers in Management & leadership, Organizational dynamics, Project management.
Tags: , , , , ,
trackback

I’ve been pretty busy over the last few weeks focusing on my job search, interviewing for a couple of positions, and preparing for a possible teaching assignment at a local university. The evaluation process at the university included a 15-minute audition that was intended to provide some insight to each candidate’s presentation and facilitation skills in a classroom environment. Fifteen minutes is not much time, and during my lesson planning I decided to deliver a small packet of information, repeated and reviewed. I know from experience that there’s a tendency to overestimate the ability of an audience to listen and absorb.

This reminded me of something I read during my preparation for the Project Management Professional (PMP) certification exam last year. One of the topics on the exam was Project Communications Management, which included identifying stakeholders, and planning the communication processes necessary to keep them informed, according to their expectations. Project managers were encouraged to strive for efficient communication, providing only the information that each stakeholder requires.

I suppose the intention is to keep it simple and avoid the confusion and doubt that can accompany information overload, but I don’t think this is necessarily a good strategy. There are potential problems when the project manager is the only person who has all the information about the project:

1. You run the risk of  creating a dependency bottleneck, where one person must always be available to communicate status, resolve issues, and answer questions. This can be mitigated somewhat with easily-accessible project documents, assuming people know where to find them and are willing to use them.

2. Team members may be constrained by a narrow perspective that limits their ability to respond quickly or deal with ambiguity because they aren’t permitted to see the big picture. Surely the project benefits when the brainpower of all team members is fully-engaged. even at the risk of sharing “too much” information.

Look, I don’t think everyone needs to know everything all the time. I just think we shouldn’t be too quick to withhold information in the name of communication efficiency.

Comments»

No comments yet — be the first.

Leave a comment