Closing the Project and Learning from It
❦
Why Closing Matters
Projects that are left to drift to an end lose their lessons and their results. Formal closure confirms that the work is complete, transfers the results, releases resources, and captures knowledge.
Closure Activities
| Activity | Purpose |
| Verify that all deliverables are complete and accepted | Confirm the scope is met |
| Obtain formal sign-off | Record agreement |
| Complete the financial and contractual close | Settle accounts and agreements |
| Hand over documentation, data, code, and equipment | Ensure continuity |
| Release the team and resources | Return people and tools |
| Write the final report | Summarize outcomes against the plan |
| Archive records | Preserve evidence |
| Hold a lessons-learned session | Improve future work |
| Plan benefits review | Check that value is realized |
Lessons Learned
A good lessons-learned review asks: What did we plan to do? What happened? Why was there a difference? What will we do the same or differently? Record the answers in a form that others can find. Do it as a blame-free exercise, in line with the psychological safety principle (Edmondson, 1999).
Benefits Realization
Benefits often appear after the project has ended. A post-implementation review, some months later, checks whether the intended benefits were achieved. In academic work, the equivalent is whether the research was published, cited, applied, or used by others.
Closing a Thesis or Dissertation
Submission is the project's closure. Make sure that you have met format requirements, deposited the thesis, archived your data and code, thanked those who helped, and obtained any required forms. Then do your own lessons-learned review. The defense or viva, where it applies, is a final gate.
Ending Well
Celebrate success, recognize contributions, and be honest about what did not work. Closing projects well builds reputation, trust, and the habit of learning.
CHAPTER 16