HKSM

Communication models are simplified views of how information moves between senders and receivers, including encoding, channels, decoding, feedback, and noise. Project teams use them to plan, analyze, and improve stakeholder communication.

Definition

In practice, models range from linear (one-way) to interactive (two-way) to transactional (simultaneous exchange), highlighting roles, media, context, and barriers.

Key Points

• Shows how information is created, transmitted, received, and confirmed.
• Highlights roles, channels, feedback loops, and potential noise or barriers.
• Guides selection of channels and frequency suitable for each stakeholder.
• Supports measurable feedback, timing expectations, and escalation paths.
• Scales from single-message flows to program- or portfolio-level communication.
• Feeds the communications management approach and working agreements.

What the Diagram Shows

• Actors: sender, receiver, and any intermediaries (e.g., PM, sponsor, team lead).
• Message lifecycle: encode, transmit, decode, understand, and acknowledge.
• Channels and media: email, meetings, chat, dashboards, documents, or tools.
• Feedback mechanisms: confirmation, questions, approvals, and issue threads.
• Noise and constraints: language, culture, time zones, bandwidth, policy, and overload.
• Context and environment: formality level, confidentiality, urgency, and timing.

How to Construct

• Clarify the purpose: what decision, update, or collaboration do you need to enable.
• Identify stakeholders and roles involved in creating, relaying, and consuming the message.
• Select the model type: linear for broadcasts, interactive for Q&A, transactional for collaborative work.
• Map the flow: sender to receiver, channels used, and explicit feedback paths and time expectations.
• Add likely noise sources and constraints, plus controls to mitigate them.
• Define rules of engagement: formats, cadences, service levels, and escalation triggers.
• Validate the diagram with stakeholders and refine until it matches real behavior.

Inputs Needed

• Stakeholder list, roles, and communication needs or preferences.
• Project objectives, decision timelines, and critical information types.
• Available channels, tool landscape, and organizational policies.
• Team distribution, language, culture, and time zone information.
• Risk, issues, and lessons learned related to past communication problems.

Outputs Produced

• Communication model diagram(s) for key flows (e.g., status, changes, incidents).
• Feedback and acknowledgment rules, including response time targets.
• Channel selection and usage guidelines tied to message types.
• List of communication risks, barriers, and mitigation actions.
• Inputs to the communications approach or team working agreements.

Interpretation Tips

• Check for clarity at each handoff; reduce steps that do not add value.
• Ensure feedback is explicit and time-bound, not assumed.
• Choose the fewest effective channels to avoid duplication and noise.
• Match channel richness to message complexity and sensitivity.
• Confirm accessibility and inclusivity for all stakeholders involved.
• Stress-test the model with urgent and off-hours scenarios.

Example

A project needs weekly progress updates with sponsor feedback.

• Sender: project manager encodes a one-page summary plus dashboard link.
• Channel: email to sponsor and PMO, with dashboard for detail and a 15-minute review call.
• Feedback: sponsor replies by email within 24 hours or discusses during the call.
• Noise: calendar conflicts, email filtering, and data latency in the dashboard.
• Controls: standardized subject lines, pre-read sent 24 hours ahead, and call recording summary.

Pitfalls

• Overcomplicating the model so people ignore it.
• Assuming feedback will happen without defining how and when.
• Choosing channels based on tools, not stakeholder needs.
• Ignoring cultural and language differences that change message meaning.
• Failing to update the model as the team, risks, or tools change.
• Documenting noise but not assigning mitigations or owners.

PMP Example Question

A distributed team struggles with misunderstood requirements after emails are sent. Which adjustment best applies a communication model to reduce errors?

1. Increase the number of emails sent to the team.
2. Switch to a richer channel with explicit feedback, such as a video walkthrough and Q&A.
3. Copy more stakeholders to ensure visibility.
4. Post requirements only on the document repository.

Correct Answer: B — Switch to a richer channel with explicit feedback, such as a video walkthrough and Q&A.

Explanation: Applying the model, complex messages need richer channels and clear feedback loops. A live session with Q&A reduces noise and confirms understanding.