9.5 Factors That Help and Hinder Communication
Key Takeaways
- Diagnose communication failures by locating the break — sender credibility, message clarity, channel fit, receiver capacity, feedback route, or environment.
- Filtering progressively softens bad news as it moves up a hierarchy, which is why projects can look green until they suddenly are not.
- Countermeasures to filtering are structural: independent assurance, direct sponsor access, exception triggers, and treating escalation as competence.
- Information overload is a communication failure too — volume is not communication, and unread packs cannot inform decisions.
- A team that has stopped raising problems usually signals that raising them has been punished, which is a psychological-safety issue rather than a process one.
Outcome 10f closes the stakeholder objective: know the factors which can positively or negatively affect communication. Scenario questions here usually describe a symptom — a message ignored, a decision misunderstood, a team that has stopped raising problems — and ask what is going wrong. The mark is in naming the factor precisely.
Factors that positively or negatively affect communication
Communication succeeds when the intended meaning is received, understood, and — where needed — acted on. Many factors sit between sender and outcome.
Barriers and negative factors (“noise”)
| Factor | How it damages communication |
|---|---|
| Information overload | Important messages are buried; stakeholders disengage |
| Ambiguous language | Different interpretations of “soon,” “ready,” or “complete” |
| Wrong channel | Complex change explained only by mass email; no dialogue |
| Poor timing | News arrives too late for action or during unrelated crises |
| Distrust / history | Past over-promising causes discounting of current messages |
| Hierarchy and fear | Bad news is filtered; sponsors hear only green status |
| Jargon and assumed knowledge | Users and non-specialists cannot decode technical content |
| Cultural / language differences | Literal translation misses meaning; silence misread as agreement |
| Physical / virtual distance | Reduced informal cues; meeting fatigue; drop-offs |
| Conflicting messengers | Sponsor says go; local manager says wait |
| Technical noise | Broken links, wrong distribution lists, inaccessible files |
| Emotional state | Anxiety about job impact blocks absorption of facts |
Enablers and positive factors
| Factor | How it helps |
|---|---|
| Clear purpose | Audience knows why they received the message and what to do |
| Audience analysis | Content matches power, interest, and literacy |
| Trusted sender | Right messenger for the relationship (sometimes sponsor, not PM) |
| Two-way feedback | Questions and confirmation loops catch misunderstanding |
| Consistent narrative | Same core facts across channels |
| Visual management | Simple dashboards and prototypes reduce ambiguity |
| Psychological safety | People raise risks and confusion early |
| Timeliness and rhythm | Predictable cadence builds habit of attention |
| Recorded decisions | Reduces re-litigation and rumour |
| Tailored volume | Less noise, more signal |
| Active listening | Engagement, not broadcast theatre |
| Resources | Time and skills for communication recognised as project work |
On long-response questions, name specific barriers in the scenario (e.g. multi-site shift workers with no email access) and match enablers (team briefings at handover, printed quick guides, supervisor cascade).
Putting LO10 together for exam answers
When a scenario mentions confused stakeholders, missed decisions, or angry expectations:
- Root the answer in stakeholder analysis (who, power, interest, attitude).
- Show how analysis shapes the communication plan (audience, message, method, frequency, owner).
- State benefits of that plan for decisions, adoption, or risk reduction.
- Address expectations explicitly — baseline, honesty, non-goals, confirmation.
- Select push / pull / interactive methods with reasons and tailoring.
- Identify barriers/noise and enablers to make communication effective.
That structure covers LO10(b)–(f) and connects cleanly to the analysis–engagement chain in the previous section: analysis informs engagement; engagement and communication plans turn insight into controlled, people-centred delivery.
A model for diagnosing a communication failure
Any communication can be broken down into sender, message, channel, receiver, and feedback. Locating the break is what turns a vague answer into a scoring one.
| Element | Positive factors | Negative factors |
|---|---|---|
| Sender | Credibility, clarity of purpose, consistency, approachability | Low trust, hidden agenda, inconsistent messages between senders |
| Message | Plain language, right level of detail, clear ask | Jargon, ambiguity, excessive length, no action requested |
| Channel | Suited to richness needed; accessible; reliable | Wrong richness, technology failure, inaccessible format |
| Receiver | Attention, capability, motivation, shared context | Overload, distraction, different assumptions, language barrier |
| Feedback | Confirmation of understanding, safe to challenge | No return route, blame culture, silence taken as agreement |
| Environment | Time to absorb, psychological safety, cultural fit | Time pressure, organisational politics, remote isolation |
Noise, filtering and the silence that matters most
Two negative factors deserve naming explicitly because they recur in PMQ scenarios.
Filtering is the progressive softening of bad news as it travels up a hierarchy: each layer rounds "at risk" towards "manageable" until the board hears green. It is the mechanism behind projects that appear healthy until they suddenly are not. Countermeasures are structural rather than personal — independent assurance, direct access from the project manager to the sponsor, exception-based reporting with defined triggers, and a culture where escalation is treated as competence.
Information overload is the opposite failure and just as damaging: a 60-page pack circulated 24 hours before a decision guarantees that nobody has read it. Volume is not communication.
The most examinable warning sign, though, is a team that has stopped raising problems. That is almost never because problems have stopped; it is because raising them has been punished. In an answer, identify psychological safety as the factor, and propose concrete responses — thank people for early warnings, separate the problem from the person, act visibly on what is raised — rather than "improve communication".
Bringing outcome 10 together
For any stakeholder or communication scenario, the reliable answer structure is: analyse who the stakeholders are and what they need (10a), show how that produces the communication plan (10b, 10c), state what expectation must be managed (10d), choose and justify the method and tailoring (10e), and name the factor helping or hindering the exchange (10f). That sequence covers the whole learning objective and reads as professional practice rather than a list of tips.
A steering group receives green status reports for six consecutive months and is then told the project will overrun by a year. Investigation shows each management layer had softened the wording it received. Which communication factor best explains this?
A project manager notices that team members have stopped raising risks and issues in weekly meetings, although delivery problems are clearly occurring. What is the most appropriate interpretation and response?