01 · Close the project without abandoning the process
Close the project without abandoning the process
Project closure ends a temporary improvement effort and confirms how its outputs will be owned in operation. It is a decision supported by evidence, not simply the date of a presentation or the moment a new system goes live. The process continues after the project closes. The operating owner must therefore be able to maintain the standard, recognise abnormal conditions and manage change without relying on the former project team.
Distinguish deliverable acceptance, operational readiness and benefit realisation. A scanner installation can be accepted as a deliverable while operator training remains incomplete. Training can be complete while the longer-term reduction in customer claims has not yet been established. These states should be stated separately. Closure may be appropriate when remaining benefit checks are explicitly assigned, but it should not conceal unresolved readiness risks.
Agree closure criteria early enough to guide the work. Include scope completion, required acceptance, controlled instructions, capability, data availability, response arrangements and residual risks. A late checklist cannot replace missing tests or an owner who lacks authority.
02 · Prepare the handover evidence
Prepare the handover evidence
Review what was promised and what was actually delivered. Identify approved scope changes and remaining work. Obtain acceptance from the appropriate owner or customer based on defined criteria rather than informal satisfaction alone. Where external contracts or internal approvals apply, complete the relevant obligations through the organisation’s normal route.
Demonstrate operational capability. The owner should retrieve the standard, explain the measures, show how an exception is handled and identify the escalation route. Confirm support arrangements, spare equipment where necessary, system access and maintenance ownership. A training attendance list is useful but does not establish that the team can operate the changed process.
Review residual risk with consequences and controls. An unresolved issue can be accepted when the authorised owner understands it, suitable protection exists and a clear action is assigned. Do not label every outstanding matter a harmless follow-up. Some gaps, such as no safe response during a network outage, may prevent responsible handover until addressed.
| Closure question | Evidence example | Continuing owner |
|---|---|---|
| Delivered scope accepted? | Acceptance against agreed criteria | Sponsor or authorised customer |
| Operation ready? | Demonstrated normal and exception routes | Process owner |
| Benefits realised? | Validated outcomes and actual costs | Benefits owner |
| Future checks assigned? | Named review, date and evidence | Accepting operational role |
03 · Worked example: Northbank’s closure decision
Worked example: Northbank’s closure decision
Fictional Northbank has implemented automated carrier-service validation. The project sponsor expects closure after six weeks of operation. At the readiness review, the dispatch manager demonstrates ordinary release, hold and reprint decisions. Both shifts can retrieve the current instruction. Data definitions are agreed, the control chart is assigned to an operating role, and the systems duty team accepts responsibility for configuration recovery.
One gap remains: the late shift has not tested the fallback when the scan service is unavailable. The owner does not accept this as a paperwork omission. The team performs a controlled interruption test with a small authorised set of parcels, verifies that release is blocked, checks the hold capacity and confirms the recovery sequence. The instruction is corrected where the test reveals ambiguity.
The sponsor accepts the delivered scope and closes the temporary project once the operating owner accepts the process. A peak-demand review remains scheduled because the trial did not include seasonal volume. It is assigned to the dispatch manager with a date and evidence requirement. The closure record states that normal-demand benefits have been observed, while peak robustness remains to be verified.
04 · Validate benefits with a credible boundary
Validate benefits with a credible boundary
State which benefits have been realised, which are forecast and which need later confirmation. Compare outcomes using consistent definitions and relevant context. Consider volume, case mix, seasonality and concurrent changes. A favourable before-and-after result may support a useful conclusion without proving that the project alone caused every difference. Explain the practical limits.
Northbank observes reduced service mismatches and fewer reprint investigations. It also estimates released staff capacity. Finance confirms a modest reduction in overtime, while some saved time has been used to handle additional volume. The closure report separates these effects instead of converting all saved minutes into cash. It includes implementation and ongoing support costs so the benefit claim remains meaningful.
Assign a benefits owner and review schedule for effects that develop after closure. The owner needs access to measures and the authority to respond if benefits erode. A scheduled review without ownership is a weak promise. Define what would trigger renewed improvement or corrective action, and where the result of the review will be recorded.
05 · Capture learning and finish obligations
Capture learning and finish obligations
Conduct a focused lessons review while participants can still recall the evidence. Ask which decisions helped, which assumptions failed and what another team should do differently. Convert broad statements into usable learning. “Communicate better” is vague; “test exception instructions on both shifts before approving handover” identifies a repeatable change. Record context so another process does not apply the lesson mechanically.
Archive the final project record, transfer document ownership and close temporary access or environments through approved routes. Reconcile resources and obligations. Return borrowed equipment, release project roles and clarify which support commitments remain active. These steps prevent a nominally closed project from continuing as an invisible burden on staff.
Recognise contributions and communicate the operating change to those affected. The message should explain the current standard and support route, not merely celebrate a percentage. Northbank’s closure briefing identifies the new owner, the authorised hold process and the later peak review. The operating team leaves with a usable system rather than a final slide deck alone.
06 · Judge closure quality after the event
Judge closure quality after the event
Common closure errors include declaring victory at installation, accepting documents nobody can use, forgetting out-of-hours support and reporting projected benefits as realised. Another error is keeping the project open indefinitely because some benefits need time. Separate completed project responsibilities from continuing operational and benefits responsibilities, then make the transfer explicit.
A post-closure check should look for dependency and drift. Does the process still call the former analyst whenever a chart needs updating? Are operators following the current instruction? Have temporary overrides become routine? If so, revisit the handover gap or operating control. The purpose is to maintain the result, not to reopen every completed project administratively.
Advanced closures may involve several sites, suppliers or staged releases. Use clear acceptance boundaries and site-specific readiness evidence. One successful site does not establish readiness everywhere. A responsible closure decision makes these boundaries visible, assigns remaining ownership and preserves the evidence that allows future decisions to be reviewed.
07 · Choose a closure decision explicitly
Choose a closure decision explicitly
The review can accept closure, accept closure with clearly owned continuing obligations, or defer closure because essential readiness criteria are unmet. Record the selected decision and its reasons. Northbank initially defers because the interruption route has not been demonstrated, then accepts closure with a later peak-demand benefits review. The later review is an operating commitment, while the missing fallback test was a handover defect. Distinguishing these conditions prevents both premature closure and an indefinitely open project. Check that every continuing obligation has an accepting owner, access to the relevant evidence and a realistic review date. A list of unassigned “future work” is not a completed transfer.
Connections
Related methods and phase use
Placed under Control because of the outcome it supports. Use the method in other phases when its purpose and assumptions fit the work; the phase list is a guide to selection, not a compulsory sequence.
Sources
Professional foundations and further reading
The explanation and fictional teaching examples are written for LeanTrainingLab. Linked primary sources provide professional foundations; example values and local conventions are stated in the guide. The accepted toolset draws on Six Sigma+Lean Toolset, second edition (Lunau, editor; Springer, 2013). No book text or examples are reproduced here.