Skip to content
Tutorials Center
My learning

Topics

Lesson 26 of 41 ยท Risk, Quality and Communication

Communication Management

Plan project communication: stakeholders, channels, frequency, the communication matrix, meeting rules and how the number of channels grows with team size, with Python.

Project managers spend most of their working time communicating: listening in stand-ups, writing status reports, negotiating with sponsors, explaining bad news. When a project fails, "poor communication" appears in the post-mortem more often than any technical cause. Communication management turns that vague skill into a plan: who needs what information, when, in which form, and from whom.

The communication model

At its simplest, communication has a sender, a message, a channel and a receiver. The sender encodes the idea into words, charts or a call; the receiver decodes it with their own background. Noise (jargon, a bad connection, a different first language, being distracted) distorts the message in between. That is why good communication includes feedback: the receiver says back what they understood.

flowchart LR
  S["Sender<br/>encodes message"] --> C["Channel<br/>email, call, meeting"]
  C --> R["Receiver<br/>decodes message"]
  R -->|"feedback"| S
  N["Noise: jargon, time zones,<br/>assumptions"] -.-> C

Feedback closes the loop; without it you only know what you sent.

Communication styles

  • Push: you send the information (email, report, announcement). Good for facts; you cannot be sure it is read.
  • Pull: the audience fetches it (wiki, dashboard, shared folder). Good for large volumes of reference material.
  • Interactive: two-way, in real time (meeting, call, chat). Best for complex or sensitive topics.

Use richer channels as the stakes rise. A budget cut should never be announced in a group chat message.

Written communication leaves a record. Spoken communication builds relationships. Complex decisions need both: talk first, then confirm in writing.

The communication management plan

The plan answers six questions for every piece of information:

Question Example
What? Weekly progress and risks
Who receives it? Sponsor, steering committee
Who sends it? Project manager
How? One-page PDF plus 15-minute call
When? Fridays, 14:00
Where is it stored? Shared drive, "Reports" folder

Start from the stakeholder list (see stakeholder management). A sponsor needs a brief summary focused on money, dates and decisions. A developer needs detail about next week's work. Sending everyone everything is as bad as sending nobody anything: people stop reading.

Python Build a communication matrix

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Communication channels grow fast

Every person you add increases the number of one-to-one lines of communication. For n people the count is n * (n - 1) / 2. A team of 5 has 10 channels; a team of 20 has 190. This is why large projects need structure (team leads, written plans, shared dashboards) instead of "everybody talks to everybody". It also explains why adding people to a late project often makes it later: the new people consume communication capacity before they contribute.

Python Channel growth with team size

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Running good meetings

Meetings are the most expensive form of communication: a one-hour meeting of eight people costs eight person-hours. Make them count.

  1. Purpose first. Every meeting has one of: share information, decide, solve a problem, plan. If it is only sharing, consider a written update.
  2. Agenda in advance, with a time for each item.
  3. Right people only. Required attendees versus optional.
  4. Roles: a facilitator, a timekeeper, a note taker.
  5. Decisions and actions recorded with an owner and a date, sent within 24 hours.
  6. Start and end on time. Parking lot for off-topic items.

For distributed teams: rotate meeting times across time zones fairly, record sessions, write things down, and prefer asynchronous updates for anything that does not need a conversation.

Reporting bad news

Bad news does not improve with age. Rules that hold up:

  • Tell the affected stakeholder directly and early, before they hear it from someone else.
  • State the fact, the impact, what you are doing, and what you need from them.
  • Bring options, not only problems.
  • Stay factual; no blame, no burying the news in paragraph six.

Common communication problems

  • Assumed understanding: "I told them" is not the same as "they understood".
  • Information overload and too many channels (email, three chat tools and a wiki all holding the truth). Pick a single source of truth for each type of information.
  • Jargon with business stakeholders, and vagueness with engineers.
  • Cultural differences: direct versus indirect styles, formality, the meaning of "yes". Ask clarifying questions and confirm decisions in writing.
  • Silence mistaken for agreement. Ask each person directly for objections.

Communication needs may change as the project does; update the plan whenever new stakeholders join or a change alters who is affected.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A team grows from 6 to 12 people. How many communication channels exist at 12?

    n(n-1)/2 = 12 * 11 / 2 = 66 (up from 15 at six people).
  2. 2. Posting a document to a wiki that people read when they need it is which style?

    Pull communication places information where the audience retrieves it when needed.
  3. 3. Which element closes the communication loop?

    Feedback confirms the receiver understood the message as intended.
  4. 4. What should you bring when reporting a serious problem to the sponsor?

    Sponsors need to act. Give the situation, its effect, your plan and what you need from them.

Summary

  • Communication is a loop of encoding, channel, decoding and feedback; noise distorts it.
  • Plan who gets what, how, when and from whom; write it in a matrix.
  • Channels grow as n(n-1)/2, so structure larger teams.
  • Use richer channels for sensitive topics and keep meetings purposeful.
  • Report bad news early with facts, impact, actions and options.

Next: Change Control