[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-165758-105":53,"doc-detail-165758-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","lessons-learned-template","Lessons Learned - Template","","Lessons Learned template for documenting project or program outcomes to support planning and continuous improvement. It outlines the purpose of capturing both successes and problems, explains when lessons should be collected (including ongoing logs and end-of-component summaries), and identifies required inputs for project initiation and charter drafting. It provides guidance on contributors, facilitation options, data sources such as meetings and change requests, and instructions for recording successes, issues, categorization, and future-facing impact.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":36,"@type":70,"position":76},"https://docshare.wps.com/template/forms/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/lessons-learned-template/165758/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/lessons-learned-template/165758.png","ImageObject",442,249,{"name":88,"@type":89},"Rowan","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/vnd.openxmlformats-officedocument.wordprocessingml.document","2026-09-25","2026-08-31",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of using this Lessons Learned template?","Question",{"text":108,"@type":109},"It supports new project/program planning by identifying problems and how they were handled, and by capturing what went well and why so others can apply those actions. It also helps gather feedback by identifying team members involved.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"When should lessons learned be collected during the project or program lifecycle?",{"text":113,"@type":109},"Lessons learned should be collected throughout the project/program, not only at closure. For programs, lessons should be collected and summarized at the end of each component project.",{"name":115,"@type":106,"acceptedAnswer":116},"How should lessons learned be organized in the report?",{"text":117,"@type":109},"Lessons should be categorized consistently to enable retrieval and trend analysis. Issues can be categorized to help readers apply lessons to their process, document, or lifecycle phase, and project phases/program phases should align with the provided options.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},165758,1788176523,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":35,"category_name":36,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":76,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":125,"read_time":79},1099514067415,"https://ap-avatar.wpscdn.com/avatar/100002539d78ffe74a7?x-image-process=image/resize,m_fixed,w_180,h_180&k=1779092875211072502","\u0003\n\u0003Lessons Learned\u0004\n\u0003[Insert Project/Program Name]\u0004\n\u000f\u0004\nPurpose of Lessons Learned\nThis document may be used as part of new project/program planning for similar projects/programs in order to determine what problems occurred and how those problems were handled and may be avoided in the future. Additionally, this document details what went well with the project/program and why, so that other project/program managers may capitalize on these actions. Project/program managers may also use this document to determine who the team members were to solicit feedback for planning their projects/programs in the future.\nWhile the lessons learned report is part of the PMO Group’s project/program closure process, lessons learned should be collected throughout the project/program. A log for lessons learned generated throughout the project/program can added to the \u0013 HYPERLINK \"https://uwaterloo.ca/vpaf-project-management-office/methodologies/project-management/planning/raid-log\" \u0014RAID log\u0015. If this is for a program, lessons learned should have been collected and summarized at the end of each of the program component projects as well.\nReview of lessons learned is a required input to project initiation/program definition and drafting the project/program charter.\nLessons Learned Contributors\nInput into the lessons learned may come from many different sources including, but not limited to, project/program manager, project/program team, subject matter experts within business unit(s), and other key stakeholders (such as staff, students, faculty).\nIt is recommended that lessons learned be facilitated by a third party who was not involved with the project/program, who would be the author of this report. PMO resources are available to facilitate lessons learned.\nInstructions:\nReview project/program documentation for lessons learned information. Potential sources include: lessons learned log, meeting minutes, change requests.\nConduct \u0013 HYPERLINK \"https://uwaterloo.ca/vpaf-project-management-office/lessons-learned-meeting\" \u0014lessons learned meeting\u0015. This meeting is best facilitated by a third-party as appropriate. PMO Resources are available to facilitate lessons learned. \u0013 HYPERLINK \"https://uwaterloo.atlassian.net/servicedesk/customer/portal/2221\" \u0014Contact the PMO to request support\u0015.\nA survey can be conducted to better facilitate collection of lessons learned. The PMO Group provides a standardized survey, delivered via web-form. \u0013 HYPERLINK \"https://uwaterloo.atlassian.net/servicedesk/customer/portal/2221\" \u0014Contact the PMO to request support\u0015.\nDocument the key successes and issues for the report. Ensure to categorize issues to aid readers of the report in applying the lesson to their process, document, or lifecycle phase.\nNext Steps\nOnce the Lessons Learned Summary has been completed the key learnings will be included in the Closure Report. It is also recommended that lessons learned be presented to other projects/programs where there may be potential application to the project/program in planning or execution. Please enter your Lessons Learned information into the document repository or \u0013 HYPERLINK \"https://uwaterloo.atlassian.net/servicedesk/customer/portal/2221\" \u0014contact the PMO\u0015 to ensure your lessons learned are available in the Lessons Learned repository so that they are available for review during project/program initiation for other similar projects/programs.\nSummary\nInstructions: Provide a brief description of the project/program for context. Briefly summarize the key findings from the lessons learned effort for use on other projects/programs. Identify key success factors and major issues, as well as the potential impacts of each that should be considered in the future.\n[Insert Summary]\nLessons Learned Approach\nInstructions: Lessons learned are documented throughout the project/program lifecycle. How they are collected and documented is part of project/program planning. Refer to the Project/Program Management Plan for this information and expan","cbCaioOJcVk92PIj","https://ap.wps.com/l/cbCaioOJcVk92PIj","docx",149037,10,"English","# Purpose of Lessons Learned\n## Lessons Learned Contributors\n## Instructions\n## Next Steps\n# Summary\n# Lessons Learned Approach\n# Lessons Learned\n## Process Improvement Recommendations","[{\"question\":\"What is the purpose of using this Lessons Learned template?\",\"answer\":\"It supports new project/program planning by identifying problems and how they were handled, and by capturing what went well and why so others can apply those actions. It also helps gather feedback by identifying team members involved.\"},{\"question\":\"When should lessons learned be collected during the project or program lifecycle?\",\"answer\":\"Lessons learned should be collected throughout the project/program, not only at closure. For programs, lessons should be collected and summarized at the end of each component project.\"},{\"question\":\"How should lessons learned be organized in the report?\",\"answer\":\"Lessons should be categorized consistently to enable retrieval and trend analysis. Issues can be categorized to help readers apply lessons to their process, document, or lifecycle phase, and project phases/program phases should align with the provided options.\"}]","Lessons Learned - Template | DOCX"]