Project Lessons Learned Document Template
Use as a prompt to get your answer, a goal to complete a complex task, or a reusable skill for your library.
This prompt is designed to assist project managers and teams in creating a structured lessons learned document. The goal is to capture valuable insights and experiences from a completed project to improve future performance and decision-making. This template helps teams systematically review what went well, what didn't, and how processes can be enhanced. It ensures that important knowledge is retained and leveraged for continuous improvement.
{
"role": "You are a project manager with expertise in conducting post-project evaluations and capturing lessons learned.",
"goal": "Develop a comprehensive lessons learned document template for [project name] to systematically capture insights and experiences from the project.",
"context": [
"Include sections for project overview, objectives, and scope.",
"Provide areas to document successes, challenges, and recommended improvements.",
"Ensure the template encourages team participation and open communication.",
"Factor in the importance of aligning lessons with organizational goals and future projects."
],
"output": [
"An introduction section with project details and objectives.",
"A section for documenting project successes and effective strategies.",
"A section for identifying challenges and areas for improvement.",
"Recommendations for future projects and action items for implementation."
],
"toneStyle": "Professional, structured, and reflective.",
"constraints": [
"Ensure the template is adaptable to different project types and sizes.",
"Avoid overly technical language\u2014keep it accessible to all team members."
],
"startingQuestions": "Before beginning, determine whether missing information would materially improve the result. If so, ask me up to [3] concise clarifying questions in a single message and wait for my answers. Do not ask for information already provided. If no clarification is needed, proceed immediately.",
"followUpQuestions": "After presenting the result, only if resolving which lesson category or future action to clarify would materially improve its usefulness, ask up to [3] concise follow-up questions about that decision. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
"successCriteria": [
"The lessons template distinguishes successes, challenges and actionable recommendations grounded in the project's actual experience.",
"The response delivers an introduction section with project details and objectives; a section for documenting project successes and effective strategies.",
"The response also delivers a section for identifying challenges and areas for improvement; recommendations for future projects and action items for implementation.",
"The result respects these original limits: ensure the template is adaptable to different project types and sizes; avoid overly technical language\u2014keep it accessible to all team members. Factual claims and examples or results presented as real are supported by supplied or verifiable evidence; missing evidence is identified without inventing results.",
"Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
]
}