Incident Response Postmortem & Communication Effectiveness Survey
Collects structured feedback from incident responders and stakeholders to evaluate response execution, communication quality, and accountability of follow-up actions. Use after any significant incident to identify process improvements.
샘플 질문
템플릿에 포함된 내용을 미리 확인해 보세요. 모든 질문은 설문 공개 전에 자유롭게 수정할 수 있습니다.
What was your primary role during this incident?
- Incident commander
- Technical responder
- Communications/PR
- Customer support
- Leadership/Executive
- Stakeholder or observer
Approximately how long did it take from detection to the start of a coordinated response?
- Under 5 minutes
- 5–15 minutes
- 16–30 minutes
- 31–60 minutes
- 1–2 hours
- More than 2 hours
- I don't know
How would you rate the timeliness of communications during the incident?
How satisfied are you with the timeliness of the post-incident review?
Which single change would most improve incident communications next time?
- Clearer audience owners
- Preset update cadence
- Single source of truth
- Fewer channels
- More status detail
- More executive summaries
- Automated stakeholder lists
- Other (please specify)
Based on your responses in this survey, is there anything else you'd like to share about this incident or our response process?
Which department or group are you part of?
- Engineering
- SRE/Operations
- Security
- Support
- Product/PM
- Communications/PR
- Leadership/Executive
- Other
Thank you for completing this survey. Your feedback directly informs our incident response improvements and will be reviewed by the postmortem team.
Which area was primarily impacted by this incident?
- Customer-facing systems
- Internal tools
- Data/analytics
- Infrastructure/network
- Security
- Compliance/regulatory
- Other
Did the team follow a documented runbook during this incident?
- Yes, fully followed
- Partially followed
- No, deviated from runbook
- No runbook exists
How would you rate the clarity and accuracy of communications during the incident?
To what extent do you agree that action items from this incident were clearly defined with accountable owners?
We'd like to explore your experience a bit further. An AI moderator will ask a couple of follow-up questions about the incident response and communication. Please respond in your own words.
How many years of experience do you have with incident response?
- Under 1 year
- 1–2 years
- 3–5 years
- 6–10 years
- 11+ years
If applicable, what is the name or ID of the incident you are referencing?
Overall, how effective were the corrective actions taken during this incident?
How would you rate the frequency of stakeholder updates during this incident?
How confident are you that the identified actions will prevent a similar incident within the next 6 months?
Which region best describes your primary working time zone?
- Americas
- EMEA
- APAC
- Other/Multiple
What were the top blockers or obstacles to achieving a faster resolution?
Rank the following communication channels from most to least effective during this incident.
- Slack/Chat
- Incident tool/Timeline
- Video bridge
- Status page
- Phone/SMS
포함된 기능
AI 후속 질문
정형화된 설문이 놓치는 세부 내용을, 주관식 답변에 맞춰 AI가 심층 질문으로 끌어냅니다.
주의력 확인 장치
성의 없는 답변과 저품질 응답자를 걸러내는 내장 안전장치입니다.
AI가 작성한 문안
문구, 질문 순서, 분기 로직까지 AI가 연구 목표에 맞춰 작성합니다.
자동 리포트
응답이 모이면 주요 주제, 인용문, 이해하기 쉬운 요약이 자동으로 작성됩니다.
다른 서비스와 비교
다른 설문 도구의 가장 유사한 템플릿을 검토했습니다. 그 도구들이 잘하는 점과, 이 템플릿이 한발 더 나아가는 지점을 정리했습니다.
이 템플릿을 선택하는 이유
- Combines structured incident-execution questions (role, impacted area, detection-to-coordination timeline, runbook adherence) with dedicated ratings for communication timeliness, clarity, and update frequency
- Includes a ranking question comparing communication channel effectiveness and opinion-scale items on action-item clarity and confidence in preventing recurrence
- Uses an AI follow-up interview to probe open-ended answers about blockers and improvement ideas rather than leaving them as static free-text
- Closes with reflective open-text and segmentation questions (department, experience level, time zone) so QuestionPunk's auto-generated report can break down findings by stakeholder group
SurveyMonkey
Incident Report Form TemplateThis is a general-purpose incident report form for logging basic details of an event (what happened, when, who was involved) rather than a structured postmortem instrument. It's fielding-ready out of the box and benefits from SurveyMonkey's broader analytics and distribution tools, but it doesn't specifically address communication-quality assessment or follow-up accountability. Best suited as an initial incident intake form rather than a post-incident retrospective.
잘하는 점
- Fielding-ready template usable immediately without customization
- Backed by SurveyMonkey's established survey infrastructure and reporting dashboards
- Customizable question set for basic incident logging
아쉬운 점
- Static question set with no adaptive AI follow-up probing on open-ended answers
- No structured multi-dimensional rating of communication timeliness, clarity, and frequency
- No published methodology or transparent prompt logic behind question design
설문을 공개할 준비가 되셨나요?
이 템플릿을 편집기에서 열어 보세요. 첫 응답자가 보기 전에 모든 부분을 원하는 대로 바꿀 수 있습니다.