yo, I am working on post mortem for very complex project incl multiple parties and…
- User
yo, I am working on post mortem for very complex project incl multiple parties and different teams before post mortem and instead of gathering 50 people in one room I would like to conduct survey with some questions so that different stkh could respond honestly and provide there opninins on what was good and what was bad
Assistant
Hey! That's a smart move — conducting a survey before a large post-mortem with 50+ stakeholders is a great way to gather honest, diverse input without the noise and groupthink that can happen in big meetings. It also helps you identify key themes and pain points in advance, so the actual post-mortem becomes more focused and productive.
Here’s a structured approach and a sample survey you can adapt:
🎯 Goals of the Pre-Post-Mortem Survey
- Gather honest feedback anonymously (if possible).
- Identify what went well and what didn’t across teams and phases.
- Surface systemic issues (process, communication, tools, ownership).
- Capture suggestions for improvement.
- Prepare data-driven talking points for the actual post-mortem.
✅ Survey Design Tips
- Keep it anonymous to encourage honesty.
- Use a mix of quantitative (ratings) and qualitative (open-ended) questions.
- Limit to 10–15 minutes to complete.
- Send via tools like Google Forms, Typeform, or Microsoft Forms.
- Set a clear deadline and send a reminder.
📝 Sample Pre-Post-Mortem Stakeholder Survey
🌟 Introduction
Thank you for taking the time to share your feedback. This survey aims to understand your perspective on the recent [Project Name] delivery. Your input will help us improve future cross-team collaboration and execution. All responses are anonymous unless you choose to share your name.
1. How would you rate the overall success of the project?
(1 = Not successful at all, 5 = Highly successful)
🔘 1 ⭕ 2 ⭕ 3 ⭕ 4 ⭕ 5
2. What do you think went well? (Open-ended)
Please share 1–3 things that worked well — e.g., team collaboration, planning, tools, communication, leadership, etc.
3. What were the biggest challenges or pain points? (Open-ended)
Think about process, communication, dependencies, timelines, decision-making, tools, or team dynamics.
4. How effective was communication across teams?
(1 = Very poor, 5 = Excellent)
🔘 1 ⭕ 2 ⭕ 3 ⭕ 4 ⭕ 5Optional: Briefly explain your rating.
5. Were roles and responsibilities clearly defined and understood?
✅ Yes, mostly
🟡 Somewhat
❌ No, not reallyComments?
6. How well were risks and blockers identified and addressed?
(1 = Not at all, 5 = Extremely well)
🔘 1 ⭕ 2 ⭕ 3 ⭕ 4 ⭕ 5Any specific examples?
7. Did you have the tools, information, and support needed to do your job effectively?
✅ Yes
🟡 Partially
❌ NoPlease elaborate.
8. How would you rate cross-team collaboration?
(1 = Very poor, 5 = Excellent)
🔘 1 ⭕ 2 ⭕ 3 ⭕ 4 ⭕ 5What helped or hindered collaboration?
9. Were timelines and milestones realistic and respected?
✅ Yes
🟡 Mostly
❌ NoAny thoughts on scheduling or scope?
10. What one change would have made the biggest positive impact on this project? (Open-ended)
11. Would you be open to a follow-up conversation to dive deeper into your feedback?
✅ Yes (please provide contact)
❌ No
(Optional field for email/name if yes)
12. Any other comments or reflections? (Optional open box)
📊 After the Survey
- Analyze responses — look for patterns (e.g., 70% flagged communication as poor).
- Group feedback by theme: communication, planning, ownership, tools, etc.
- Summarize key insights to present at the post-mortem.
- Use quotes (anonymized) to highlight real concerns or wins.
- Structure the post-mortem meeting around the top 3–5 issues and successes.
💡 Pro Tips
- Share a high-level summary of survey results with participants before the post-mortem.
- In the meeting, focus on solutions, not blame.
- Assign action items with owners and timelines.
- Consider segmenting feedback by team/function if you can (e.g., engineering vs. product vs. ops).
Let me know if you want a ready-to-use Google Form template or help analyzing the results later. You got this! 👏
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.