5.6 Business Case Justification

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

5.6 Business Case Justification

Key Takeaways Explain This Topic AI

A business case links the strategic objective, the measured process gap, the financial consequence, the cost of inaction, and the resources requested.

The problem statement describes what is wrong; the business case describes why the organization should care enough to fund the fix.

Estimated benefit at Define is an order-of-magnitude figure that must be agreed with finance and refined at each toll gate.

The cost of inaction is what separates a real business case from a proposal, because doing nothing is always an option.

A business case that cannot name the strategic objective it serves indicates a project selected bottom-up without line of sight.

Last updated: August 2026

• What a business case is for
• Black Belt capacity is the scarcest resource in a Six Sigma deployment. A full-time Black Belt
• completes perhaps four to six projects a year, so chartering one project means declining others. The

business case is the argument that this problem deserves that capacity.

• It is distinct from the problem statement. The problem statement says what is wrong, where, since
• when, and how big it is. The business case says why it matters to the organization and what

happens if nothing is done.

The five components

• Component Question Failure if weak
• Strategic linkage Which organizational objective does this serve? Bottom-up project with no sponsor interest

Process gap What is the measured difference between current and required performance? Anecdotal justification that collapses under scrutiny

• Financial consequence What is this gap costing, in what accounting category? Benefit disputed at closure
• Cost of inaction What happens if we do nothing, and when? No urgency; project deprioritized indefinitely

Resource request What is needed: belt time, SME hours, capital, data access? Approved project that cannot be executed

• Strategic linkage
• Every project should be traceable to a stated objective -- a balanced scorecard measure, an annual
• operating plan target, a regulatory commitment, or a customer escalation. If the team cannot name the
• objective, the project was selected because the problem was visible rather than because it was

important, and it will lose sponsor attention the moment something else becomes visible.

Process gap

State it in the metric that the objective uses, with a baseline period and a sample size:

First-pass yield on the moulding line averaged 91.4% over the 26 weeks ending 30 June (n = 1.18

million parts) against an operating plan requirement of 97.0%.

• Financial consequence
• Translate the gap into money using the categories from the cost of poor quality model, and label each

figure hard or soft:

• Element Basis Annual value Type
• Scrap material and conversion 4.2% x 1.2 M parts x $2.85 $143,640 Hard
• Rework labour 1.1% x 1.2 M x $1.40 $18,480 Hard
• Premium freight to cover shortfalls Actual paid, 12 months $46,000 Hard
• Capacity consumed producing scrap 620 machine hours $71,300 Soft
• Total identified $279,420
• Two disciplines: agree the calculation basis with finance now , and separate hard from soft so the

approving executive is not surprised at closure.

• Cost of inaction
• Doing nothing is always an available option, and a business case that does not address it is
• incomplete. Cost of inaction has three usual forms: the recurring cost continues and compounds; a
• threshold is approaching (a customer audit, a capacity constraint, a regulatory deadline); or an

opportunity closes (a contract renewal, a launch window).

• Resource request
• Be specific and current: Black Belt allocation, SME hours by function, data access, capital band, and
• any external cost. An approved project with unfunded resources is the most common form of apparent

management support that is not real support.

• Estimating benefit at Define without over-claiming
• At Define you have a gap, not a solution, so the benefit estimate is an order of magnitude. Three

conventions keep it honest:

• Estimate the achievable fraction of the gap, not the whole gap. Committing to eliminate 100% of
• a loss before root causes are known is a charter written to fail; 50% to 70% is a defensible opening

position.

State the estimate as a range with an accuracy class , for example "$120k-$180k, Define-phase

estimate, plus or minus 50%", and tighten it at each toll gate.

Never book the benefit in Define. Financial validation belongs in Control, signed by finance.

• Project selection screens
• Business cases are compared, not evaluated in isolation. Common screens applied by a project selection

committee:

Strategic fit : is it linked to a stated objective?

Financial size : does the estimated benefit exceed the deployment's threshold?

Feasibility : is the data available, is the process stable enough to study, is the scope bounded?

Cycle time : can it be completed in four to six months?

Risk : what is the consequence if it fails or is abandoned?

Sponsor commitment : is there a sponsor with authority over the whole process?

• Projects that fail the feasibility or sponsor screens should be rejected outright rather than
• chartered optimistically. A project with a large benefit and no data is not a Six Sigma project; it is

a data collection project that may become one.

• Worked example
• Business case. On-time in-full delivery to fleet customers has averaged 87.3% for the last three
• quarters against the annual operating plan target of 96%, and the shortfall is concentrated in the
• two accounts that represent 41% of segment revenue. The performance gap is currently costing an
• estimated $310,000 per year in expedited freight, service credits, and rework of incorrect
• shipments, of which approximately $240,000 is hard cost recognized in the freight and credits
• accounts. Both accounts are up for renewal in Q3, and the larger has cited delivery reliability in
• its most recent quarterly review, so the cost of inaction includes the risk of losing $4.2 million
• of annual revenue. The project requests one Black Belt at full allocation for five months, 120 hours
• of logistics and planning subject-matter expert time, access to the transportation management system

data, and a pre-approved capital band of $75,000.

That case names the objective, quantifies the gap, separates hard from soft, makes the cost of inaction

concrete and dated, and states exactly what it needs.