Root Causes of Communication Breakdowns

Overview
In the PMI Construction Professional (PMI-CP) framework, communication is the foundation that holds a construction project together. Owners, designers, general contractors, subcontractors, suppliers, regulators and community stakeholders must all exchange accurate, timely information. When that exchange fails, the result is a communication breakdown. Typical consequences include rework, claims, schedule slippage, safety incidents and damaged relationships.

This guide covers what root causes of communication breakdowns are, why they matter, how they arise and how to diagnose them, and how to answer exam questions on the topic.

1. Why This Topic Is Important

Construction is uniquely communication-intensive. Projects are temporary and the supply chain is fragmented. Many organizations come together, often for the first time, under contracts that can be adversarial. Each handoff is a point where information can be lost or distorted, for example:
• designer to contractor
• office to field
• general contractor to subcontractor

Key reasons the topic matters:
• Cost of rework: Industry studies consistently link a large share of rework to poor communication. Examples include wrong drawing revisions, misunderstood RFI responses and undocumented field changes.
• Safety: Hazards that are not communicated clearly at toolbox talks, pre-task plans or shift handovers can lead to injuries or fatalities.
• Claims and disputes: Undocumented directives, late notices and verbal approvals are frequent triggers of change-order disputes and litigation.
• Stakeholder trust: Owners, neighbours and authorities lose confidence when they are surprised by bad news or kept uninformed.
• Schedule performance: Slow RFI and submittal cycles are often caused by unclear responsibility or poor routing. They delay procurement and critical-path activities.

Why root causes and not just symptoms? Fixing a symptom solves today's problem. Fixing the root cause prevents the problem from recurring. For example, re-sending one missing drawing is a symptom fix. Correcting the document-control process that allowed it to go missing is a root-cause fix. PMI consistently rewards this deeper, systemic thinking.

2. What Are Root Causes of Communication Breakdowns?

A communication breakdown occurs when the intended message is not received, not understood, not acted upon correctly, or not received in time.

A root cause is the fundamental, underlying reason the breakdown happened. If it is removed, the problem will not recur.

The basic communication model
PMI uses a sender-receiver model with these elements:
• the sender encodes a message
• the message is transmitted through a medium or channel
• noise may interfere along the way
• the receiver decodes it
• the receiver provides feedback or acknowledgement to confirm understanding

A breakdown can occur at any of these points. Root causes are the reasons those points fail.

Major categories of root causes

A. People and behavioural causes
• Assumptions that others already know the information
• Reluctance to deliver bad news, so issues are hidden until they become crises
• Poor listening and failure to confirm understanding
• Personality conflicts, lack of trust, or a blame culture
• Inadequate communication skills or technical jargon used with non-technical stakeholders
• Selective filtering of information to protect self-interest

B. Process and planning causes
• No communication management plan, or one that is not followed
• Unclear roles and responsibilities: no RACI matrix, so nobody owns a message
• Undefined escalation paths
• Weak document control, which leads to outdated drawings and multiple versions in circulation
• Inefficient RFI and submittal workflows with no tracking or due dates
• No formal change management process, so field changes are made verbally
• Missing or ineffective meetings, or too many meetings with no clear outcomes

C. Organizational and structural causes
• Information silos between departments or between office and field
• Fragmented project delivery: design-bid-build separates designer and builder
• Multiple tiers of subcontractors, which creates long communication chains
• High staff turnover with poor handover of knowledge
• Matrix structures where staff report to several managers

D. Contractual and commercial causes
• Adversarial contracts that discourage open sharing for fear of liability
• Ambiguous scope definitions and specifications
• Unclear contractual notice requirements
• Misaligned incentives among parties

E. Cultural, language and geographic causes
• Multilingual workforces, especially in field crews
• Differences in national or organizational culture, such as attitudes to hierarchy or directness
• Distributed or virtual teams across time zones

F. Technology and channel causes
• Wrong channel for the message, such as sending complex or sensitive issues by email instead of discussing them face to face
• Incompatible software, for example BIM model versions or file formats
• No common data environment (CDE) or single source of truth
• Information overload: too many emails, notifications or reports
• Poor connectivity on remote sites

G. Stakeholder-related causes
• Stakeholders not identified early, so they are left out of communications
• Stakeholder needs, interests and preferred communication methods not analysed
• Engagement level not matched to stakeholder influence and interest

3. How It Works: Mechanisms and Diagnosis

The complexity of communication channels
The number of potential communication channels is n(n-1)/2, where n is the number of stakeholders.
• A project with 10 stakeholders has 45 channels.
• Adding 5 more stakeholders (15 in total) raises this to 105 channels.

Construction projects add stakeholders as phases progress. Complexity, and the risk of breakdown, therefore grows quickly. This is why structured plans, clear hierarchies and defined information flows are essential.

How breakdowns typically unfold
1. A trigger occurs, such as a design revision.
2. The process gap fails to route the revision, for example because there is no transmittal protocol.
3. The receiver continues working with outdated information.
4. There is no feedback loop to detect the error.
5. The consequence emerges: rework, a delay or a dispute.

Root cause analysis (RCA) tools
• 5 Whys: Ask 'why?' repeatedly until you reach the systemic cause.
Example:
– Concrete was poured with the wrong embed layout. Why?
– The crew used Revision B. Why?
– Revision C was not distributed to the field. Why?
– The document controller emails only the superintendent, who was on leave. Why?
– There is no defined distribution list or CDE.
Root cause: a deficient document control process.

