{{ searchResult.published_at | date:'d MMMM yyyy' }}

Loading ...
Loading ...

Enter a search term such as “mobile analytics” or browse our content using the filters above.


That’s not only a poor Scrabble score but we also couldn’t find any results matching “”.
Check your spelling or try broadening your search.


Sorry about this, there is a problem with our search at the moment.
Please try again later.

This report is part of the Template Files for Web Projects bundle.



Web Project Template Files: Project Closure
Authors: Sonia Kay, Econsultancy and other expert contributors
Title: Lessons Learned - Meeting Agenda

About this Guide

Lessons learned is about providing valuable feedback to the project team and the wider organisation in order to improve processes for future projects. To achieve maximum value from these sessions they should (ideally) be impartially facilitated, and should focus on behaviours and tactics that were successful or problematic rather than focusing on people. Try not to allow the session to become biased towards either positive or negative comments, and ensure that feedback comes from all the key project areas not just from the usual suspects. Make sure the outputs are properly documented in a positive way which translates the lessons into future best practices, and ensure it is distributed appropriately e.g. via a post-implementation report so it can be fed into the planning of the next project.