Team Communication
Key Takeaways
- Effective project communication covers both internal team coordination and external stakeholder updates with audience-appropriate detail.
- Progress reports should tie status to charter goals, metrics, risks, decisions needed, and next steps—not only activity lists.
- Tollgates and formal reviews create structured decision points with the champion and process owner.
- Choose channel and frequency by stakeholder influence/interest: manage closely vs inform lightly.
- BoK II.F.4 is Apply level: select communication content, cadence, and audience for Green Belt project scenarios.
Team Communication (CSSGB BoK II.F.4 — Apply)
Quick Answer: Communicate inside the team for coordination and learning, and to stakeholders for decisions, support, and transparency. Use agendas, visual management, and progress reports that link work to charter metrics, risks, and asks. Use reviews/tollgates as formal decision points—not slide theater.
BoK II.F.4 is Apply. Strong analysis dies in silence: sponsors disengage, process owners are surprised at Control, and team members duplicate work. Green Belts plan communication as deliberately as they plan data collection.
Two Audiences, Two Jobs
| Audience | Primary job of communication | Typical content |
|---|---|---|
| Core team | Align tasks, surface blockers, share learning | Working data, detailed plans, action logs, method debates |
| Stakeholders (champion, process owner, adjacent leaders, customers as needed) | Enable decisions, maintain support, manage expectations | Status vs goals, risks, resource needs, go/no-go recommendations |
Exam trap: Sending the champion a 40-page Minitab dump weekly. Executives need decision-ready summaries; the team needs the detail. Tailor depth to audience.
Communication Within the Team
Cadence and rituals
- Kickoff: charter, roles, RACI, ground rules, meeting rhythm
- Working meetings: timeboxed agenda, decisions, owners, due dates
- Stand-ups or huddles (short): what moved, what is blocked, help needed
- Gemba communication: talk at the process, not only in conference rooms
- Shared repository: charter, SIPOC, data dictionary, action tracker, latest charts
Meeting hygiene that supports dynamics
Good communication prevents floundering and tangents:
- Purpose and desired decisions stated up front
- Roles: facilitator, timekeeper, scribe
- Parking lot for off-topic items
- End with who / what / when action review
- Publish notes within a day
When conflict is high, use structured tools (NGT) and a neutral facilitator so communication stays about the process, not personalities.
Listening and feedback
Apply-level communication is two-way. Green Belts:
- Paraphrase process experts before jumping to tools
- Separate advocacy (“I recommend X”) from inquiry (“what am I missing?”)
- Give feedback on behaviors that help or hurt team norms (II.F.1)
- Escalate facts early—bad news ages poorly
Communication to Stakeholders
Stakeholder maps (influence/interest) drive who gets what:
| Stakeholder type | Frequency | Channel examples | Focus |
|---|---|---|---|
| Champion / sponsor | Tollgates + exception alerts | Face-to-face or video review; one-page status | Decisions, barriers, benefits |
| Process owner | Weekly or biweekly working touch | Huddle + shared tracker | Operational impact, pilot design, sustainment |
| Extended stakeholders | Milestone updates | Email brief, town hall, dashboard | “What changed for you” |
| Customers (if VOC-critical) | At Define and validation points | Interview summary, pilot feedback | CTQ confirmation |
Never surprise a high-influence stakeholder at a final tollgate with a scope they never saw.
Progress Reports
A useful progress report answers: Are we on track to the charter? What did we learn? What is at risk? What do we need?
Recommended skeleton
- Project identity — name, belt, champion, process owner, phase, date
- Goal reminder — problem statement and primary metric target
- Status snapshot — Green/Yellow/Red against schedule, scope, benefits
- Metric trend — baseline vs current (even if incomplete)
- Accomplishments since last report — outcomes, not only meetings held
- Plans next period — concrete deliverables
- Risks and issues — with owners and due dates
- Decisions / help needed — explicit asks for the champion
Weak report: “Held three meetings and pulled some data.”
Strong report: “Baseline DPMO = 12,400 (n=2,100 units). MSA shows 28% GR&R—Measure gate at risk. Request: approve gage improvement week before Analyze tollgate.”
Link reports to the project plan (Gantt/WBS) so schedule claims are checkable.
Reviews and Tollgates
Tollgates (phase reviews) are formal communication events. The team presents evidence that exit criteria for Define, Measure, Analyze, Improve, or Control are met; the champion (and often process owner / MBB) approves, recycles, or kills the project.
Tollgate communication standards
- Start with the business problem and CTQs, not tool nostalgia
- Show data quality and sample rationale when claiming baseline or effects
- Present alternatives considered (anti-groupthink signal)
- State residual risks and control plan ownership for late phases
- End with a clear decision request
Between tollgates, lightweight reviews with the process owner keep operational reality aligned with analysis. MBBs may review tool correctness before the champion sees a polished story.
Choosing Channels
| Need | Prefer |
|---|---|
| Complex conflict or barrier removal | Synchronous conversation |
| Decision record and portfolio tracking | Written status + tollgate minutes |
| Shop-floor awareness | Visual board, huddle, brief demos |
| Wide FYI | Dashboard, newsletter, short video |
| Sensitive personnel issues | Private one-on-one—not group email |
Over-reliance on email for contentious issues worsens feuding; over-reliance on meetings without notes causes rework.
Common Failures
| Failure | Fix |
|---|---|
| Activity reporting without metrics | Lead with CTQ and project Y |
| Hidden risks until the last week | Risk log in every progress report |
| Team-only jargon with executives | Translate to cost, risk, customer impact |
| No feedback loop from operators | Gemba reviews during pilots |
| Communication ends at celebrate | Adjourning plan: who gets final docs and training |
Exam Focus
- Distinguish team vs stakeholder messaging
- Progress reports need status, metrics, risks, asks—not only calendars
- Tollgates are decision forums with evidence, not optional slide shows
- Match frequency and depth to influence/interest
- Bad news early is good communication; silence is a project risk
Apply these habits and II.F.4 becomes practical leadership: the Green Belt keeps people aligned so DMAIC tools can create results that last.
A champion asks for a weekly update. Which progress report content best supports decision-making?
The team finishes Measure and schedules a formal review with the champion and process owner to approve moving to Analyze. What is this communication event primarily designed to do?