Study guide

4.5 The 15-Point Project Viability Model & Process-Level Selection

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

4.5 The 15-Point Project Viability Model & Process-Level Selection

Key Takeaways Explain This Topic AI

The CSSC Project Viability Model scores a candidate project against 15 weighted criteria and returns a single number between 1 and 5.

Viability scores below 2.0 mean the project is not viable for DMAIC; 2.0 to 3.0 means possibly viable but requiring further validation; above 3.0 means a viable DMAIC project.

The model tests DMAIC fit only - a low-scoring process may still need improvement, in which case a redesign through DMADV may be the right structure.

Two viability criteria are stated as negatives that reduce a project's attractiveness: a large required cash investment and the need for a complete process redesign.

Enterprise-level selection is leadership's job; departmental leaders select at the process level, often using a Pareto chart to find the target and the selection matrix to validate and prioritize it.

Last updated: September 2026

4.5 The 15-Point Project Viability Model & Process-Level Selection

Quick Summary: Section 4.1 covered project selection generally — the business case, the benefit categories, and the qualitative screens. This section covers the specific instrument CSSC publishes in Chapter 9. The Council does not merely say "score your projects"; it defines a 15-criterion weighted viability model , a six-step arithmetic procedure, and a three-band interpretation key. Because the numbers are published, they are testable, and candidates who only learned generic selection matrices lose these items.

Why CSSC Publishes Its Own Model

Teams can always invent criteria for a homemade selection matrix. The manual states two concrete advantages of using the 15-point viability model instead:

It provides weighting , letting teams make some criteria more important than others. A simple matrix treats "is there a sponsor?" and "will this improve customer satisfaction?" as equals; the viability model does not.

It removes some of the objective nature of the ad-hoc matrix — that is, it replaces one team's improvised scoring scheme with a consistent published instrument, so two departments scoring two projects arrive at comparable numbers.

The 15 Criteria

# Criterion What "yes" means

1 Sponsorship The project is likely to be sponsored at a high level, which increases the chance the team gets the funds and resources it needs.

2 Corporate alignment Project goals align with business goals. Working on unaligned projects reduces business effectiveness.

3 Data Data is available or accessible so the team can design project metrics. Without data, Six Sigma cannot be applied; if data is excessively time-consuming or expensive to collect, the project is usually not the best choice.

4 Definition of defect There is a specific, well-defined defect or problem. Without one, the project risks scope creep.

5 Stability The process is stable and is not expected to be overhauled, redesigned, or changed soon. There is no reason to spend money improving a process about to change anyway.

6 Customer The goal would create a substantial, positive impact on customer satisfaction or perception of quality.

7 Benefits The project has a strong cost-benefit ratio.

8 Timeline The timeline is relatively short. Most Six Sigma improvement projects run around 6 months ; longer timelines reduce the chance the work fits DMAIC.

9 Solution The purpose is to find a solution that is not already known . If the solution is obvious, you do not need a project to find it.

10 Implementation is likely A verified solution is likely to actually be implemented. If change is very unlikely, the improvement work wastes resources.

11 Required investment Stated as a negative: the project requires a large investment of cash. The greater the capital required, the less likely the project is selected or the solution implemented.

12 Available Six Sigma resources The Black and Green Belts the project needs are available.

13 Inputs can be controlled At least some inputs must be within the team's or organization's control. A team cannot improve the quality of a part supplied wholly by a vendor.

14 Redesign Stated as a negative: the process can be improved as-is and does not need a complete redesign.

15 Process quality is improved/maintained The improvement does not negatively affect quality of service or products along the value chain .

Important

Criteria 11 and 14 invert. Every other criterion reads "more is better." Required investment and redesign are framed so that a high requirement is a bad sign. On the scoring sheet these appear as the questions "Would a new solution cost little to no cash?" and "Can the process be improved without a full redesign?" — so a Yes answer is still the favorable one. Candidates who score criterion 11 as "yes, we need a lot of cash" invert the whole result.

The Six-Step Scoring Procedure

Each criterion is phrased as a question, given a weight from 1 to 5 , and answered on a five-point response scale : No (1), Mostly No (2), Possibly (3), Mostly Yes (4), Yes (5).

Assign a weight of 1–5 to each of the 15 questions, reflecting how much that criterion matters to your organization.

Answer each question by placing the question's weight into the appropriate response column — but recorded as a normalized weighted entry rather than the raw weight.

Sum each of the five response columns.

Multiply each column sum by the number at the head of that column (1 for No, 2 for Mostly No, 3 for Possibly, 4 for Mostly Yes, 5 for Yes).

Add the five products together.

Divide that total by the sum of the weighted column totals from step 3. The quotient is the project's viability score.

Worked Calculation — the Manual's Own Example

Suppose the five column sums from step 3 are:

  • Column No (1) Mostly No (2) Possibly (3) Mostly Yes (4) Yes (5)
  • Weighted total 1.3 4.4 4.7 3.3 4.4

Step 3 — sum of all weighted totals: 1.3 + 4.4 + 4.7 + 3.3 + 4.4 = 18.1 1.3 + 4.4 + 4.7 + 3.3 + 4.4 = 18.1 1.3 + 4.4 + 4.7 + 3.3 + 4.4 = 18.1

