Study guide
Organizational Goals & Six Sigma Projects
ASQ Certified Six Sigma Green Belt CSSGB
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
CSSGB Exam Facts & Logistics How to Study for an Open-Book ASQ Exam
2 Six Sigma Foundations
Value of Six Sigma & Quality Leaders Organizational Goals & Six Sigma Projects Organizational Drivers, KPIs & Scorecards
3 Lean Principles in the Organization
Lean Concepts Value Stream Mapping & Waste
4 Design for Six Sigma
DFSS Road Maps: DMADV & IDOV FMEA Basics & Risk Priority Number Design FMEA vs Process FMEA
5 Define: Project Identification
Project Selection & DMAIC Fit Process Elements & Boundaries Benchmarking Types SIPOC & Process Inputs/Outputs
6 Stakeholders & Voice of the Customer
Owners & Stakeholders Customer Identification Customer Data Collection CTQ, QFD & Kano
7 Project Management Core
Agile & Top-Down Project Methods Project Charter & Problem Statements Project Scope Tools Primary & Consequential Metrics
8 Planning, Risk & Closure
WBS, Gantt, CPM, PERT & Tollgates Project Documentation Project Risk Analysis & Management Project Closure & Lessons Learned
9 Management Tools & Business Results
Eight Management & Planning Tools DPU, RTY, CoPQ, DPMO & Sigma Level Organizational Communication
10 Team Dynamics & Performance
Team Stages & Negative Dynamics Six Sigma Roles & RACI Brainstorming, NGT & Multivoting Team Communication
11 Measure: Process & Probability
Process Maps & Documentation Basic Probability Concepts Central Limit Theorem
12 Distributions & Data Collection
Statistical Distributions Data Types & Measurement Scales Sampling & Data Collection Plans Descriptive Statistics
13 Graphical Methods & MSA
Graphical Methods Measurement System Analysis & Gage R&R Bias, Linearity, Stability & P/T
14 Process & Performance Capability
Process Performance vs Specifications Process Capability Studies Cp, Cpk, Pp, Ppk & Cpm Short-Term vs Long-Term Capability & Sigma Shift
15 Analyze: Exploratory Data Analysis
Multi-Vari Studies Correlation & Linear Regression
16 Hypothesis Testing
Hypothesis Testing Basics Tests for Means, Variances & Proportions
17 Gap & Root Cause Analysis
Gap Analysis Root Cause Analysis Tools
18 Design of Experiments
DoE Basic Terms Main Effects & Interaction Plots
19 Implementation Planning & Lean Tools
Implementation Planning & Pilots Waste Elimination Tools Cycle-Time Reduction & SMED Kaizen & Kaizen Blitz
20 Statistical Process Control
SPC Basics: Common vs Special Cause Rational Subgrouping Control Chart Selection & Construction
21 Sustaining Improvements & Lean Control
Control Plans Document Control, Training & Audits Plan-Do-Check-Act (PDCA) TPM & Visual Factory
Organizational Goals & Six Sigma Projects
Key Takeaways Explain This Topic AI
Every Green Belt project Y should trace upward to an organizational or business-unit goal; orphan projects consume capacity without strategic return.
SMART goals are Specific, Measurable, Achievable, Relevant, and Time-bound—and they belong in the project charter baseline and target.
Strategy cascades through inputs, outputs, and feedback loops across enterprise, process, and project levels so local metrics stay aligned.
Primary metrics track the problem you intend to fix; consequential (secondary) metrics guard against improving Y while harming customers, cost, or safety.
Champions and process owners own goal linkage; Green Belts translate those goals into scoped DMAIC work with clear success criteria.
Last updated: July 2026
Organizational Goals & Six Sigma Projects
Quick Answer: Green Belt projects must connect a local process metric (the project Y) to a higher-level organizational goal. Use SMART goal statements in the charter, cascade strategy through inputs/outputs/feedback across levels, and track both primary and consequential metrics so improvements help the business without creating new harm.
Why Linkage Matters
A technically excellent DMAIC project that saves a department two hours a week but never touches a metric leadership reviews is a hobby, not a deployment. Six Sigma programs fail when belts chase interesting problems instead of important ones. Organizational goal linkage answers: If this project succeeds, which enterprise or business-unit result improves?
ASQ’s CSSGB Body of Knowledge (I.A.2) expects you to understand how project goals relate to organizational goals—not merely to write a clever problem statement. That includes:
- Selecting projects that support strategy, customer commitments, regulatory obligations, or cost structure
- Writing goals that can be measured and verified at tollgates
- Recognizing how information and work flow between levels of the organization
- Avoiding sub-optimization (winning locally while the system loses)
- From Strategy to Project Y
Think of goal linkage as a vertical chain:
Enterprise / corporate goals — Growth, profitability, safety, compliance, market position, ESG targets.
Business unit or value-stream goals — On-time delivery for a product line, claims cycle time for a region, first-pass yield for a plant.
Process KPIs — Metrics the process owner already reviews (defect rate, lead time, cost per transaction).
Project Y (primary metric) — The specific outcome the Green Belt will move within scope and timebox.
Consequential metrics — Related measures that must not degrade (or must improve) as Y improves.
Worked example — hospital pharmacy:
- Level Goal / metric
- Enterprise Improve patient safety and reduce preventable harm
- Business unit Reduce medication-related adverse events 15% this fiscal year
- Process KPI Order-verification error rate and turnaround time
- Project Y (primary) Reduce wrong-dose verification escapes from 12 to ≤3 per 10,000 orders in 6 months
- Consequential Median verification turnaround ≤20 minutes; no increase in overtime hours
The Green Belt does not “own” enterprise patient-safety strategy, but the charter explicitly shows how the project supports it. The Champion signs because the linkage is clear.
SMART Goals for Six Sigma Projects
Vague goals (“improve quality,” “make customers happier”) cannot be baselined or verified. SMART criteria turn strategy into an auditable project target:
Letter Meaning Project application
S — Specific Clear process, defect, and boundary “Invoice coding defects on domestic AP invoices,” not “AP problems”
M — Measurable Operational definition and data source Defects per opportunity, % on-time, mean cycle time with unit and formula
A — Achievable Stretch but feasible for belt, data, and authority Based on baseline, resource, and best-practice gap—not fantasy zero overnight
- R — Relevant Linked to organizational priority Ties to CoPQ, CSAT, compliance, or capacity
- T — Time-bound Deadline for target performance “By 30 November 2026” aligned with tollgate schedule
Weak vs. strong goal statements:
Weak: “Reduce customer complaints about shipping.”
SMART: “Reduce damage-related shipping complaints for SKU family A from 4.8% to ≤2.0% of orders shipped from Plant North within 5 months of charter approval, measured weekly from CRM category ‘damage in transit,’ without increasing average pack time above 95 seconds.”
The strong statement names the metric, baseline, target, scope, time, data source, and a consequential guardrail (pack time). That is what belongs in the project charter goal section.
Inputs, Outputs, and Feedback Across Levels
Organizations are systems. Each level consumes inputs , produces outputs , and receives feedback that should adjust behavior.
Level Typical inputs Typical outputs Feedback loops
Enterprise Markets, capital, regulation, strategy Financial results, brand, compliance posture Board reviews, earnings, market share, risk reports
Function / plant / BU Enterprise targets, budgets, policies Local scorecard results, capacity, quality Monthly ops reviews, customer scorecards
Process SOPs, materials, staffing, IT systems Products/services meeting CTQs KPI dashboards, audit findings, VOC
Project Charter, baseline data, team time, tools Improved process, control plan, validated savings Tollgates, Champion reviews, control-chart signals after handoff
Green Belt implications:
Inputs to your project include the strategic reason for selection, access to data, sponsor authority, and cross-functional participation. Missing inputs (no data owner, no Champion) are project risks, not excuses to skip Define.
Outputs from your project are not only a lower defect rate; they include documentation, training, updated SOPs, and a process owner who accepts the control plan.
Feedback must travel both ways. Upward: report metric movement and barriers. Downward: receive priority changes, resource decisions, and strategy updates that may reprioritize the portfolio.
When feedback is broken—projects close without control metrics, or scorecards ignore project Y—gains decay and the deployment loses credibility.
Aligning Project Selection with Goals
Not every problem deserves a full DMAIC project. Goal-aligned selection typically prefers:
- Chronic issues with meaningful CoPQ or risk exposure
- Problems with unclear root cause (not just a known fix waiting for funding)
- Processes with available or obtainable data
- Scope a Green Belt can finish (often a few months, limited process boundary)
- Clear process owner and Champion
Use a simple intake question: Which organizational goal moves if we win? If the team cannot answer in one sentence, refine scope or decline the project.
Portfolio view (Champion/Black Belt territory, Green Belt awareness): Multiple Green Belt projects should not all attack the same constrained resource or create conflicting local optima (for example, one project cuts inventory while another demands higher service levels without a shared model). Goal linkage includes horizontal awareness, not only vertical mapping.
Primary vs. Consequential Metrics
Organizational goals are multi-dimensional. Improving one dimension can damage another if you only watch a single Y.
Primary metric — The main outcome of the project (defect rate, lead time, cost per unit, first-pass yield).
Consequential (secondary) metrics — Measures that protect the system (safety incidents, overtime, customer wait time, employee turnover, scrap of a related product).
Worked example — claims processing: Primary goal is to reduce mean cycle time from 12 days to 7 days. Consequential metrics might include accuracy rate ≥99%, reopened-claim rate not increasing, and average handle time on complex claims remaining stable. A “win” that meets cycle time by rubber-stamping claims fails organizational goals even if the primary chart looks green.
Document both metric types in the charter and review them at every tollgate.
Green Belt Practices That Keep Goals Honest
Write the linkage sentence in the charter — “This project supports BU Goal 3 (reduce CoPQ 10%) by cutting rework hours in Process X.”
Baseline before promising — Achievable targets need Measure-phase reality, not Define-phase optimism alone; update targets if MSA or data prove the baseline wrong.
Use the same operational definitions as the scorecard when possible so finance and operations accept the results.
Close with owner acceptance — Goal linkage ends when the process owner runs the control plan and the metric continues to appear on the operational review.
Escalate misalignment early — If strategy shifts mid-project, reconfirm with the Champion rather than finishing a project that no longer matters.
Organizational goals are the “why.” SMART project goals are the “what and when.” Inputs, outputs, and feedback are the “how the system stays aligned.” Master all three and your Green Belt work will support—not distract from—the business.