QuestionPunkQuestionPunk
Start free
All templates

Project Retrospective: Root Causes & Process Fixes

Captures what went well, what broke, and why on a just-completed project, then surfaces the process changes the team would realistically adopt. An AI follow-up reconstructs the actual sequence of events behind the biggest setback instead of settling for a vague 'communication issues' answer. Built for project leads and PMOs running structured retros.

Use this templateBrowse more templates

Sample questions

A preview of what’s in the template. Every question is editable before you launch.

11 questions · ~6 min
Q01
Message

Thanks for taking a few minutes to reflect on this project. Your honest read on what worked, what didn't, and what should change helps us actually fix things next time. About 6-8 minutes.

Q02
Opinion ScaleRequired

Overall, how successful was this project relative to its original goals (scope, timeline, quality)?

Scale: 1 – 7
Min:Complete failureMax:Complete success
Q03
MatrixRequired

Rate how each part of the project went.

7 rows × 3 columns
  • Planning & scope definition
  • Stakeholder communication & alignment
  • Resourcing & staffing
  • Technical execution
  • Testing & quality assurance
  • +2 more
Columns: Went poorly · Went okay · Went well
Q04
Multiple ChoiceRequired

Which of these contributed to the project's biggest setbacks? Select all that apply.

  • Unclear or shifting requirements
  • Scope creep
  • Insufficient staffing or skills
  • Poor communication across teams
  • Unrealistic timeline or estimates
  • Technical debt or legacy systems
  • Lack of stakeholder buy-in
  • Dependency delays from other teams
  • Unclear ownership or decision rights
Q05
Long TextRequired

In your own words, describe the single most significant failure or near-miss moment on this project — what happened, and when did the team first notice something was off?

Q06
RankingRequired

Rank these potential process changes from most to least valuable for this team to adopt on the next project. (Template note: replace with your own candidate process changes before launching, based on internal input.)

  1. Add a formal scope-freeze milestone before build starts
  2. Hold a weekly cross-team sync on dependencies
  3. Build explicit buffer time into estimates
  4. Run a lightweight retro after every sprint, not just at the end
  5. Clarify ownership with a RACI-style breakdown
  6. Increase automated test coverage before release
  7. Improve handoff documentation between teams
Drag to rank
Q07
AI Interview

Reconstruct the actual sequence of events behind the single biggest setback the respondent described: what decision or signal came first, who noticed it, how long it took to escalate, and what was tried before it became a real problem. If they named a process change they ranked highest, probe what would concretely block their team from adopting it next time and what would need to be true for it to actually stick.

Q08
Opinion ScaleRequired

Realistically, without extra management pressure, how likely is your team to actually adopt the process change you ranked highest?

Scale: 0 – 10
Min:Not at all likelyMax:Extremely likely
Q09
Multiple Choice

Which best describes your role on this project?

  • Project or program lead
  • Individual contributor / builder
  • Product or business owner
  • Engineering or technical lead
  • QA or testing
  • Prefer not to say
Q10
Multiple Choice

How long were you involved with this project?

  • Less than 1 month
  • 1-3 months
  • 4-6 months
  • More than 6 months
  • Prefer not to say
Q11
Message

That's everything — thank you for the candid feedback. Responses across the team will be compiled into a root-cause summary and a short list of process changes for leadership to review before the next project kicks off.

What’s included

  • AI follow-ups

    Adaptive probes on open-ended answers that pull out detail a static form would miss.

  • Attention checks

    Built-in safeguards against rushed answers and low-quality respondents.

  • AI-drafted copy

    Wording, ordering, and branching written by the AI — tuned to your research goal.

  • Auto report

    Themes, quotes, and a plain-English summary write themselves once responses come in.

How it compares

We reviewed the closest templates from other survey tools. Here’s what they do well — and where this template goes further.

Why this template

  • Includes a dedicated AI follow-up interview block that reconstructs the actual sequence of events behind the biggest setback, instead of stopping at a surface-level 'communication issues' answer
  • Combines quantitative rating (rating-scale, matrix) with open-ended failure analysis (open-text) and a ranking exercise for prioritizing realistic process fixes
  • Asks a grounded feasibility question — how likely the team is to act on changes without extra management pressure — which static templates don't probe
  • Segments respondents by role and project tenure (multiple-choice) so PMOs can weight perspectives when reading the auto-generated report

SurveyMonkey

Project Retrospective Questions Template

A fielding-ready retrospective template covering standard post-project reflection questions. It's built on SurveyMonkey's established survey infrastructure with broad question-type support and easy distribution. However, it appears to be a fixed question set rather than one that adapts based on a respondent's answers.

What it does well

  • Ready-to-deploy template on a mature survey platform
  • Likely covers standard retrospective categories (what went well/poorly)
  • Easy to customize question wording within SurveyMonkey's editor

Where it falls short

  • No adaptive AI follow-up to dig into vague answers like 'communication issues'
  • No voice AI interview or guided screen-share task option
  • No automated per-response quality scoring or transparent AI prompt methodology

Jotform

Project Changes Report Form Template

This is a static form for logging project changes/reports rather than a purpose-built root-cause retrospective survey, so it's a partial and somewhat tangential comparison. It benefits from Jotform's flexible form-builder and integrations. It's not designed to surface why a setback happened, just to record what changed.

What it does well

  • Highly customizable drag-and-drop form fields
  • Good for structured documentation/reporting workflows
  • Integrates with Jotform's broader app ecosystem

Where it falls short

  • Not designed as a reflective retrospective survey — closer to a change-log form
  • No adaptive AI questioning to reconstruct event sequences
  • No built-in scoring, AI interview, or auto-generated analysis report

Ready to launch?

Open this template in the editor. Every part is yours to change before the first respondent sees it.

Use this templateStart free