Step 4 — multiply each column by its response value: 1.3 × 1 = 1.3 4.4 × 2 = 8.8 4.7 × 3 = 14.1 3.3 × 4 = 13.2 4.4 × 5 = 22.0 1.3 \times 1 = 1.3 \qquad 4.4 \times 2 = 8.8 \qquad 4.7 \times 3 = 14.1 \qquad 3.3 \times 4 = 13.2 \qquad 4.4 \times 5 = 22.0 1.3 × 1 = 1.3 4.4 × 2 = 8.8 4.7 × 3 = 14.1 3.3 × 4 = 13.2 4.4 × 5 = 22.0

Step 5 — add the products: 1.3 + 8.8 + 14.1 + 13.2 + 22.0 = 59.4 1.3 + 8.8 + 14.1 + 13.2 + 22.0 = 59.4 1.3 + 8.8 + 14.1 + 13.2 + 22.0 = 59.4

Step 6 — divide by the step-3 total: Viability Score = 59.4 18.1 = 3.28 \text{Viability Score} = \frac{59.4}{18.1} = 3.28 Viability Score = 18.1 59.4 ​ = 3.28

Notice what the arithmetic actually is: a weighted mean of the response values on the 1–5 scale . That is why the output always lands between 1.0 and 5.0 regardless of how many criteria you use, and why the interpretation key can be fixed.

The Viability Key

  • Score DMAIC Viability
  • Below 2.0 Not viable for DMAIC
  • 2.0 to 3.0 Possibly viable , but the organization should validate further
  • Above 3.0 A viable DMAIC project

The worked example's 3.28 therefore clears the bar: it is a viable DMAIC project.

Note

The scope caveat CSSC attaches to its own model. The 15-point matrix determines only whether a project is viable within a DMAIC structure . A process might still need improvement even though it does not fit DMAIC. Where the answer is a redesign, the DMADV structure may let a Six Sigma team approach the improvement instead. A low viability score is a verdict on method fit , not a verdict that the process is fine.

Enterprise-Level versus Process-Level Selection

The manual draws a line that maps directly onto what a Green Belt actually does day to day.

  • Enterprise-Level Selection Process-Level Selection
  • Who Executive leadership and the Six Sigma deployment function Departmental leaders and their teams
  • Scope The portfolio: how many projects to run at once and which ones A few processes the department owns
  • Trigger Strategic goals, enterprise metrics A leader spotting a local improvement opportunity

Typical tools Project viability model, selection matrix, portfolio balancing Pareto chart to find the target, then the selection matrix to validate and prioritize

Typical outcome Chartered project with a Belt assigned Either a proposal to leadership or a small self-run improvement

CSSC is explicit that defining projects at the enterprise level is not the Six Sigma team's job . A department responsible for only a few processes may simply be seeking an improvement. In organizations where Six Sigma is part of the culture, departmental leaders are often familiar with the tools and may be Green or Black Belts themselves; they can bring Six Sigma thinking to their department while carrying non-Six-Sigma daily responsibilities. Some organizations let departmental leaders run smaller versions of projects with guidance from on-staff experts, especially when little capital is required.

Departmental staff can use every tool in the chapter, but they are usually close enough to the situation to identify opportunities without a brainstorming stage . When data already exists, the manual's recommended shortcut is to use a Pareto chart to find where improvement would create results, then use the selection matrix to validate those assumptions and prioritize effort.

Realistic Exam Scenario

A distribution center's operations manager scores three candidate projects. Project A returns 3.6, Project B returns 2.4, and Project C returns 1.7.

The correct reading is not "run A, then B, then C." It is:

Project A (3.6) — above 3.0, a viable DMAIC project. Charter it.

Project B (2.4) — in the 2.0–3.0 band. Possibly viable, but the organization should validate further before committing a Belt. Find out which criteria dragged it down; a low score driven by criterion 12 (Belt availability) is a scheduling problem, while a low score driven by criterion 3 (data) is a fundamental blocker.

Project C (1.7) — below 2.0, not viable for DMAIC . That does not mean the process is healthy. If C scored low because it needs a complete redesign (criterion 14), the right recommendation is to route it to DMADV , not to shelve it.

Common Exam Traps

Trap 1: Treating a low viability score as "no problem here." The score measures DMAIC fit only. A redesign candidate scores badly and still needs work — through DMADV.

Trap 2: Inverting criteria 11 and 14. High cash requirement and a need for full redesign both reduce viability.

Trap 3: Misplacing the band boundaries. Below 2.0 is not viable; 2.0–3.0 needs further validation; above 3.0 is viable. A score of exactly 3.0 sits in the middle band, not the top one.

Trap 4: Forgetting the 6-month timeline norm. Criterion 8 is anchored to the manual's statement that most Six Sigma improvement projects run around six months, and that longer timelines reduce DMAIC fit.

Trap 5: Dividing by 15. Step 6 divides by the sum of the weighted column totals (18.1 in the worked example), not by the number of criteria. Dividing by 15 gives 3.96 and the wrong band interpretation in borderline cases.