Study guide
9.5 Factors That Help and Hinder Communication
APM Project Management Qualification PMQ
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Exam Format & Question Types 1.3 How to Study for APM PMQ
2 Life Cycles
2.1 Linear Life Cycles and Why Work Is Phased 2.2 Iterative and Hybrid Life Cycles 2.3 Project Life Cycles and Extended Life Cycles 2.4 Choosing a Life Cycle: Context, Culture, Strengths and Limitations
3 Governance Arrangements
3.1 Functional, Matrix and Projectised Structures 3.2 Governance Frameworks, Policies and Delegated Responsibility 3.3 Life-Cycle Impact on Governance and Limits of Financial Authority 3.4 Project Roles and Responsibilities 3.5 Project Manager and Project Sponsor Through the Life Cycle 3.6 Linking Projects to Organisational Objectives
4 Sustainability
4.1 Sustainability Responsibilities, Principles and Impact 4.2 Monitoring and Reporting Sustainability Measures
5 Business Case
5.1 Business Case Fundamentals and Analysis Tools 5.2 The Business Case as Baseline and Reviewing Change
6 Procurement
6.1 Procurement Strategy: Purpose and Contents 6.2 Supplier Selection and Negotiation 6.3 Features of Different Contractual Relationships 6.4 Supplier Reimbursement Methods
7 Reviews & Assurance
7.1 Reviews, Decision Gates, Benefits Reviews and Audits 7.2 What Gets Reported and Informing Decisions 7.3 Why Activities Are Re-Planned After a Review 7.4 Project Assurance
8 Transition & Benefits Management
8.1 Transition Requirements and Business-as-Usual Readiness 8.2 Knowledge Transfer and Agreeing the Transition Plan 8.3 Benefits Management: Identification to Realisation 8.4 Aligning and Communicating Benefits
9 Stakeholder Engagement & Communication
9.1 Stakeholder Analysis, Influence and Engagement 9.2 The Communication Management Plan and Its Benefits 9.3 Managing Stakeholder Expectations 9.4 Communication Methods and Tailoring the Message 9.5 Factors That Help and Hinder Communication
10 Conflict Resolution
10.1 Sources and Impacts of Conflict 10.2 Addressing Conflict and the Thomas-Kilmann Model
11 Leadership
11.1 Leadership, Motivation and Team Performance 11.2 Changing Leadership Styles for the Situation 11.3 Coaching, Mentoring and Emotional Intelligence
12 Team Management
12.1 Team Development Stages and Models 12.2 Characteristics and Benefits of Effective Teams 12.3 Leading Virtual and Hybrid Teams
13 Diversity & Inclusion
13.1 Diversity Characteristics and the Equality Act 13.2 Incorporating Diversity and Diverse Thinking 13.3 Conscious and Unconscious Bias and Fair Treatment
14 Ethics, Compliance & Professionalism
14.1 Continuing Professional Development and Competence 14.2 Sources of Specialist Advice and Standards 14.3 The Legal and Regulatory Landscape
15 Requirements & Solutions
15.1 Establishing Scope Through Requirements Management 15.2 Managing Scope Through Configuration Management 15.3 Solutions Development and Prioritisation
16 Quality Management
16.1 Quality Planning, Indicators and the Business Case 16.2 Quality Control and Success Criteria
17 Integrated Planning
17.1 The Integrated Project Management Plan: Format and Contents 17.2 Why an Integrated Plan Matters
18 Schedule Management
18.1 Defining Scope and Breakdown Structures 18.2 Dependencies and What Drives the Schedule 18.3 Re-Estimating and Schedule Optimisation
19 Resource Management
19.1 Determining Resource Requirements and Availability 19.2 Organisational Breakdown Structure and RACI 19.3 Categorising and Allocating Resources 19.4 Resource Smoothing and Resource Levelling
20 Budgeting & Cost Control
20.1 Creating a Budget and Cost Types 20.2 Earned Value and Cost Forecasting 20.3 Monitoring and Reporting Financial Performance 20.4 Closing Down Project Finances
21 Risk & Issue Management
21.1 Benefits of Risk and Issue Management and Contingency Planning 21.2 The Risk and Issue Management Processes 21.3 Proactive and Reactive Risk Responses 21.4 Governance in Risk and Issue Management
22 Change Control
22.1 The Change Control Process and Its Stages 22.2 What a Change Request Must Capture 22.3 Assessing Options and the Impact of a Change 22.4 Recommending Decisions and Updating Plans
9.5 Factors That Help and Hinder Communication
Key Takeaways Explain This Topic AI
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.
Last updated: August 2026
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.