Skip to main content Skip to course navigation

Control and Documentation

Learning Objective

By the end of this lesson, learners will be able to:

  • Understand the importance of documenting Six Sigma project results.
  • Identify the key documents required for project completion.
  • Understand the role of SOPs in maintaining improved processes.
  • Capture lessons learned for future projects.
  • Establish document ownership and version control.
  • Understand how documentation supports transparency and repeatability.

1. Introduction

A Six Sigma project produces important knowledge about the process, the improvement achieved and the controls required to sustain that improvement.

Control & Documentation ensures that project results, lessons learned and control mechanisms are properly documented. This supports transparency and repeatability.

Documentation also helps ensure that the improved process can continue even after the original project team has completed its work.

2. Project Record

The project record captures:

  • What was done.
  • What was achieved.
  • The relevant project results.

It provides a record of the improvement journey and its outcomes.

A complete project record helps future users understand the basis of the improvement and the results obtained.

3. Standard Operating Procedure (SOP)

An SOP defines the standard method for performing the process.

When a Six Sigma project changes the way work is performed, the relevant SOP should reflect the approved improved process.

This helps ensure that the improvement becomes the standard way of working.

4. Lessons Learned

Lessons learned capture knowledge that can be useful for future work.

A Black Belt should document important learning from the project, including relevant experience that can help future teams.

Lessons learned prevent valuable project knowledge from being lost when the project team disbands.

5. Document Ownership

Important project documents should have clearly defined ownership.

Document ownership establishes who is responsible for maintaining and reviewing important documents.

This is particularly important after project closure because responsibility must move from the project team to the appropriate ongoing process owner.

6. Version Control

Version control helps prevent conflicting old and new instructions.

When procedures, training materials or other controlled documents change, the organization should be able to distinguish the current approved version from previous versions.

This supports consistency and reduces the risk of people following outdated instructions.

7. Tools & Techniques

The key tools and techniques are:

  • Control Plans
  • SOPs
  • Project Closure Reports
  • Training Manuals
  • Monitoring Plans
  • Response Plans

These documents collectively support process control, knowledge transfer and sustained improvement.

8. Application Example

Improved Inspection Process

A factory improves its inspection process through a Six Sigma project.

The improved method is documented in the relevant SOP so that the process can be performed consistently by the responsible personnel.

The documentation becomes part of the normal operating system rather than remaining only within the project team’s records.

9. Case Study

Electronics Manufacturing

An electronics firm reduced soldering defects.

To sustain and transfer the improvement, the organization documented:

  • Updated SOPs.
  • Training manuals.
  • Control charts.

The case study identifies this documentation as supporting sustained and transferable improvement.

This demonstrates that documentation is not simply an administrative activity; it supports continued process performance.

10. Black Belt Perspective

Before considering a project ready for closure, a Black Belt should ask:

  • Are the project results documented?
  • Are the current SOPs updated?
  • Are lessons learned captured?
  • Is document ownership clear?
  • Is version control established?
  • Are monitoring and response requirements documented?
  • Can another responsible person understand and follow the improved process?

The objective is to ensure that the improvement is documented, transferable and repeatable.

11. Lesson Practice

  1. What information should a project record capture?
  2. Why should an improved process be reflected in the appropriate SOP?
  3. Why should lessons learned be captured?
  4. Who should own important process documents after project completion?
  5. How does version control prevent conflicting instructions?
  6. What documents should be reviewed before closure?
  7. How does documentation support repeatability?

12. Key Learning Points

  • Documentation supports transparency and repeatability.
  • The project record captures what was done and what was achieved.
  • SOPs define the standard method for performing the process.
  • Lessons learned preserve knowledge for future work.
  • Document ownership establishes responsibility for maintaining important documents.
  • Version control helps prevent the use of outdated instructions.
  • Control Plans, SOPs, closure reports, training manuals, monitoring plans and response plans support sustained improvement.

13. Lesson Conclusion

A Six Sigma improvement should not remain dependent on the people who conducted the project.

Control & Documentation transfers project knowledge into the organization’s normal operating system.

By documenting results, updating SOPs, capturing lessons learned, establishing ownership and maintaining version control, the Black Belt helps ensure that the improvement remains transparent, repeatable and transferable.