Study guide

Owners & Stakeholders

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

Owners & Stakeholders

Key Takeaways Explain This Topic AI

A process owner is accountable for end-to-end process performance and for sustaining improvements after the Green Belt team hands off control.

Stakeholders include anyone who can affect or is affected by the project—sponsors, operators, customers, suppliers, IT, finance, regulators, and adjacent process owners.

Influence/interest (power–interest) analysis prioritizes engagement: manage high-influence/high-interest stakeholders closely and monitor low-influence/low-interest groups.

Green Belt projects fail more often from ignored stakeholders than from weak statistics; map owners and stakeholders in Define and keep them engaged through tollgates.

The sponsor authorizes and resources the project; the process owner owns the process day-to-day—do not treat those roles as interchangeable on the exam.

Last updated: July 2026

Owners & Stakeholders (CSSGB BoK II.A.5 — Apply)

Quick Answer: A process owner is accountable for the process end-to-end and for keeping gains after the project. Stakeholders are anyone who affects or is affected by the work. Use influence/interest analysis to prioritize engagement so high-power, high-interest people get managed closely while low-power groups are monitored or informed.

Define-phase success is not only a clean charter and SIPOC. Projects live or die on people : who owns the process, who can block change, who must live with the new standard work, and who cares about the results. BoK II.A.5 is at the Apply level—recognize roles in scenarios and choose the right engagement strategy.

Process Owner vs Other Stakeholders

A process owner is the person (or role) accountable for how the process performs every day : cycle time, quality, cost, compliance, and customer experience for that stream. The owner typically:

  • Approves process changes and new standard work
  • Allocates operators and local resources for pilots
  • Owns metrics after Control-phase handoff
  • Escalates when the process drifts

Stakeholders is the broader set: individuals or groups with a vested interest in the project’s outcome or with power to help or hinder it. Every process owner is a stakeholder, but not every stakeholder is the process owner.

Role Primary accountability Typical Green Belt interaction

Process owner Day-to-day process performance and sustainment Co-own problem statement; approve future-state design; accept control plan

Project sponsor / champion Business case, priority, resources, barriers Charter approval; tollgate decisions; remove organizational obstacles

  • Team members / operators Execute process; provide Gemba truth Map process; pilot changes; suggest waste fixes
  • Customers (internal/external) Receive outputs; define value VOC, CTQ validation, satisfaction feedback
  • Suppliers Provide inputs Input quality, lead time, specification alignment

Functional support (IT, finance, HR, quality, legal) Systems, money, people, compliance Data access, cost models, training, policy

  • Adjacent process owners Upstream/downstream handoffs Boundary agreements; prevent local optimization
  • Regulators / auditors External compliance constraints Constraints the future state must still meet

Exam trap: Confusing sponsor with process owner . The sponsor may be a VP who funds the project and sits at tollgates but does not run the daily packing line. The packing supervisor (or operations manager) is more often the process owner. If the stem asks who must sustain the control plan after the team disbands, choose the process owner , not the distant executive sponsor—unless the stem clearly makes the sponsor both.

Why Stakeholder Clarity Matters on Green Belt Projects

Six Sigma projects change work. Change creates resistance, support, or indifference depending on impact and influence. Without a clear owner:

  • No one enforces the new procedure after the celebration meeting
  • Metrics stop being reviewed
  • Old workarounds return
  • The next audit finds “tribal knowledge” again

Without a stakeholder map:

  • IT learns about a system change two weeks before go-live
  • Finance disputes hard savings because they were never in the loop
  • An upstream planner keeps pushing oversized batches into your improved cell
  • A high-influence skeptic quietly stalls training

Green Belts apply stakeholder thinking in Define (who must agree the problem is real), Improve (who must approve pilots), and Control (who owns the process afterward).

Influence / Interest Analysis

A practical tool is the power–interest (or influence–interest ) grid. Plot each stakeholder on two axes:

  • Influence (power): ability to enable, fund, block, or reverse the project
  • Interest: how much they care about the outcome or will feel the impact
  • Quadrant Influence Interest Engagement strategy
  • Manage closely High High Frequent two-way communication; involve in key decisions; never surprise
  • Keep satisfied High Low Enough updates to protect support; do not overburden with detail
  • Keep informed Low High Regular status; invite input that improves the design
  • Monitor Low Low Light touch; watch for role or interest shifts
  • Worked example — claim-processing project

A Green Belt is reducing first-pass reject rate on insurance claims.

Stakeholder Influence Interest Placement Action

Claims operations manager (process owner) High High Manage closely Weekly huddles; co-sign charter and control plan

  • Division VP (sponsor) High Medium–high Manage closely / keep satisfied Tollgates; exception escalations only
  • Claims examiners Medium High Keep informed + involve Workshops, pilots, standard-work feedback

IT ticket-routing owner High Low (until system change) Keep satisfied → manage closely if scope hits systems Early architecture check; freeze dates

  • Marketing Low Low Monitor FYI only
  • External regulators High (constraints) Medium Keep satisfied Confirm compliance of new checklist

If the team designs a new screen workflow without IT and the process owner, the “statistically significant” pilot may never deploy. Influence/interest analysis prevents that failure mode.

Applying Stakeholder Analysis on Real Projects

Step 1 — Identify. Brainstorm from SIPOC, org charts, and Gemba: suppliers, customers, owners, support functions, and anyone who loses status, overtime, or comfort from the change.

Step 2 — Classify. Mark process owner(s), sponsor, core team, and external constraints. One process may have a single owner; cross-functional streams sometimes need a named primary owner plus supporting owners—ambiguity here is a red flag.

Step 3 — Assess influence and interest. Use interviews and observation, not wishful thinking. Quiet people with budget authority still have high influence.

Step 4 — Plan engagement. Match communication frequency and depth to the quadrant. High-influence skeptics need face time and data, not only email blasts.

Step 5 — Revisit. Interest and influence shift when scope changes (for example, when Improve needs a software change, IT jumps to “manage closely”).

Green Belt Behaviors That Score on the Exam

Name the process owner when asked who accepts the control plan or owns Y after project close.

Distinguish sponsor (authority/resources) from owner (process accountability).

Use influence/interest language when a stem describes a powerful but disengaged VP versus highly interested frontline staff with little formal power.

Prefer early engagement of high-influence stakeholders over heroic late-stage persuasion.

Tie stakeholder work to project success and sustainment , not to soft “team building” alone.

Scenario pattern: “Which action should the Green Belt take first after charter approval?” If options include statistical analysis before talking to the process owner and high-influence functions that supply data or live with the change, the BoK-aligned answer is usually confirm owners and engage critical stakeholders , then proceed with measurement design.

Owners and stakeholders are not a soft sidebar to DMAIC—they are how Define-phase projects earn the right to change the process and keep the gains.