Project Closure & Lessons Learned

Project Closure & Lessons Learned

Quick Answer: Close a DMAIC project by comparing results to the charter, confirming Control handoff, storing documentation where the organization can find it, running lessons learned, and communicating further opportunities—then release the team with explicit residual-risk owners.

Why Closure Is Part of the BoK

ASQ CSSGB BoK II.C.8 is at Apply level: Green Belts must execute closure, not only “stop working.” Many projects die in a gray zone—Improve finished, meetings faded, control charts unwatched. Closure is the governance act that:

1. Declares whether the charter promise was kept
2. Transfers accountability to operations
3. Preserves knowledge
4. Feeds the improvement portfolio with next opportunities

Without closure, benefits claims stay anecdotal and replication is guesswork.

Review Objectives vs. Charter

Start with the approved charter (and any approved change logs). Score the project against commitments:

Outcome categories (be honest)

A “not met” project closed with integrity is more valuable than a “met” claim with no data. Partial success still warrants closure so the organization stops paying for an endless team.

Worked example — charter vs. results:

• Charter goal: Reduce coding defect rate from 6.4% to ≤3.0% within 6 months
• Result: 2.7% for three consecutive months post-Improve; p-chart stable
• Consequential: Average days-to-pay improved 0.4 days (no harm); auditor exceptions flat
• Savings: $142k annualized hard savings validated by Controller method v3
• Decision: Met — close after Control audit #1 and documentation archive

Closure Activities Checklist

Use a structured closeout so nothing critical is left in the Green Belt’s inbox.

1. Results package

• Final before/after for primary and consequential metrics
• Time windows, sample sizes, operational definitions
• Pilot vs. full-scale distinction clearly labeled

2. Control handoff confirmation

• Process owner sign-off on control plan and response plan
• SPC or KPI monitoring live in the operational system
• Training records complete; job aids accessible
• Escalation path tested at least once (tabletop or real signal)

3. Administrative close

• Open actions closed or reassigned with dates
• Budget/code closed if used
• Team recognition and release of borrowed resources
• Risk log: residual risks have operational owners

4. Stakeholder communication

• Champion briefing with outcome category and benefit status
• Thank-you and feedback to SMEs and process staff
• Customer-facing notes only if changes affect them

5. Documentation storage

• See next section—non-negotiable for II.C.8

Documentation Storage

Where documents live matters as much as what they contain. Store the project record in the organization’s system of record (QMS, project PMO library, controlled SharePoint with retention rules)—not only personal drives.

Minimum archive set

Storage practices

• Use naming conventions and metadata (site, process, date, belt name, Y metric)
• Set access so process owners can read control docs without the belt present
• Follow retention and confidentiality rules (especially healthcare, finance, personal data)
• Link from the control plan to the archive location
• Prefer controlled documents for SOPs; keep analytical workbooks as referenced records

If the next Green Belt cannot find the MSA definition of the defect code six months later, closure failed even if the metric looked green on day 90.

Lessons Learned

A lessons learned session is a structured reflection—ideally with the core team, Champion, and process owner—captured in writing.

Facilitation prompts

Rules for useful lessons

• Be specific (“Extract approval took 19 days because Form 12 lacked a backup approver”), not vague (“communication was hard”)
• Separate fact from recommendation
• Avoid personal blame; focus on system fixes
• Feed lessons into deployment standards (charter template, MSA checklist, tollgate agenda)

Lessons learned that never leave a sticky note pile do not meet the intent of closure.

Informing the Organization of Further Opportunities

Closure is not the end of improvement—it is a portfolio feed. Communicate opportunities that appeared during the project but stayed out of scope:

How to communicate without scope creep

1. List opportunities in the final report with estimated impact/feasibility sketches
2. Present them at the closure tollgate as candidates, not silent work
3. Route into the formal project selection process (II.A.1)—do not auto-start a second project without charter
4. Assign a parking-lot owner (Champion or deployment lead), not the exhausted belt by default

This fulfills II.C.8’s expectation to inform the organization of further opportunities while protecting DMAIC discipline.

Closure Tollgate Agenda (Template)

1. Charter commitments vs. results (primary + consequential)
2. Control system demo / evidence of sustainment
3. Benefits status and tracking owner
4. Documentation archive location and access
5. Lessons learned highlights (3–5 actionable)
6. Residual risks and owners
7. Further opportunities for portfolio intake
8. Formal close decision and team release

Common Closure Failures

1. Meeting fade-out — No formal close decision
2. Metric mirage — Goal “met” on a two-week honeymoon sample
3. Control on paper only — Plan written, charts not reviewed
4. Laptop archive — Knowledge leaves with the belt
5. No lessons — Same MSA failure repeats next quarter
6. Opportunity silence — Replication value dies in a drawer
7. Celebrating before finance validation — Credibility burn for the deployment

Green Belt Closure Checklist

• Charter comparison completed and outcome category assigned
• Process owner accepted control plan and monitoring cadence
• Documentation stored in organizational repository with links
• Lessons learned recorded and routed to deployment improvements
• Further opportunities listed for selection/replication
• Residual risks owned outside the project team
• Champion formal close decision recorded
• Team released and recognized

Apply closure rigorously and the project’s value compounds: results stick, methods travel, and the next charter starts smarter. That is the practical meaning of CSSGB II.C.8.