In the project management and change management world, there is a tool commonly used called a stakeholder analysis. It's should be used to identify people that could torpedo your project.
If only that was the case.
Many people use a stakeholder analysis to identify everyone that needs to be informed on the project's status.
I remember sitting in a meeting reviewing a stakeholder analysis and it might as well have been a dump from the HR system listing the entire corporate hierarchy all the way down to the summer intern.
The goal of any manager is to reduce the amount of noise in the system (increase the signal-to-noise ratio). This ultimately means streamlining communication. It kills me when an email goes out with hundreds of people in the To: and even more in the Cc... You are essentially asking for unnecessary noise which leads to decreased productivity.
It kills me when the answer to solving a problem is to insert even more management. That also reduces the signal-to-noise ratio and increases the probability that the problem will not get solved.
So here's my advice. For stakeholder communication, the best path is always the direct path. Identify the potential land mines (i.e., people) and develop a strategy to neutralize those land mines. On the flip side, identify the advocates and develop a strategy for them as well. But don't introduce more management noise into the system. There isn't a noise-canceling device made to handle that type of static.

Comments
Post a Comment