4.6 Team Communication Plans

ASQ Certified Six Sigma Black Belt CSSBB

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & CSSBB Exam Strategy

1.1 CSSBB Exam Format, Scoring, and Testing Windows 1.2 Eligibility, Project Affidavits, Application, and Recertification 1.3 Open-Book Strategy, Reference Materials, and a 16-Week Study Plan

2 Chapter 2: Organization-Wide Planning and Deployment

2.1 Fundamentals of Six Sigma and Lean Methodologies 2.2 Selecting the Right Methodology: DMAIC, DFSS, and Lean 2.3 Business Systems, Processes, and Stakeholder Relationships 2.4 Strategic Planning and Deployment of Six Sigma Initiatives 2.5 Six Sigma Roles and Responsibilities 2.6 Organizational Barriers and Common Causes of Six Sigma Failure 2.7 Change Management: Stakeholder Analysis, Readiness, and Communication

3 Chapter 3: Organizational Process Management and Measures

3.1 Impact of Six Sigma Projects on Customers, Suppliers, and Stakeholders 3.2 Benchmarking Types and Performance Goal Setting 3.3 Performance Measures: Balanced Scorecard, KPIs, KBIs, OKRs, and Line of Sight 3.4 Leading and Lagging Indicators and Performance Dashboards 3.5 Financial Measures: Revenue Growth, Margin, NPV, ROI, and Cost-Benefit Analysis 3.6 Cost of Poor Quality and Hard versus Soft Savings

4 Chapter 4: Team Management

4.1 Team Types and Constraints 4.2 Team Roles, Responsibilities, and Member Selection 4.3 Team Success Factors and Ground Rules 4.4 Motivational Techniques and Overcoming Demotivators 4.5 Stages of Team Development and Conflict Resolution 4.6 Team Communication Plans 4.7 Team Leadership Models: Direct, Coach, Support, and Delegate 4.8 Group Behaviors, Conflict Resolution, and Meeting Management 4.9 Facilitation Techniques and Team Decision-Making Methods 4.10 Team Training: Needs Assessment, Delivery, and Evaluation

5 Chapter 5: Define Phase

5.1 Customer Identification and Segmentation 5.2 Customer Data Collection: Methods, Validity, and Reliability 5.3 Customer Requirements: CTX, CTQ Trees, and Operational Definitions 5.4 The Kano Model and Quality Function Deployment 5.5 SIPOC and Process Mapping 5.6 Business Case Justification 5.7 The Project Charter and the Problem Statement 5.8 Project Scope and Boundaries 5.9 SMART Goals and Project Performance Measurements 5.10 Project Charter Reviews and Toll-Gate Governance 5.11 Project Management Tools: Gantt Charts, Toll-Gate Reviews, WBS, and RACI 5.12 Analytical Tools Used Throughout the DMAIC Cycle

6 Chapter 6: Measure Phase

6.1 Process Flow Metrics and the Hidden Factory 6.2 Process Analysis Tools and Value Stream Mapping 6.3 Types of Data and Measurement Scales 6.4 Sampling Concepts, Methods, and Sample Size for Estimation 6.5 Data Collection Plans and Common Pitfalls 6.6 Gage R&R for Variable Measurement Systems 6.7 Attribute Agreement Analysis and Audit MSA 6.8 Measurement Systems Across the Organization, and Metrology 6.9 Population Parameters, Sample Statistics, and Valid Statistical Conclusions 6.10 Descriptive Statistics: Central Tendency, Dispersion, and Shape 6.11 Graphical Methods for Exploratory Data Analysis 6.12 Probability Concepts, Common Distributions, and the Central Limit Theorem 6.13 Additional Distributions: Hypergeometric, Exponential, Lognormal, Weibull, and Bivariate 6.14 Process Capability and Performance Indices 6.15 Capability Studies, Attributes Capability, Yield Metrics, and Long-Term Capability

7 Chapter 7: Analyze Phase

7.1 The Correlation Coefficient, Its Confidence Interval, and Causation 7.2 Linear Regression and Residual Analysis 7.3 Multivariate Tools: Factor Analysis, Discriminant Analysis, and MANOVA 7.4 Hypothesis Testing Terminology, Errors, and Single-Sample Tests 7.5 Statistical Versus Practical Significance 7.6 Sample Size for Hypothesis Tests 7.7 Point Estimates, Confidence, Prediction, and Tolerance Intervals 7.8 Tests for Means, Variances, and Proportions 7.9 Analysis of Variance 7.10 Chi-Square Goodness-of-Fit and Tests of Independence 7.11 Types of Risk and Failure Mode and Effects Analysis 7.12 Gap Analysis and Root Cause Analysis 7.13 Waste Analysis: The Seven Classic Wastes and Resource Under-Utilization

8 Chapter 8: Improve Phase

8.1 Design of Experiments: Objectives, Terminology, and Effects 8.2 DOE Design Principles: Randomization, Blocking, Replication, and Resolution 8.3 Planning and Evaluating Designed Experiments 8.4 One-Factor Experiments: Completely Randomized, Randomized Block, and Latin Square Designs 8.5 Full Factorial Experiments and Design Selection 8.6 Two-Level Fractional Factorial Experiments and Confounding 8.7 Response Surface Methodology and Optimization 8.8 Waste Elimination: Pull Systems, Kanban, 5S, and Poka-Yoke 8.9 Cycle-Time Reduction: Continuous Flow, SMED, and Heijunka 8.10 Kaizen, Kaizen Blitz, Theory of Constraints, and OEE 8.11 Implementation Planning, Piloting, and Solution Selection

9 Chapter 9: Control Phase

9.1 SPC Objectives, Variable Selection, and Rational Subgrouping 9.2 Control Charts for Variables Data 9.3 Control Charts for Attributes Data 9.4 Short-Run SPC and Moving Average Charts 9.5 Control Chart Analysis: Common Cause, Special Cause, and Run Rules 9.6 Total Productive Maintenance and Visual Controls 9.7 Measurement System Reanalysis 9.8 Control Plan Development and Process Owner Handoff 9.9 Lessons Learned, Documentation, and Training for Sustainment 9.10 Ongoing Evaluation of the Improved Process

10 Chapter 10: Design for Six Sigma (DFSS)

10.1 DFSS Frameworks: DMADV, DMADOV, and Design Transfer 10.2 Design for X (DFX) 10.3 Robust Design, Parameter Design, and Verification 10.4 Tolerance Design and Statistical Tolerancing

4.6 Team Communication Plans

Key Takeaways Explain This Topic AI

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.

Last updated: August 2026

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
• Email 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