QuestionPunkQuestionPunk
無料で始める
すべてのテンプレート
Developer & Engineering

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.

このテンプレートを使うほかのテンプレートを見る

設問の例

テンプレートの内容をプレビューできます。すべての設問は公開前に自由に編集できます。

全22問・約10分
Q01
メッセージ

Welcome to the Incident Postmortem Survey. This survey takes approximately 8–10 minutes and asks about your experience during a specific recent incident. Your responses are confidential, reported only in aggregate, and will be used to improve our response and communication processes. Participation is voluntary and you may stop at any time. There are no right or wrong answers—we value your honest perspective.

Q02
選択式

What was your primary role during this incident?

  • Incident commander
  • Technical responder
  • Communications/PR
  • Customer support
  • Leadership/Executive
  • Stakeholder or observer
Q03
プルダウン

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
Q04
オピニオンスケール

How would you rate the timeliness of communications during the incident?

スケール: 1 – 7
最小:Very poor最大:Excellent
Q05
オピニオンスケール

How satisfied are you with the timeliness of the post-incident review?

スケール: 1 – 7
最小:Not at all satisfied最大:Extremely satisfied
Q06
選択式

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)
Q07
自由回答（長文）

Based on your responses in this survey, is there anything else you'd like to share about this incident or our response process?

Q08
選択式

Which department or group are you part of?

  • Engineering
  • SRE/Operations
  • Security
  • Support
  • Product/PM
  • Communications/PR
  • Leadership/Executive
  • Other
Q09
メッセージ

Thank you for completing this survey. Your feedback directly informs our incident response improvements and will be reviewed by the postmortem team.

Q10
プルダウン

Which area was primarily impacted by this incident?

  • Customer-facing systems
  • Internal tools
  • Data/analytics
  • Infrastructure/network
  • Security
  • Compliance/regulatory
  • Other
Q11
選択式

Did the team follow a documented runbook during this incident?

  • Yes, fully followed
  • Partially followed
  • No, deviated from runbook
  • No runbook exists
Q12
オピニオンスケール

How would you rate the clarity and accuracy of communications during the incident?

スケール: 1 – 7
最小:Very poor最大:Excellent
Q13
オピニオンスケール

To what extent do you agree that action items from this incident were clearly defined with accountable owners?

スケール: 1 – 7
最小:Strongly disagree最大:Strongly agree
Q14
AIインタビュー

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.

Q15
プルダウン

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
Q16
自由回答（長文）

If applicable, what is the name or ID of the incident you are referencing?

Q17
オピニオンスケール

Overall, how effective were the corrective actions taken during this incident?

スケール: 1 – 7
最小:Not at all effective最大:Extremely effective
Q18
オピニオンスケール

How would you rate the frequency of stakeholder updates during this incident?

スケール: 1 – 7
最小:Far too infrequent最大:Far too frequent
Q19
オピニオンスケール

How confident are you that the identified actions will prevent a similar incident within the next 6 months?

スケール: 1 – 7
最小:Not at all confident最大:Very confident
Q20
プルダウン

Which region best describes your primary working time zone?

  • Americas
  • EMEA
  • APAC
  • Other/Multiple
Q21
自由回答（長文）

What were the top blockers or obstacles to achieving a faster resolution?

Q22
ランク付け

Rank the following communication channels from most to least effective during this incident.

  1. Slack/Chat
  2. Email
  3. Incident tool/Timeline
  4. Video bridge
  5. Status page
  6. 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 Template

This 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

よくあるご質問

「Incident Response Postmortem & Communication Effectiveness Survey」テンプレートにはどのような設問が含まれていますか？

すぐに使える設問が22問含まれており、最初の設問は次のとおりです：「Welcome to the Incident Postmortem Survey. This survey takes approximately 8–10 minutes and asks about your experience…」・「What was your primary role during this incident?」・「Approximately how long did it take from detection to the start of a coordinated response?」。すべての設問は上でプレビューでき、自由に編集できます。

このアンケートの回答にはどのくらい時間がかかりますか？

回答者は通常、22問を約10分で回答し終えます。

テンプレートは編集できますか？

はい。公開前であれば、すべての設問、選択肢、順序を編集できます。設問の追加や削除のほか、調査の目的に合わせた作り直しをAIエディターに依頼することもできます。

このテンプレートは無料で使えますか？

はい。エディターで開けば、すぐに編集を始められます。お試しにアカウントは不要で、無料プランでアンケートを公開できます。

公開の準備はできましたか？

このテンプレートをエディターで開いてみてください。最初の回答者が目にする前に、すべてを自由に変更できます。

このテンプレートを使う無料で始める

関連テンプレート

似たテーマのほかの調査もご覧ください。

すべて見る
Developer & Engineering

Developer Productivity & AI Tooling Adoption Survey

Measures developer productivity, AI coding tool adoption and barriers, code quality practices, and professional growth for engineering teams. Designed for 6–8 minute completion with branching logic for AI tool users vs. non-users.

テンプレートを見る
Developer & Engineering

Incident Communication & Stakeholder Update Survey

Evaluates the timeliness, clarity, channel effectiveness, and overall quality of incident communications from stakeholders' perspectives to identify actionable improvements in crisis response.

テンプレートを見る
Developer & Engineering

Incident Communication Effectiveness Survey

Measures customer perceptions of clarity, timeliness, and trust in crisis and outage communications. Designed for B2B operations teams seeking to benchmark and improve incident response communication.

テンプレートを見る
Developer & Engineering

Post-Incident Trust & Communication Assessment

Measures incident impact, communication effectiveness, and trust recovery across stakeholder roles. Designed for internal post-incident reviews to identify systemic improvement priorities.

テンプレートを見る
Developer & Engineering

Incident Communication Effectiveness Assessment

Evaluates stakeholder perceptions of incident communication timeliness, clarity, frequency, and helpfulness to identify priority improvements in crisis communication workflows.

テンプレートを見る
Developer & Engineering

Crisis Response Evaluation and Debrief Survey

Gathers structured feedback from employees or stakeholders on how your organization communicated and led through a specific crisis — speed, clarity, and trust in decision-making — plus an AI follow-up that reconstructs the moment communication broke down or worked well. Built for comms, HR, and leadership teams running a post-incident debrief.

テンプレートを見る