CSSBB · Domain 1 of 9

CSSBB Domain 1: Organization-wide Planning and Deployment

Why an organization runs six sigma at all, how projects are tied to strategy, and who does what from executive to Green Belt. It sets the governance lens the rest of the CSSBB exam assumes.

Exam weight
8%
Official subsections
2
Estimated questions estimate
~12
Suggested study time estimate
15–20 hrs

About 16 min read Reviewed October 2026

Overview

Organization-wide Planning and Deployment is the strategic frame for everything else on the CSSBB exam. It covers the origins and value of six sigma and lean, how DMAIC, lean, PDCA and design for six sigma fit together as continuous improvement methods, how processes connect to wider business systems, and how leaders use strategic planning (SWOT, PESTLE, hoshin kanri) to select and deploy improvement initiatives. The second half addresses leadership: the defined roles of executives, champions, process owners, Master Black Belts, Black Belts and Green Belts, and the organizational roadblocks and change-management tactics that decide whether a deployment survives.

Candidates must think like a deployment lead, not a statistician. Questions ask which project deserves resources, who owns a decision, or why an initiative stalled. The answers connect to stakeholder and financial measures in Domain 2 and to team management in Domain 3.

How it's tested

Questions here are short organizational scenarios rather than calculations. Expect role-assignment items, BEST or MOST appropriate choices about which methodology or project fits a situation, and cause-of-failure items about stalled deployments. The right answer usually aligns improvement with strategy and puts accountability with the role that owns it.

  • Who owns it

    A deployment task such as removing a barrier, approving scope or owning the improved process is described, and you pick the role responsible: champion, process owner, Master Black Belt or Black Belt.

  • Which methodology fits

    A problem is described and you decide whether DMAIC, lean waste removal, a kaizen event, or design for six sigma is the best match based on whether a process exists and whether the root cause is known.

  • Why the deployment stalled

    A program loses momentum and you identify the roadblock, such as missing executive sponsorship, projects disconnected from strategy, or no process owner to sustain gains.

Reasoning it through

A plant has completed twelve Green Belt projects, but leadership sees no change in operating margin. The options include more statistical training, more projects, and linking project selection to the strategic plan. The clue is the gap between project activity and business results. Projects chosen bottom-up without strategic alignment rarely move enterprise metrics, so the best answer is a selection process tied to strategic objectives through leadership or hoshin kanri.

Subsections 2

Official subsections from the ASQ outline, in outline order.

