Keep the finding specific
Example retrospective comments describe waiting for an external dependency that had no early owner.
Operations and internal services / Survey guide
Operations and internal services · Practical field guide
Project retrospective survey
Capture lessons before the next project repeats the same friction.
Opens product registration. Example questions are not imported automatically.
QUESTION WORDING LAB
Assumes a positive answer
Would you agree that project retrospective was a completely positive experience?
Ask about the actual situation
What helped this project move forward?
The initial wording assumes a positive evaluation. The revised question asks about the actual situation so a respondent can describe difficulty, uncertainty, or a different experience.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Choose an action to test
Add an early dependency check and an owner to the next project kickoff.
Check the experience again
After testing the action, revisit this original observation: Example retrospective comments describe waiting for an external dependency that had no early owner. Repeat the relevant experience prompts with people who encountered the change. Compare specific explanations and sample differences; do not claim causation from the before-and-after responses.
Read the answers carefully
What the answers cannot tell you.
Discuss system conditions without using the survey to assign blame.
Example retrospective comments describe waiting for an external dependency that had no early owner. This is an illustrative interpretation problem rather than a real customer result. Add an early dependency check and an owner to the next project kickoff.
From question to next step
Make the feedback useful.
Set the decision
Write down the decision you want this questionnaire to support: capture lessons before the next project repeats the same friction.
Invite relevant voices
Invite people who experienced the relevant situation. Explain response handling and include an optional skip or not-applicable route. Discuss system conditions without using the survey to assign blame.
Choose an action
Add an early dependency check and an owner to the next project kickoff.
A useful starting point
A questionnaire for project retrospective.
Capture lessons before the next project repeats the same friction. Choose the questions that fit the experience you are investigating; avoid asking people to evaluate a step they did not encounter.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
What helped this project move forward?
Identify a practice or coordination condition worth retaining on later projects. Compare it with the actual project record before attributing delivery progress to that factor.
Where did coordination break down?
Locate the handoff or decision point where coordination failed, including who needed what context. Investigate the process without converting the answer into a personal blame rating.
What single practice should the next project change?
Choose one feasible practice to change and define where it would apply next time. A suggested improvement remains a hypothesis until tested in another project.
Which dependency was discovered later than expected?
Find a dependency revealed after planning decisions had been made. Improve early discovery or notification while distinguishing unforeseeable changes from information that was available earlier.
What early check would have prevented repeated work?
Identify a check that could expose a repeated-work risk before execution. Validate it against the project sequence rather than claim hindsight proves it would have prevented failure.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. What helped this project move forward? Where did coordination break down? What single practice should the next project change? Which dependency was discovered later than expected? What early check would have prevented repeated work?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| What helped this project move forward? | Short open text | Let people explain the experience in their own words. Review this answer for: what helped this project move forward. |
| Where did coordination break down? | Short open text | Let people explain the experience in their own words. Review this answer for: where did coordination break down. |
| What single practice should the next project change? | Short open text | Let people explain the experience in their own words. Review this answer for: what single practice should the next project change. |
| Which dependency was discovered later than expected? | Short open text | Let people explain the experience in their own words. Review this answer for: which dependency was discovered later than expected. |
| What early check would have prevented repeated work? | Short open text | Let people explain the experience in their own words. Review this answer for: what early check would have prevented repeated work. |
Make questions optional where appropriate. If you add a rating scale, label its endpoints, keep one idea per question, and retain a follow-up for reasons. These examples are not a validated measurement instrument.
Before you send it
Check what your wording assumes.
Would you agree that project retrospective was a completely positive experience?
What helped this project move forward?
The initial wording assumes a positive evaluation. The revised question asks about the actual situation so a respondent can describe difficulty, uncertainty, or a different experience.
Build with SurveyTeams
Build your own project retrospective questionnaire.
Use these examples to draft your questionnaire. Create a survey draft, add questions, and check the respondent preview in SurveyTeams. Additional features depend on your account and plan.
Create your survey in SurveyTeams
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗Before you send it
Questions, answered.
What should I learn from this project retrospective questionnaire?
Capture lessons before the next project repeats the same friction. Start with one decision you can act on rather than using the survey to confirm a preferred answer.
How should I interpret answers to “Where did coordination break down?”?
Read this answer for the concrete issue behind the response. Discuss system conditions without using the survey to assign blame. Compare specific explanations instead of reducing every response to one average.
What would a practical next action look like?
Add an early dependency check and an owner to the next project kickoff. This is an example action to investigate, not a guaranteed improvement.
When should I send this questionnaire?
Ask after respondents have experienced the specific situation in the first prompt: “What helped this project move forward?” Allow enough time after a proposed change for people to experience it before repeating the questionnaire.
What should I check after changing the process?
After testing the action, revisit this original observation: Example retrospective comments describe waiting for an external dependency that had no early owner. Repeat the relevant experience prompts with people who encountered the change. Compare specific explanations and sample differences; do not claim causation from the before-and-after responses.
Can I use these questions in SurveyTeams?
Copy the questions or download TXT, CSV, JSON, or a Markdown worksheet and adapt them in your own survey. The product CTA opens registration and does not import the example. Verify the features and terms available in your account.
Continue exploring