Get Started Free
📊 Survey & Market Research

Free Project Retrospective Survey Template

A structured research retrospective: project context, facilitator and participants, goal recap, what worked, what dragged, execution quality, lessons, unexpected insights, next actions and owners.

~6 min
Team lessons
Live Preview

Quick answer

A structured research retrospective: project context, facilitator and participants, goal recap, what worked, what dragged, execution quality, lessons, unexpected insights, next actions and owners.

💡

About this template

Research lessons evaporate in the delivery call. This retrospective keeps them: fifteen fields covering project context, retrospective date, facilitator, participants, a goal recap, what worked, what did not work, quality of execution, key lessons, unexpected insights, next-step actions, the owner of each action, action due date, whether the objective was met and a stop-doing item. Answers are exportable and themable, so two quarters of retrospectives turn into a practice list rather than a series of meetings.

🖥️

Live Preview

Live form preview — fill it in to see how each answer is captured and exported.

loading...
…
Fill it in to see how responses flow.
📦

What's Included

Everything you need to run this template.

1

Delivery review

Goal recap against what actually happened.

2

Work and drag

What worked, what did not, where execution quality slipped.

3

Lessons and insight

Key lessons plus the unexpected finding nobody planned for.

4

Next actions

Next-step actions with owners and due dates.

🧭

How It Works

From copy to deliverable in four steps.

1

Use this template

Copy the retro survey into your FormLM workspace — free.

2

Run at project close

Collect while details are fresh.

3

Theme the responses

Group answers by recurring friction.

4

Assign next steps

Put owners on the top changes.

👥

Who Is This For

Pick your role — see how it fits your workflow.

1

Delivery and product teams

Close sprints with recorded learning.

2

Consultants after engagements

Hand the client a lessons list.

3

Program managers

Roll retrospectives up across projects.

⭐

Key Features

What makes this template work as a professional deliverable.

📝

Sample Questions Inside

A preview of real questions — the full version lets you customize every field.

  1. Project Context (open)
  2. Retrospective Date (text)
  3. Facilitator (text)
  4. Participants (open)
  5. Goal Recap (open)
  6. What Worked (open)
❓

Frequently Asked Questions

When exactly should the retro survey go out?
Within days of close — memory decays fast and the next project starts sooner than you think.
Anonymous or attributed?
Anonymous collection with attributed actions; candor needs safety, but the improvement owner still gets named.
How many responses make a valid retro?
Most of the project team; a two-person answer set is a conversation, not a retrospective.
What do we do with repeated themes?
A theme recurring across projects is a process issue — promote it to a standing improvement with an owner.
Is this the same as client feedback?
No — it faces the delivering team; client-side feedback has its own survey after delivery.
Can it run per sprint as well as per project?
Yes — copy per cadence; keep question wording identical so trends emerge across sprints.

Bank the lesson before it fades

Run the retro survey at close and assign the fixes — free.