Study guide
12.5 Communicating Statistical Results to Business Audiences
CSSC Certified Six Sigma Green Belt Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Six Sigma Overview & Exam Fundamentals
1.1 CSSC Certification Overview, Exam Structure & Body of Knowledge 1.2 History & Evolution of Six Sigma 1.3 Six Sigma Organizational Roles & Belts Hierarchy 1.4 The DMAIC Methodology Architecture vs. DMADV / DFSS 1.5 Other Process Improvement & Quality Methods, and When to Choose Six Sigma
2 Chapter 2: Quality Fundamentals & Defect Metrics
2.1 Critical to Quality (CTQ) Characteristics & VOC Translation 2.2 Defect Metrics: DPU, DPO, DPMO, & the 1.5-Sigma Shift 2.3 First Time Yield (FTY) & Rolled Throughput Yield (RTY) 2.4 Cost of Quality (COQ) & Cost of Poor Quality (COPQ)
3 Chapter 3: Lean Principles & Waste Elimination
3.1 Foundations of Lean & The Toyota Production System (TPS) 3.2 The Eight Wastes: CSSC's Seven Muda, TIMWOODS, and Muri/Mura 3.3 The 5S Visual Workplace Methodology 3.4 Value Stream Mapping (VSM), Cycle Time & Takt Time
4 Chapter 4: Project Selection & Team Management
4.1 Six Sigma Project Selection & Business Case Development 4.2 Project Charter Architecture 4.3 Stakeholder Management & Communication Planning 4.4 Team Dynamics & Tuckman's Team Development Stages 4.5 The 15-Point Project Viability Model & Process-Level Selection
5 Chapter 5: Define Phase & Process Mapping
5.1 High-Level Process Mapping with SIPOC 5.2 Flowcharts, Swimlane Diagrams & Process Value Analysis 5.3 Quality Function Deployment (QFD) & The House of Quality 5.4 Critical to Quality (CTQ) Flowdown & Operational Definitions 5.5 The CSSC Define Toolset: Ground Rules, In/Out of the Box, Is–Is Not & Tollgate Checklists
6 Chapter 6: Measure Phase & Measurement Systems
6.1 Data Types: Continuous (Variable) vs. Discrete (Attribute) Data 6.2 Data Collection Planning & Sampling Strategies 6.3 Measurement System Analysis (MSA) Foundations & Calibration 6.4 Variable & Attribute Gage R&R Studies
7 Chapter 7: Analyze Phase & Root Cause Analysis
7.1 Qualitative Root Cause Tools: 5 Whys & Cause-and-Effect (Fishbone) Diagrams 7.2 Failure Mode and Effects Analysis (FMEA) & RPN Calculation 7.3 Pareto Analysis & The 80/20 Rule 7.4 Graphical Data Exploration: Histograms, Box Plots, & Multi-Vari Charts 7.5 The Root Cause Verification Matrix
8 Chapter 8: Descriptive Statistics & Distributions
8.1 Measures of Central Tendency & Dispersion 8.2 The Normal Distribution & The Empirical Rule (68-95-99.7) 8.3 Standard Normal Distribution, Z-Scores & Probability Calculations 8.4 Common Non-Normal Distributions: Binomial, Poisson & Chi-Square
9 Chapter 9: Inferential Statistics & Hypothesis Testing
9.1 Fundamentals of Hypothesis Testing: Null vs. Alternative, Alpha & Beta Risks 9.2 One-Sample and Two-Sample t-Tests for Means 9.3 Paired t-Tests & Non-Parametric Alternatives 9.4 Analysis of Variance (One-Way & Two-Way ANOVA) & Chi-Square Contingency Tests 9.5 Sample Size Determination for Hypothesis Tests
10 Chapter 10: Correlation, Regression, & Experimentation
10.1 Linear Correlation & Pearson's Correlation Coefficient (r) 10.2 Simple Linear Regression & Coefficient of Determination (R^2) 10.3 Introduction to Design of Experiments (DOE) & Factorial Designs 10.4 Analyzing Experimental Results: Main Effects & Interaction Plots
11 Chapter 11: Improve Phase & Solution Implementation
11.1 Brainstorming, Creative Thinking & Solution Selection Matrices 11.2 Piloting Solutions & Conducting Risk Assessments 11.3 Implementation Planning & Change Management (ADKAR) 11.4 Mistake-Proofing (Poka-Yoke) & Standard Work
12 Chapter 12: Control Phase, SPC, & Process Capability
12.1 Statistical Process Control (SPC) & Shewhart Control Rules 12.2 Variable Control Charts: I-MR, X-bar & R, X-bar & S 12.3 Attribute Control Charts: p, np, c, and u Charts 12.4 Process Capability & Performance Indices: Cp, Cpk, Pp, Ppk 12.5 Communicating Statistical Results to Business Audiences
12.5 Communicating Statistical Results to Business Audiences
Key Takeaways Explain This Topic AI
CSSC names four obstacles to presenting statistical analysis: most of the audience does not care about the method, they lack the analyst's statistical background, the discussion gets derailed into statistics, and presenters include too much information.
Statistics belong in the presentation because they are what give conclusions and results credibility - the answer is to translate them, never to omit them.
The published inclusion test is whether an item relates to the problem statement or to a solution for it; if it does not, it probably does not belong in a general business presentation.
For statistically literate audiences, move analysis, data tables, and Minitab output into a presentation appendix that can be displayed on demand.
The five business-friendly presentation tips are: understand the target audience, tell a story with text and images, be clear and concise, do not misuse your tools, and do not let the presentation drive the project.
Last updated: September 2026
12.5 Communicating Statistical Results to Business Audiences
Quick Summary: This is the final chapter of the CSSC Green Belt Body of Knowledge, and it deliberately steps back from the mathematics of Units 4 and 5. The manual's own framing: the more you learn about statistical analysis, the easier it is to get caught up in the challenge of the analysis and forget that the business is relying on you for answers about its own challenges . Every tollgate, every sign-off, and every funded improvement in a DMAIC project depends on somebody non-technical being persuaded. That makes this chapter a skills chapter, not an afterthought.
- The Four Obstacles
- Obstacle 1: Most people do not care about the method
CSSC states it bluntly. Unless your sponsor is a Six Sigma expert or your leadership committee is well-versed in Six Sigma methods, the people you are presenting to do not care which hypothesis test you used, or what your Chi-Square statistic or p-value was.
Read that precisely, because the exam does. It does not say business leaders are indifferent to your findings. They care a great deal about the conclusions and results of your analysis, and about the results of the project as a whole. What they do not care about is the machinery. The presenter's task is to present the information in a way that ties in with what they care about and does not rely solely on statistical concepts and language.
Obstacle 2: The audience lacks your statistical background
General business staff and leaders are unlikely to understand statistical analysis the way a Six Sigma expert does. That leaves the presenter delivering data whose backing may not be understood. You must be able to explain why the team chose to move in a certain direction or how you know a process has improved — because not everyone will simply take your word that the p-value was appropriate for the decision you made.
Obstacle 3: Getting derailed by the statistics
This happens two ways, and they need opposite responses.
A statistically literate audience member hijacks the discussion. A sponsor or Black Belt in the room starts asking statistical rather than business questions: Why did you use the 1-Proportion test? How did you choose the sample size? Do you really think a beta of 0.2 is sufficient, or should you have gone with 0.1?
CSSC's judgment on these is nuanced. Some are valid — "how did you choose the sample size?" may be worth covering so the audience understands what assumptions the team made and what risks it accepted. But once the analysis is done and decisions have been made on the basis of it, whether the power was set correctly is a moot point . The published preventive measure is structural: keep a Six Sigma-knowledgeable sponsor in the loop throughout the project , so they can give that input in real time rather than at the tollgate.
The audience does not understand the statistics, so the presentation becomes a statistics lesson. The remedy is to walk a line: educate on what is necessary to follow the Six Sigma process, without delivering an in-depth discussion of statistical analysis. CSSC's calibration is concrete — you probably should ensure the audience understands what standard deviation is and why it matters; you probably do not need to explain all the types of hypothesis tests, or in some cases even mention that you used one.
Obstacle 4: Too much information
The temptation is familiar: you have a box plot, a bar graph, a pie chart, a hypothesis test, and several probability-distribution calculations. They all look good and each says something slightly different. Surely they should all go in?
Wrong. Too many ways of illustrating the data overwhelms the audience . Worse, most people in the business will not see the nuances a trained Six Sigma expert sees — so from their perspective you are showing the same data over and over. It is not an effective use of presentation space or meeting time.
Why Statistics Stay In
Given all four obstacles, why not drop the statistics entirely? Because statistics are what give your conclusions and results credibility. Whether you are presenting at a Measure or Analyze tollgate or seeking final approval on improvements, the numbers are the warrant for the recommendation. The answer is translation, not omission.
The Problem-Statement Test
CSSC gives one decision rule for what goes in the deck, and it is worth committing to memory because it doubles as an exam answer.
Because a real Six Sigma team is already rooted in business terms, the problem statement — which combines statistical concepts with business goals and needs — is a good reference point for anyone presenting throughout and after a DMAIC project. So:
If you are not sure whether something should be included, ask: does it relate to the problem statement, or to a solution for the problem statement? If not, it probably does not need to be communicated in a general business environment.
The manual pairs this with a warning about a specific professional failure mode: as you work with data, you may be surprised how much your interest in the numbers grows . That interest leads to valuable discoveries — but you must avoid the temptation to include data or conclusions in a presentation simply because you find them interesting or "cool."
- Tailoring to the Audience
- The invested, statistically literate audience
Consider a Black Belt presenting at an Improve tollgate to a leadership team that includes the sponsor and two other Black Belts, perhaps a Master Black Belt. This audience is both invested and capable of following the statistical reasoning.
That does not mean including all your data — your audience is also busy . But it does mean you should anticipate a few methodology questions and can incorporate technical terms and results without stopping to explain them .
The appendix technique. For this audience, CSSC's specific recommendation is to build a presentation appendix holding your analysis, data tables, and even specific Minitab output, where it can be displayed quickly if a question calls for it . The main deck stays business-facing; the evidence stays one click away. This matters most in high-cost or high-risk situations , where leadership is more likely to want the background analysis because they need to fully understand all assumptions and risks before deciding on the recommended improvements.
The uninvested or non-technical audience
Presenting to general management, or explaining changes to frontline staff in a department, calls for a different build: heavier on what changes and why it helps, far lighter on method.
- Invested + statistically literate Uninvested or non-technical
- Technical terms Use without explanation Define only what is unavoidable
- Analysis depth in main deck Summary plus key results Conclusion and business impact
- Appendix Essential — data tables, Minitab output Usually unnecessary
- Expect Methodology and assumption questions "What does this mean for my job?"
- Risk to manage Derailment into statistical debate Turning the meeting into a statistics lesson
- The Five Presentation Tips
CSSC lists five techniques for creating viable business presentations from statistical work.
Understand the target audience. Tailor the information to the audience's level of concern and knowledge, as above.
Tell a story with text and images. A narrative structure — the problem, what the data showed, what the team did, what changed — carries a business audience through material that a table of results cannot.
Be clear and concise. Keep things short and simple; this is the direct countermeasure to Obstacle 4.
Do not misuse your tools. Avoid misuse of technology, presentation, or statistical tools — including chart types that distort the data and slide effects that distract from it.
Do not let the presentation drive the project. The project's purpose is improving a business process. If work is being done, or evidence framed, to make a slide land rather than to answer the business question, the tail is wagging the dog.
Realistic Exam Scenario
A Green Belt has finished the Control phase of a warehouse picking project. Cpk rose from 0.87 to 1.42, a two-sample proportion test confirmed the mis-pick reduction at p = 0.003, and the I-MR chart has been stable for eleven weeks. She must present twice: first to an executive steering committee approving a rollout to four more sites, then to the warehouse floor staff.
Executive deck. Lead with business impact — mis-picks down 61%, an annualized $340,000 in avoided rework and expedited freight, sustained over eleven weeks. Keep the control chart, because it visually proves sustainment, and keep one sentence establishing that the improvement was statistically confirmed rather than luck. Push the proportion test output, the Gage R&R study, and the capability calculations into the appendix — this is a high-cost decision, so leadership may well ask for the assumptions, and the appendix has them ready.
Floor deck. No p-values, no Cpk. The story is: here is the error that used to happen, here is what changed about the pick sequence, here is how we will know if it drifts back, and here is who to tell. Standard deviation might earn a sentence if the monitoring chart is going up on the wall; the hypothesis test will not.
Same project, same evidence, two builds. Applying the problem-statement test to each is what produces the difference.
Common Exam Traps
Trap 1: Reading "most people don't care" as "leaders don't care about results." They care intensely about conclusions, results, and project outcomes. They do not care which test produced them.
Trap 2: Removing statistics to simplify. Statistics are what give conclusions credibility. Translate, do not delete.
Trap 3: Answering every methodology question in the main session. Some are valid — sample size and accepted risk may be worth covering. Debating whether power should have been 0.9 after decisions are already made is moot. The published fix is keeping a knowledgeable sponsor engaged throughout.
Trap 4: Showing every chart you built. Multiple views of the same data read as repetition to a business audience and waste meeting time.
Trap 5: Skipping the appendix for a high-risk decision. High-cost, high-risk proposals are exactly where leadership wants the background analysis available on demand.
Trap 6: Including a finding because it is interesting. The test is relevance to the problem statement or its solution — not analyst enthusiasm.