• Fishbone (Ishikawa) diagram: Organize possible causes into categories such as People, Process, Technology, Environment, Materials and Management.
• Pareto analysis: Identify the few causes responsible for most breakdowns, following the 80/20 rule.
• Lessons learned and retrospectives: Capture recurring communication issues and feed them into the organizational process assets.
• Stakeholder feedback, surveys and communication audits: Test whether messages are actually received and understood.

Preventive and corrective responses
• Develop and maintain a communications management plan that defines who needs what information, when, in what format, through which channel, and who sends it.
• Use a stakeholder register and an engagement assessment matrix, which compares current and desired engagement levels.
• Define roles with a RACI matrix.
• Implement a common data environment, BIM coordination, and formal RFI, submittal and transmittal logs.
• Establish escalation procedures and issue logs.
• Adopt collaborative delivery approaches, such as integrated project delivery (IPD), partnering and the Last Planner System, where appropriate.
• Hold structured meetings with agendas, minutes and action items.
• Provide multilingual safety communication, visual aids and confirmation of understanding.
• Use active listening and face-to-face communication for complex, sensitive or conflict-laden issues.
• Match the method to the purpose:
– interactive communication: meetings and calls
– push communication: emails and memos
– pull communication: portals and repositories

4. How to Answer Exam Questions on This Topic

PMI-CP questions are usually situational. You are given a scenario and asked what the construction professional should do first, next or best, or what the most likely cause is.

Step-by-step approach
1. Identify the real problem. Separate the symptom (for example, the subcontractor installed the wrong fixture) from the likely cause (for example, the submittal approval was never communicated).
2. Classify the cause. Decide whether it is mainly people, process, organizational, contractual, cultural, technology or stakeholder-related.
3. Look for the systemic fix. Prefer answers that correct the plan, process or structure over one-off workarounds.
4. Check the sequence. PMI favours this order: analyse or assess first, consult the plan and stakeholders, then act. Escalate only when the matter is beyond your authority.
5. Eliminate weak options. These include blaming individuals, ignoring the issue, taking unilateral action outside your authority, or escalating immediately without investigating.

Sample question 1
A general contractor discovers that three subcontractors have been working from different revisions of the structural drawings. What should the project manager do FIRST?
• A. Issue back-charges to the subcontractors
• B. Stop work and conduct a root cause analysis of the document distribution process
• C. Email the latest drawings to everyone
• D. Report the issue to the owner

Best answer: B. Emailing the latest drawings (C) fixes the symptom only. Back-charging (A) assigns blame without understanding the cause. Reporting to the owner (D) is premature. Stopping affected work to prevent further rework and investigating the cause addresses the systemic problem.

Sample question 2
Field crews repeatedly misunderstand safety instructions delivered at morning briefings. Several workers have limited English proficiency. What is the MOST likely root cause?
Answer: A language and cultural barrier, combined with no confirmation of understanding. The appropriate response includes multilingual or visual communication, interpreters or bilingual foremen, and teach-back techniques.

Sample question 3
A community group complains that it learned about night-time concrete pours only after they began. What should have prevented this?
Answer: Early stakeholder identification and analysis, with the community group in the stakeholder register, plus a communications management plan that defines advance notification. The root cause is a gap in stakeholder identification and planning.

Exam Tips: Answering Questions on Root Causes of Communication Breakdowns

Tip 1 – Symptom versus root cause: If an answer only patches the immediate problem, it is rarely the best choice. Look for the option that prevents recurrence.

Tip 2 – The communications management plan is your anchor: When a scenario describes confusion about who gets what information, the answer often involves reviewing or updating the communications management plan or the stakeholder engagement plan.

Tip 3 – Roles and responsibilities: Repeated 'I thought someone else told them' situations point to unclear accountability. Think RACI.

Tip 4 – Choose the right channel: Complex, sensitive or conflict-related messages call for interactive, face-to-face communication. Formal or contractual matters call for written, documented communication.

Tip 5 – Remember the formula: n(n-1)/2. Calculation questions may ask how many channels are added when stakeholders join. Always subtract the old total from the new total.

Tip 6 – Feedback loops matter: A message is not truly communicated until understanding is confirmed. Answers that include acknowledgement, read-back or teach-back are strong.

Tip 7 – Know the construction-specific triggers: RFIs, submittals, transmittals, change orders, BIM coordination, toolbox talks, shift handovers, daily reports and meeting minutes are common settings for breakdown scenarios.

Tip 8 – Don't escalate too early: PMI expects you to analyse and try to resolve issues within your authority before escalating to the sponsor or owner.

Tip 9 – Avoid blame-oriented answers: PMI favours collaborative, transparent and solution-focused approaches. Punishment-first answers are usually wrong.

Tip 10 – Think lessons learned: After a breakdown is resolved, the complete response includes documenting it in the lessons learned register and updating organizational process assets.

Tip 11 – Watch for keywords: 'FIRST', 'BEST', 'MOST likely' and 'NEXT' change the correct answer. FIRST usually means assess or analyse. BEST usually means the most comprehensive systemic fix.

Tip 12 – Stakeholder gaps begin at identification: If a stakeholder was surprised or left out, trace the problem back to identification and analysis, not just to the message itself.

Summary
Root causes of communication breakdowns in construction fall into several groups: people, process, organization, contracts, culture, technology and stakeholder management. Successful PMI-CP candidates:
• recognise that symptoms such as rework, disputes and safety incidents usually have systemic causes
• use tools like the 5 Whys and fishbone diagrams to find those causes
• apply structured remedies: communications plans, RACI matrices, common data environments, feedback loops and proper channel selection

On the exam, always aim for the answer that diagnoses before acting, fixes the system rather than the symptom, and engages stakeholders collaboratively.