1.1 Organization-wide considerationsSix sigma and lean fundamentals, improvement methodologies, business systems and strategic deployment.
What it means
This covers the value and history of six sigma (Motorola's defect-reduction origin, the 3.4 defects per million opportunities goal) and lean (Toyota Production System, waste removal), how DMAIC, DMADV, PDCA, lean and theory of constraints relate, how processes sit inside business systems, and how strategic planning tools (SWOT, PESTLE, hoshin kanri) feed project selection.
What to understand
Six sigma attacks variation and defects using data, lean attacks waste and flow, and the two combine because a stable, low-variation process is easier to make fast. Strategic deployment means projects are chosen to close gaps in strategic objectives, cascaded through hoshin kanri catchball, not picked because a tool is interesting.
How it shows up
A scenario describes a problem and asks which improvement approach or strategic-planning tool fits best, or how a project portfolio should be aligned with organizational goals.
Common confusion
Candidates treat lean and six sigma as rival programs or assume DMAIC fits every problem; when no process exists yet, a design methodology such as DMADV is the correct choice.
1.2 LeadershipDeployment roles and responsibilities, organizational roadblocks and change management.
What it means
This covers who does what in a six sigma deployment (executive leadership, champions, process owners, Master Black Belts, Black Belts, Green Belts, Yellow Belts) and the barriers that derail change: structure, culture, resistance, and lack of resources, along with the change-management techniques that address them.
What to understand
Executives set direction and select strategic priorities; champions sponsor projects, remove barriers and own resources; process owners own the process before and after the project; Master Black Belts coach and govern methodology; Black Belts lead complex projects full time. Change management works on the reasons people resist, using communication, involvement, and aligned incentives.
How it shows up
A stalled project or resistant department is described, and you must choose the role that should act or the change technique that addresses the real cause.
Common confusion
Assigning barrier removal or resource allocation to the Black Belt, when that authority sits with the champion; the Black Belt escalates, the champion clears.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Six sigma performance level

    A process at six sigma quality produces about 3.4 defects per million opportunities (DPMO), which assumes the long-term mean drifts 1.5 standard deviations from target.

    Remember
    Short-term sigma level equals long-term Z plus 1.5, so 3.4 DPMO corresponds to a long-term Z of 4.5 and a short-term sigma of 6.
    Tested as
    Deployment questions use the 3.4 DPMO goal to describe what six sigma means as a business target, and Measure-section questions convert between DPMO and sigma level.
    Trap
    Treating 3.4 DPMO as the tail area beyond six standard deviations of a centered normal curve, which is roughly 0.002 parts per million, not 3.4.
  • DMAIC

    Define, Measure, Analyze, Improve, Control is the six sigma method for improving an existing process whose root causes are unknown.

    Remember
    DMAIC needs an existing process and data; it ends with a control plan and handoff to the process owner.
    Tested as
    Methodology-selection items test whether a scenario describes an existing process with an unknown cause, which points to DMAIC.
    Trap
    Choosing DMAIC for a brand-new product or service, where DMADV or another DFSS method is designed for the job.
  • Lean and the eight wastes

    Lean maximizes customer value by removing non-value-added activity; the common list is defects, overproduction, waiting, non-utilized talent, transportation, inventory, motion and extra processing (DOWNTIME).

    Remember
    Lean defines value from the customer's view: an activity adds value only if the customer would pay for it, it changes the product, and it is done right the first time.
    Tested as
    Questions describe a process symptom such as piles of work between steps and ask which waste it represents or why lean is integrated with six sigma.
    Trap
    Classifying required but non-value-added activity, such as regulatory inspection, as pure waste to eliminate rather than minimize.
  • Theory of constraints (TOC)

    TOC holds that throughput of a system is limited by one constraint, improved through five focusing steps: identify, exploit, subordinate, elevate, repeat.

    Remember
    Improving a non-constraint step does not increase system throughput.
    Tested as
    Scenarios ask where to focus improvement when one step limits output, or why local efficiency gains did not raise output.
    Trap
    Elevating the constraint with capital spending before exploiting it with existing capacity, which reverses the TOC sequence.
  • Hoshin kanri

    Hoshin kanri (policy deployment) cascades a few breakthrough objectives from leadership to every level using catchball, a back-and-forth negotiation of targets and means.

    Remember
    It links strategy to projects and includes regular review; the X-matrix is a common one-page form.
    Tested as
    Asked when a scenario shows projects disconnected from strategic goals and seeks the mechanism to align them.
    Trap
    Confusing it with a top-down directive; catchball means lower levels negotiate how targets are achieved.
  • SWOT and PESTLE

    SWOT lists internal strengths and weaknesses plus external opportunities and threats; PESTLE scans external political, economic, social, technological, legal and environmental factors.

    Remember
    Strengths and weaknesses are internal, opportunities and threats are external; PESTLE feeds the external half of SWOT.
    Tested as
    Items describe a factor such as a new regulation and ask where it belongs in strategic planning.
    Trap
    Listing a competitor's new product as a weakness rather than an external threat.
  • Champion

    A champion is the senior manager who sponsors projects, selects and scopes them with leadership, provides resources and removes organizational barriers.

    Remember
    Champions hold the authority the Black Belt lacks: budget, people and cross-functional influence.
    Tested as
    The most frequent role question: who should resolve a blocked project or reassign resources.
    Trap
    Picking the Master Black Belt, whose role is technical coaching and methodology governance rather than organizational authority.
  • Process owner

    The process owner is the manager accountable for a process's day-to-day performance, who supplies team members and accepts the improved process at Control.

    Remember
    Sustaining gains is the process owner's job after handoff, not the Black Belt's.
    Tested as
    Control and deployment questions ask who maintains the control plan or who must agree to the solution.
    Trap
    Assuming the Black Belt keeps monitoring the process indefinitely after the project closes.
  • Master Black Belt

    A Master Black Belt is the deployment's technical expert who trains and coaches Black Belts and Green Belts, reviews project rigor and helps select projects.

    Remember
    Master Black Belts govern method quality; they are not usually project leaders or resource owners.
    Tested as
    Appears when a scenario asks who should review statistical analysis or mentor a struggling Black Belt.
    Trap
    Treating the Master Black Belt as the person who approves budget or overrides line managers.
  • Resistance to change

    Resistance is the predictable response when people see loss of control, competence, status or security from a change; it can be technical (disagreeing with the solution) or social (fearing its effects).

    Remember
    Address the cause: involve people early, communicate the why, align measures and rewards, and make leadership support visible.
    Tested as
    Items describe pushback and ask the BEST first response for a Black Belt or leader.
    Trap
    Escalating or mandating compliance first, when involving the resisters in the solution is usually the better first move.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Champion vs. process owner vs. Master Black Belt vs. Black Belt

ConceptMeaningKey differenceCommon trap
Champion Senior sponsor who selects and scopes projects with leadership and supplies resources Has organizational authority to remove barriers across functions Confused with the process owner, who owns daily operation of one process
Process owner Manager accountable for the process's ongoing performance Owns the process before and after the project and sustains the gains Assumed to drive project analysis rather than accept and maintain the solution
Master Black Belt Expert coach, trainer and methodology steward Governs technical rigor across many projects Chosen for resource or budget decisions it does not control
Black Belt Full-time leader of complex, cross-functional projects Leads the team and the DMAIC analysis; mentors Green Belts Expected to resolve political roadblocks without escalating to the champion

Six sigma vs. lean vs. theory of constraints

ConceptMeaningKey differenceCommon trap
Six sigma Data-driven reduction of variation and defects Primary metric is defects or DPMO and capability Used where the issue is flow delay rather than variation
Lean Removal of waste to speed value flow Primary metrics are lead time, process cycle efficiency and inventory Assumed to ignore quality, when defects are one of the eight wastes
Theory of constraints Managing the single bottleneck that limits throughput Focuses on one constraint and subordinates everything else to it Improving many steps at once rather than the constraint

DMAIC vs. DMADV vs. PDCA

ConceptMeaningKey differenceCommon trap
DMAIC Improve an existing process with an unknown root cause Starts from baseline data on a running process Applied to a process that does not exist yet
DMADV Define, Measure, Analyze, Design, Verify for a new product or process Designs to customer requirements from the start Chosen for a small fix to a working process
PDCA Plan-Do-Check-Act iterative improvement cycle Lighter weight; suits quick, repeated small changes Treated as a synonym for DMAIC despite less structured analysis

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Black Belt as the fixer of politics

    What candidates pick
    The Black Belt negotiates directly with a department head who refuses to release team members.
    Why it looks right
    The Black Belt leads the project and seems responsible for its success.
    Why it's wrong
    Resource and cross-functional authority belongs to the champion; the Black Belt's correct move is to escalate the barrier to the champion.

    Clue to watch for The obstacle is about people, budget or another manager's priorities rather than analysis.

  2. More projects equals more results

    What candidates pick
    Launch additional projects when the deployment shows activity but no bottom-line impact.
    Why it looks right
    Volume of projects looks like commitment to the program.
    Why it's wrong
    Without strategic linkage and financial validation, extra projects add cost without moving enterprise metrics.

    Clue to watch for Many completed projects but flat business results.

  3. One methodology for everything

    What candidates pick
    DMAIC for a new service launch.
    Why it looks right
    DMAIC is the best-known six sigma roadmap.
    Why it's wrong
    DMAIC improves an existing process; a new design calls for DMADV or another DFSS approach.

    Clue to watch for Words such as new product, new service or no current process.

  4. Mandate over involvement

    What candidates pick
    Have leadership order staff to adopt the new process.
    Why it looks right
    It seems fastest and shows executive support.
    Why it's wrong
    Mandates without involvement drive passive resistance and weak sustainment; the better first step addresses why people resist.

    Clue to watch for The scenario mentions fear, distrust or lack of understanding among staff.

  5. Subordinate before exploit

    What candidates pick
    Buy a second machine at the bottleneck immediately.
    Why it looks right
    Added capacity directly attacks the constraint.
    Why it's wrong
    TOC exploits the constraint first (no idle time, no defects reaching it) and elevates with capital only after that.

    Clue to watch for The bottleneck has downtime, changeovers or rework that could be eliminated cheaply.

  6. Internal versus external in SWOT

    What candidates pick
    Classify a new regulation or competitor move as a weakness.
    Why it looks right
    It hurts the company, so it feels like a weakness.
    Why it's wrong
    Weaknesses are internal attributes; outside forces are threats or opportunities.

    Clue to watch for The factor originates outside the organization.

Answer framework

For any deployment or leadership scenario, use this sequence to find the organizationally correct answer.

  1. Identify whether the question is about strategy, methodology choice, a role's responsibility, or resistance to change.
  2. For project selection, prefer the option that links the project to a strategic objective and measurable financial or customer benefit.
  3. For methodology, check whether a process exists and whether the cause is known: unknown cause means DMAIC, no process means DFSS, obvious waste means lean or kaizen.
  4. For roles, give authority over resources and barriers to the champion, method coaching to the Master Black Belt, analysis leadership to the Black Belt and sustainment to the process owner.
  5. For resistance, choose the response that addresses its cause through involvement, communication and aligned measures before escalation or mandates.

Practice question

A Black Belt's project to cut invoice errors has stalled because the accounts payable manager will not release two clerks for team meetings. The Black Belt has already explained the project's goals to the manager. What should the Black Belt do NEXT?

Choose one answer

Want more like this? The CSSBB practice test has questions for every domain.

Checklist

0 of 11

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Start this section after a first pass through DMAIC, because the deployment questions make more sense once you know what each phase produces. Begin with the role map: write out the executive, champion, process owner, Master Black Belt, Black Belt and Green Belt responsibilities on one page, and for each role note one decision it owns and one it does not. Most questions in this section reduce to that table.

Next, build a methodology-selection grid covering DMAIC, DMADV, PDCA, lean, kaizen events and theory of constraints, with the trigger words that point to each. Then cover strategic planning: SWOT versus PESTLE, hoshin kanri with catchball, and how a balanced project portfolio is tied to strategic objectives.

The commonly underestimated area is change management. Candidates skim it as soft content, yet BEST-response questions about resistance are easy to miss when you choose the forceful option. Learn the sources of resistance and the matching responses.

Because the CSSBB is open book, tab your reference handbook at the roles and methodology pages so you can confirm a definition quickly, but do not plan on looking up every item. Afterwards, practice mixed scenario questions and then move to Organizational Process Management and Measures, which supplies the financial and stakeholder measures used to justify projects.

FAQ

How many questions come from Organization-wide Planning and Deployment?

ASQ's Body of Knowledge assigns 12 of the 150 scored questions to this section, about 8% of the exam. The computer-based exam also carries 15 unscored questions that are not allocated by section.

Is this section mostly memorization?

Partly, but the questions are scenario-based. You need the role definitions memorized so you can apply them when a project stalls or a decision needs an owner.

What is the difference between a champion and a process owner?

The champion sponsors the project and clears organizational barriers, while the process owner runs the process daily and takes it over after the project. A champion may sponsor projects across several processes.

Why does six sigma assume a 1.5 sigma shift?

Motorola observed that process means drift over time, so it adds a 1.5 standard deviation allowance when converting short-term capability to long-term defect rates. That is why six sigma short-term equals 3.4 DPMO long-term.

When should a Black Belt recommend DMADV instead of DMAIC?

When there is no existing process to improve, or when the current process is so far from requirements that incremental improvement cannot close the gap and a redesign is needed.

How does this section connect to the rest of the exam?

It explains why projects exist and who sponsors them, which the Define section turns into a charter and the Control section turns into a handoff to the process owner.

Can I rely on my open-book references here?

References help confirm definitions, but at roughly a minute and a half per question you cannot look up every item. Know the role map and methodology triggers without the book.

Other Quality Management certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 1 knowledge

You have covered six sigma and lean fundamentals, strategic project selection, deployment roles and change management. Test whether you can assign the right owner and method in exam-style scenarios.

Keep going