In the Programme Management SIG Webinar “Turbocharge project performance by reinventing communication” Mark Phillips gave us a fascinating insight into the role and importance of communication within projects and programmes.
Starting with an obvious - but often overlooked - observation that projects are about people and that therefore communication between people is the binding structure that holds a project together. If communication breaks down or is ineffective then project delivery suffers. Conflict within a project has a direct impact on it, often causing cost and time overruns.
Interestingly the use of technology in communication can make things worse, not better, if it is not used wisely. The introduction of new tools can create more noise and reduce the quality of the signal.
The way in which the people are organised - for example multiple contractors or a single organisation, flat or as a hierarchy - drive the sorts of risks that projects face and affect the style of communication. With multiple contractors for example, communication needs to be formal and follow the hierarchy and the project will be exposed to more integration risk than a single organisation project.
Mark offered a couple of case studies by way of illustration.
● The F18 fighter programme - a very large and complex programme which agreed a common Earned Value Management “language” from the outset and was very successful.
● The Mars Climate Survey Orbiter on the other hand failed to agree even a common scale of measurement (metric vs imperial) between the teams of scientists with the end result that the Orbiter, literally, crashed and burned.
He introduced us to some marketing research that strongly suggests that the time of day and the day of the week that a communication message is sent can have a significant impact on how the message is received. The research indicates that messages sent toward the end of the day/week are more likely to be heard.
The effectiveness of an individual item of communication can be increased if it is a boundary object. A boundary object is something that holds common ground between different groups of stakeholders. Each group may have different insights about, and understandings of, the object but because it is shared across the groups it provides a point of common ground between them.
Mark finished with a discussion about project complexity. Recent research has suggested that problems can be broken down into 3 separate categories:
1. Tame - first order problem requiring the knowledge of a single subject matter expert. Problem is understood outcome is predictable.
2. Messy - Numerous systems involved, requiring input from multiple stakeholders. With collaboration the problem is understandable and the outcome can be predicted.
3. Wicked - Problems that emanate from people. Outcomes and solutions are not knowable upfront because people are unpredictable.
Clipping is a handy way to collect important slides you want to go back to later.