Study guide
Project Documentation
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
Project Documentation
Key Takeaways Explain This Topic AI
Project documentation captures inputs, decisions, analyses, and results so work is auditable, transferable, and reviewable at tollgates.
Green Belts manage many data and input types—VOC, process maps, measurement plans, statistical output, risk logs, and financial benefit sheets.
Storyboards summarize the DMAIC narrative on a single visual path for leadership reviews and knowledge sharing.
Spreadsheet (or dashboard) summaries package phase metrics, sample sizes, and before/after results for tollgates without dumping raw files.
Good documentation is current, versioned, and stored where the organization can find it after the belt moves on.
Last updated: July 2026
Project Documentation
Quick Answer: Document the data and inputs your DMAIC project uses, maintain a living storyboard of the project narrative, and bring spreadsheet or dashboard summaries to each phase review. Documentation proves rigor, speeds tollgates, and preserves methods after the Green Belt rotates off the process.
Why Documentation Is a Belt Skill
ASQ CSSGB BoK II.C.6 asks Green Belts to apply project documentation: identify what must be recorded, organize phase evidence, and present concise packages for reviews. Documentation is not bureaucracy for its own sake. It:
- Makes analysis reproducible (another analyst can rebuild the baseline)
- Supports tollgate decisions with facts instead of memory
- Enables handoff to process owners and future audits
- Feeds lessons learned and replication across sites
- Protects the organization when personnel change mid-project
Weak documentation is a leading indicator of projects that “worked once in a meeting” and then silently regressed.
Data and Input Types Green Belts Document
Think in categories so nothing critical lives only in email threads.
- Category Examples Why keep it
- Charter & scope Problem/goal statements, SIPOC, in/out of scope, RACI Anchors every later claim
- Customer & stakeholder inputs VOC notes, CTQ trees, complaint themes, interview logs Links Y to customer value
- Process knowledge Maps, spaghetti diagrams, standard work, system screenshots Shows how work really flows
- Measurement system Operational definitions, MSA plans/results, data dictionaries Defends data quality
- Data sets & extracts Raw files, query definitions, sample frames, time windows Enables reanalysis
- Analysis artifacts Graphs, hypothesis tests, multi-vari, regression, DOE setup Evidence for vital few X’s
- Risk & change Risk register, FMEA snippets, pilot risks, mitigation status Supports go/no-go
- Implementation Pilot plans, training records, SOP revisions, IT tickets Proves Improve really landed
- Control & benefits Control plan, response plan, SPC setup, CoPQ/savings tracker Sustains and monetizes gains
- Governance Tollgate decks, decisions, action logs, Champion approvals Audit trail
- Input vs. output documentation
- Inputs: What the team received or collected (VOC, extracts, SME interviews)
- Working analyses: Intermediate calculations and candidate models
- Outputs / deliverables: Charter, MSA report, root-cause package, control plan, closure report
Label status clearly: draft / in review / approved . Ambiguous “final_v7_REAL.xlsx” is how organizations lose the approved baseline.
Principles of Useful Project Docs
Traceability: Every metric on a slide should point to a defined field, period, and filter.
Version control: Date, author, version; one source of truth location (SharePoint, PLM, QMS, project folder).
Operational definitions first: Numbers without definitions are not evidence.
Right altitude: Executives need summaries; analysts need appendices—do not force either audience into the wrong layer.
Security & privacy: Mask customer PII, patient data, or regulated fields; document redaction rules.
Living, not archaeological: Update when the plan or baseline changes; do not only archive at the end.
Storyboards
A project storyboard is a structured visual summary of the DMAIC journey—often one page per phase or a single multi-panel board. It tells the story: problem → measure → causes → solutions → controls → results.
Typical storyboard panels
- Phase Panel content
- Define Problem, goal, scope, business case, team
- Measure Y definition, MSA headline, baseline performance
- Analyze Vital few X’s, key graphs, root-cause statement
- Improve Solutions selected, pilot design, before/after
- Control Control plan highlights, owner, response rules, sustain metrics
- Why storyboards work at reviews
- Leadership can follow logic in minutes
- Gaps become obvious (e.g., solutions without verified causes)
- Replication teams get a portable template
- Storyboards force selection : only the vital evidence stays on the board
- Storyboard anti-patterns
- Walls of unreadable statistical output with no “so what”
- Solutions appearing in Define before any Measure
- Before/after charts with unlabeled axes or cherry-picked weeks
- No link back to the charter goal statement
Worked example — Measure panel one-liners:
- Y: % invoices with coding defect (operational definition v2.1)
- MSA: attribute agreement κ = 0.82 after recalibration (was 0.51)
- Baseline: 6.4% defect rate (n = 1,240 invoices, Jan–Mar), stable mean on p-chart
- Stratification: Vendor family C at 11.2% drives ~48% of defects
That panel is review-ready; a 40-tab workbook alone is not.
Spreadsheet Summaries for Phase Reviews
Tollgates need decision packages , not raw dumps. Spreadsheet (or BI dashboard) summaries typically include:
- Summary sheet Contents
- Charter snapshot Problem, goal, scope, dates, owners
- Metric tracker Primary Y, consequential metrics, targets, current vs. baseline
- Sample & data log Sources, n, time window, exclusions with justification
- MSA summary Method, acceptance criteria, result, action if failed
- Analysis index Link or pointer to each key study and conclusion
- Risk & issue log Top risks, owners, due dates, residual risk
- Action register Open actions from last tollgate with status
- Financials Soft/hard savings assumptions, finance validation status
- Formatting that helps Champions
- One dashboard tab with red/yellow/green vs. exit criteria
- Frozen header rows; units on every column
- Explicit “as of” date
- Separate appendix tabs for supporting pivots—do not clutter the decision view
- Phase-review checklist (documentation view)
- Exit criteria listed with pass/fail evidence cells
- Metric definitions match the charter (or approved change log)
- Sample sizes and time windows stated
- Open risks and resource needs highlighted
- Decisions requested (go / conditional / recycle) written in advance
- Links to full analyses available for deep dive
- Documentation Rhythm Across DMAIC
- When Minimum documentation update
- Project kickoff Folder structure, charter, RACI, communication plan
- End of each week Action log, risk log, schedule actuals
- Pre-tollgate Storyboard + summary pack + appendix
- Post-tollgate Decision record, revised plan if conditional go
- Pilot Protocol, data, issues, decision to scale
- Control handoff Control plan, SOPs, training records, owner sign-off
- Closure Final report, lessons learned, repository location
- Common Documentation Failures
- Hero laptop only — Project dies when the belt changes jobs
- No operational definitions — Later teams cannot reproduce Y
- Screenshot graveyards — Images without source queries or dates
- Storyboard theater — Pretty boards that contradict the data appendices
- Finance afterthought — Benefits claimed with no documented assumption trail
- Ignoring consequential metrics — Only the primary Y appears in summaries
- Green Belt Documentation Starter Kit
Create these shells on day one:
- Project charter (approved)
- Shared folder with phase subfolders
- Data dictionary + operational definitions
- Risk/issue/action log
- Metric tracker spreadsheet
- Storyboard template
- Tollgate decision log
Fill them continuously. Documentation applied this way is a management system for the project—not a final scramble the night before the gate.
Strong II.C.6 practice means anyone reviewing your storyboard and summary pack can answer: What was wrong, how do we know, what changed, who owns sustainment, and where is the evidence stored?