Organizational Communication

Organizational Communication (CSSGB BoK II.E.2 — Apply)

Quick Answer: Improvement projects fail as often from communication gaps as from weak statistics. Top-down messaging aligns strategy, authority, and resources. Bottom-up feedback brings Gemba truth and early warning. Horizontal communication syncs cross-functional partners who share the process. Green Belts plan all three directions—who needs what information, when, and through which channel.

BoK II.E.2 is at the Apply level: choose the right communication direction and practice for a project situation, and recognize failure modes when one direction is missing.

Communication as a Business Result Enabler

Section II.E pairs process performance metrics with communication because metrics only drive results when people understand them, act on them, and sustain them. A perfect DPMO chart that never reaches the process owner, or a pilot schedule that never reaches adjacent departments, will not stick.

Organizational communication in Six Sigma is not “more email.” It is intentional flow of decisions, data, risks, and changes among sponsors, teams, process participants, and customers of the process.

Three Directions of Organizational Communication

Healthy projects use all three. Over-reliance on any single channel creates blind spots.

Top-Down Communication

Top-down communication carries authority and organizational intent. Champions and deployment leaders must visibly support projects: why this problem matters, what success looks like, which resources are authorized, and what trade-offs are acceptable.

Green Belt applications:

• Kickoff messages from the Champion clarifying project priority over local firefighting
• Tollgate expectations and decision rights (who approves scope changes)
• Cascading strategic metrics so the project Y links to scorecard KPIs
• Control-phase endorsement when new standard work becomes “the way we work”

Failure mode: Silent sponsorship. If leaders never reinforce the project, middle managers deprioritize data collection and pilots. The Green Belt cannot fully substitute for missing top-down cover—but must escalate the gap.

Best practices: Short, consistent messages; link project goals to strategy; announce decisions after tollgates so rumors do not fill the void; thank contributors publicly to reinforce desired behaviors.

Bottom-Up Communication

Bottom-up communication moves information from people closest to the work upward to decision makers. It is how organizations learn what dashboards miss.

Green Belt applications:

• Gemba interviews and structured feedback during Measure
• Operator input on failure modes before FMEA scores are finalized
• Pilot feedback loops: what worked, what was unworkable, what metrics felt wrong
• Escalation of safety, quality, or customer risks discovered mid-project

Failure mode: “Shot messenger” culture. If staff are punished for bad news, RTY and CoPQ problems hide until they explode. Teams then present only polished tollgate slides.

Best practices: Ask specific questions (“Where does rework actually start?”) rather than “Any concerns?”; close the loop—tell the floor what changed because of their input; protect anonymity when needed; convert anecdotes into data without dismissing the anecdote.

Exam tip: Bottom-up is not insubordination; it is process truth. Items that describe ignoring front-line barriers while forcing a solution describe failed bottom-up listening.

Horizontal (Lateral) Communication

Most value streams cut across functions: Sales → Order Entry → Production → Logistics → Finance. Horizontal communication coordinates peers who do not report to each other but share process outcomes.

Green Belt applications:

• SIPOC supplier/customer conversations between departments
• Joint review of handoff defects that inflate DPU at the next step
• Aligning definitions of “complete order” or “on-time” across teams
• Change-management notices when Improve alters an upstream or downstream process
• Shared visual management or huddles for multi-department control plans

Failure mode: Local optimization. Each silo hits its own KPI while RTY collapses at interfaces. Horizontal silence is a classic root of suboptimization.

Best practices: Name interface owners; publish shared operational definitions; invite adjacent functions to relevant tollgates; use RACI so handoffs are explicit; schedule brief cross-functional stand-ups during pilots.

Matching Direction to Project Moments

Designing a Simple Communication Plan

For each audience, document:

1. Audience — Champion, process owner, operators, adjacent managers, customers
2. Purpose — Decide, inform, request data, train, celebrate
3. Message — One primary point per touch (status, risk, decision needed)
4. Channel — Huddle, email, dashboard, town hall, one-on-one, visual board
5. Frequency — Daily during pilot; weekly team; tollgate cadence for sponsors
6. Owner — Who sends it (Green Belt, process owner, Champion)

Example: During a pilot reducing invoice field defects (DPMO focus), the Green Belt runs a 10-minute morning huddle (horizontal + bottom-up), sends a Friday metric snapshot to the process owner (upward), and asks the Champion to announce the new checklist as mandatory in the Monday ops meeting (top-down).

Barriers and How Green Belts Counter Them

Linking Communication to Metrics and Tools

• Present RTY/DPU/CoPQ top-down so leaders fund the right scope.
• Use bottom-up stories plus data to keep VOC honest.
• Resolve horizontal definition fights with operational definitions and matrix diagrams of CTQ × process step ownership.
• Use PDPC and activity networks as communication artifacts—not only planning tools—so everyone sees risks and sequence.

Exam and Practice Takeaways

• Identify whether a scenario needs direction-setting (top-down), process truth (bottom-up), or cross-silo sync (horizontal).
• Strong Green Belts orchestrate communication; they do not assume “the data will speak for itself.”
• Communication plans are living documents—update them when scope, pilot timing, or stakeholders change.
• Business results stick when metrics, process changes, and multi-directional communication travel together into Control.

Apply the three directions deliberately on every project: authority from above, reality from below, and coordination across the value stream.