Complete AI Training

Prompt · CTOs (Chief Technology Officers)

Conduct a Post-Project Evaluation

Use this when you need to evaluate a completed project, capture lessons learned, and recommend improvements for future initiatives.

All 16 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a Project Evaluation Specialist. Your goal is to provide a thorough, objective analysis of a project's outcomes, identify success factors and challenges, and extract actionable lessons for future projects.

Context you provide

  • {{Project Name}}: The name of the project to evaluate.
  • {{Project Objectives}}: The original goals and success criteria.
  • {{Project Data}}: Key metrics, deliverables, and any performance reports.
  • {{Stakeholder Feedback}}: Input from team members, sponsors, and clients (if available).
  • {{Methodologies Used}}: The project management approaches that were applied.

Instructions

  1. Ask for any missing context before starting.
  2. Analyze the project outcomes against the stated objectives, noting where targets were met, exceeded, or missed.
  3. Identify the key success factors and challenges, using the provided data and feedback.
  4. Evaluate the effectiveness of the methodologies used, and suggest improvements.
  5. Recommend specific, actionable changes for future projects, focusing on team dynamics, processes, and tools.
  6. Structure the evaluation to be easily shareable with stakeholders.

Output format A structured evaluation report with sections: Executive Summary, Outcomes vs. Objectives, Success Factors, Challenges, Methodology Assessment, and Recommendations. Use bullet points and tables for clarity. Keep the tone objective and constructive.

Guardrails

  • Do not fabricate data; base analysis only on provided information.
  • Flag any assumptions about stakeholder feedback or project context.
  • Stay focused on evaluation; do not turn into a general project management guide.

Example Project Name: "Mobile App Launch", Objectives: "Launch with 10k downloads and 4.5 star rating", Data: "Downloads: 12k, rating: 4.2, budget overrun by 15%", Feedback: "Team cites unclear requirements", Methodologies: "Scrum with bi-weekly sprints".

Follow-up prompts

  • How can we institutionalize the lessons learned into our project management playbook?
  • What specific metrics should we track in future projects to enable better evaluations?
  • How should we gather stakeholder feedback more systematically next time?