4.6 Team Communication Plans
Key Takeaways
- The four elements of a communication plan named by ASQ are audience identification, message type, medium, and frequency.
- Audiences are segmented by their stake and influence, and each segment gets a different message, medium, and cadence.
- Rich media such as face-to-face and video suit ambiguous or emotionally charged messages; lean media such as email suit factual, repeatable updates.
- The communication plan is written during Define, not during Improve, because the audience for a change must be prepared before the change arrives.
- Two-way channels are required to detect misunderstanding; a plan consisting only of broadcast messages cannot tell whether it worked.
The four elements
A communication plan is a table, not a philosophy. Every row answers four questions.
| Element | Question | Common mistake |
|---|---|---|
| Audience | Who specifically needs to know? | "All employees" as a single audience |
| Message type | Awareness, instruction, decision request, or feedback solicitation? | Sending an instruction when a decision was needed |
| Medium | Face-to-face, video, meeting, email, dashboard, notice board, training? | Using email for an ambiguous or contentious message |
| Frequency | Once, weekly, at each toll gate, on exception? | One announcement at go-live |
Audience identification
Start from the stakeholder map and segment by stake (how much the change affects them) and influence (how much they can affect the change).
| Segment | Stake / influence | Message type | Medium | Frequency |
|---|---|---|---|---|
| Sponsor and steering group | High / high | Decision requests, risk escalation, benefit tracking | Toll-gate meeting plus one-page brief | Each phase, plus on exception |
| Process owner | High / high | Design of the future state, control plan ownership | Working sessions | Weekly |
| Operators in scope | High / medium | What changes, why, what it means for their work, how to raise problems | Shift briefing face to face, then written standard work | Weekly during Improve, daily at cutover |
| Adjacent departments | Medium / medium | Interface impacts, timing | Existing management meeting | At Define and before implementation |
| Support functions (IT, maintenance, finance) | Medium / high | Specific requests with lead times | Direct request plus ticket | As needed, with named dates |
| Wider organization | Low / low | Awareness and results | Newsletter, dashboard | At closure |
The reliable error is treating operators as low-stake because they are low-influence. They have the highest stake of anyone in the room, and they are the population whose behaviour determines whether the control plan survives.
Message type
Four types, and mixing them is what makes communications ineffective:
- Awareness -- "this project exists, here is the goal and the timeline." Broadcast is fine.
- Instruction -- "from Monday, record the reject reason code before restarting." Must be specific, written, and paired with training.
- Decision request -- "we need approval to run a two-week pilot on line 3." Must name the decision, the options, the recommendation, the deadline, and the decider.
- Feedback solicitation -- "what would stop this working on night shift?" Must be genuinely two-way, and every response must receive a disposition.
A message that tries to do all four does none. The most common failure is a long update email that buries a decision request in paragraph six; the decision does not get made and the team assumes consent.
Medium: match richness to ambiguity
Media richness theory is the useful framing. Rich media carry tone, allow immediate clarification, and support multiple cues; lean media are efficient, repeatable, and create a record.
| Medium | Richness | Best for | Poor for |
|---|---|---|---|
| Face-to-face at the process | Highest | Job-affecting change, bad news, contentious findings | Detailed reference information |
| Video call | High | Distributed teams, working sessions | Large broadcast audiences |
| Meeting with visuals | High | Decisions, toll gates | Anything that needs to be re-read later |
| Written standard work / instruction | Medium | Instructions people must follow exactly | Persuasion |
| Low | Confirmations, records, routine updates | Ambiguous, emotional, or contested messages | |
| Dashboard / notice board | Low | Ongoing performance visibility | One-time critical notices |
The single strongest rule: never deliver a job-affecting change by email first. Deliver it face to face at the process, then follow up in writing. The written version is the record; the conversation is the communication.
Frequency
Frequency is set by the audience's need to act, not by the team's need to report.
- Sponsor: at each toll gate, plus immediately on any risk that could change scope, timeline, or benefit. Sponsors dislike surprises far more than they dislike bad news.
- Team: weekly, short, with a visible board.
- Affected operators: light during Define and Measure, weekly through Improve, and daily around cutover, then folded into the normal shift briefing during Control.
- Wider organization: at closure, with a result rather than an intention.
Under-communication and over-communication both fail, differently. Too little and the change arrives as a surprise; too much and the audience filters the channel out, so the one message that mattered is missed with all the others.
Building it in Define
Write the communication plan in the Define phase alongside the charter. Two reasons. First, the audiences for a change need lead time proportional to how much the change affects them, and that lead time has to be scheduled. Second, writing the plan forces the team to identify audiences it had not thought about -- the second-shift supervisor, the internal auditor who signs the SOP, the customer whose incoming inspection expectations will change.
Closing the loop
A plan of broadcast messages cannot tell you whether communication happened. Build in at least one two-way channel per high-stake audience -- a standing agenda item at the shift meeting, a question board at the line, a short pulse question -- and treat silence as a warning rather than as agreement. Every question raised should get an answer with a date, and every suggestion a disposition, even if the disposition is "not this project, and here is why".
Worked example
A team is changing a torque verification step. Communication plan extract:
| Audience | Message type | Medium | Frequency | Owner |
|---|---|---|---|---|
| Assembly operators, all 3 shifts | Instruction + feedback | Shift-start briefing at the station, then laminated standard work | Daily for 2 weeks pre-cutover, then weekly | Line supervisor |
| Maintenance | Instruction | Work order with calibration interval change | Once, 3 weeks ahead | Black Belt |
| Quality engineering | Decision request | Working session | Once, before pilot | Black Belt |
| Sponsor | Decision + risk | Toll-gate brief | Each phase | Black Belt |
| Customer quality representative | Awareness | Formal letter with validation data | Once, before implementation | Quality manager |
A Black Belt announces a change to operators' standard work by sending a detailed email to the shift distribution list two days before cutover. Which element of the communication plan is misapplied?
Which four elements does the ASQ Body of Knowledge name as the components of an effective communication plan?
A team's communication plan consists solely of a weekly status email and a monthly dashboard update. What is the principal weakness?