Team & People
Incident Response Tabletop Exercise: Find Gaps in Your Plan and Contact List in 90 Minutes
Intermediate | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)
Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.
Run an incident response tabletop exercise in 90 minutes with four roles, reading a scenario step by step to decide who acts and who is told. The four roles are facilitator, management, frontline staff, and IT, and all you need is your own response plan and emergency contact list; attack methods are out of scope. The facilitator reads one situation at a time, each person notes what they would do in their role before discussing, and anything unclear or missing from the plan goes down as a gap found. No tabletop experience is needed: follow the examples and you finish with three gaps to fix, each with an owner and deadline, and an idea for the next scenario. Owners, deadlines, and a new scenario each time guard against a plan-recital quiz, missing frontline staff, gaps that never get fixed, and repeated scenarios. The whiteboard has four pages and ends with a KPT review, and the task board has five columns with 4 parent tasks of 3 subtasks each.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Incident Response Tabletop Board
How to use (4 pages): ① On page 1, set the aim, the four roles, and the ground rules (sections①–⑤) → ② On page 2, run the scenario by time and write decisions and contacts (sections⑥⑦) → ③ On page 3, line up the gaps, check pitfalls, and pick three to fix (sections⑧–⑫) → ④ On page 4, run a KPT review and set owners, deadlines, and the next scenario (sections⑬–⑮)
1/4 Set the aim and roles
① Aim and time (start writing here)
- Aim of the exercise e.g. Check that the plan and contact list work on the day, and find the gaps
- Time plan for 90 minutes e.g. Briefing 10 min, scenario 45, review 20, reflection 15
- Scenario to use (the prompt) e.g. Files in the shared folder will not open this morning. Skip attack methods and focus on how you decide once it has happened
② The four roles and what they do on the day
| Who | Role in the exercise | What to bring | |
|---|---|---|---|
| Facilitator, note-taker | e.g. Person from general affairs | e.g. Reads each situation and records decisions and gaps | e.g. Table ⑥ and a clock |
| Management | e.g. One executive | e.g. Decides whether to stop work and what to tell outsiders | e.g. List of business partners |
| Frontline rep | e.g. One person from a team that uses the files daily | e.g. Describes what they do on noticing, and when work stops | e.g. Work procedure notes |
| IT | e.g. In-house IT person (or the contact person if outsourced) | e.g. Explains how to check the situation and who to call at the vendor | e.g. Plan, emergency contact list, vendor contacts |
③ Rule 1 No blame
- Talk about the plan and the system, not the person, when judging a decision
- e.g. Ask "was the contact written down?" rather than "why didn't you call?"
- Senior staff follow the same rule
④ Rule 2 No hunting for answers
- If the plan is silent, writing that is enough
- e.g. The facilitator gives no answers and asks "what does the plan say?"
- Where people hesitate is where the gaps are
⑤ Rule 3 Keep records
- Write decisions, contacts, and hesitations on sticky notes on the spot
- e.g. The note-taker records in table ⑥ who decided what, in one line
- Page 4 uses the record to decide who fixes what
2/4 Run the scenario
⑥ Scenario by time, played by the four roles in ②
| What happened | Decision (who, what) | Contact | Gap found | |
|---|---|---|---|---|
| Discovery (0 min) | e.g. A frontline person reports that files in the shared folder will not open | e.g. Frontline decides whether to take the first step in the plan. IT asks about the situation | e.g. IT person | e.g. No night or holiday contact on the contact list |
| After 30 min | e.g. Another team has the same symptom. Delivery data is stored there too | e.g. IT decides how far to investigate the impact | e.g. Management and team leaders | e.g. The plan does not say who decides the scope of impact |
| After 1 hour | e.g. The maintenance vendor does not pick up the phone | e.g. Management decides whether to stop work | e.g. Maintenance vendor and a backup contact | e.g. Only one vendor contact person is listed |
| After half a day | e.g. A client asks about the delivery date | e.g. Management decides what to tell the client and when | e.g. Client contact and the in-house PR team | e.g. Nobody has settled the wording for outsiders or who approves it |
| Next morning | e.g. It is time to check whether data can be restored from backup | e.g. IT decides which point in time to restore to | e.g. Maintenance vendor and teams that use the data | e.g. Nobody has ever practiced restoring from backup |
⑦ How to run the scenario (about 9 min per row, 5 rows in 45 min)
- Read the situation The facilitator reads just one row of What happened from ⑥ e.g. Copy only the row read aloud into ⑥ and keep the next row hidden
- Write alone In 1 minute, write on a sticky note what you would do in your role e.g. IT: "Call the vendor, and if no answer, go to the backup contact"
- Discuss Line up the decisions of management, frontline, and IT, and check them against the plan and contact list e.g. Open the plan on the spot and point to where it says so
- Note the gaps Write what you hesitated over or what is not written down in the Gap found column of ⑥ e.g. "No next step when the vendor does not pick up"
3/4 Review the decisions
⑧ Line up the gaps from ⑥ (impact x ease of fixing)
Vertical axis: Impact (higher = bigger) / Horizontal axis: Ease of fixing (further right = easier)
- Big impact, hard to fix Plan it and fix it carefully, with a longer deadline. e.g. Nobody has practiced restoring from backup
- Big impact, easy to fix Fix first. Make these the candidates for ⑫. e.g. No night or holiday contact on the contact list
- Small impact, hard to fix Skip this time and check again in the next exercise. e.g. Procedures by team are not yet aligned
- Small impact, easy to fix Assign an owner on the spot and fix. e.g. An old team name remains in the plan
⑨ Pitfall 1 It turns into a quiz
- What happens: e.g. Only people who memorized the plan answer and the rest stay silent
- How to check: e.g. See whether all three roles (management, frontline, IT) appear in the decision column of ⑥
- How to prevent: e.g. Give no answers, and have everyone write on sticky notes before talking
- Check this time: e.g. Management made decisions in only 2 of 5 rows. Next time management speaks first
⑩ Pitfall 2 Leaving out frontline staff
- What happens: e.g. Only IT and management take part, so scenes where work stops never come up
- How to check: e.g. See whether the frontline representative in ② has a name and attended on the day
- How to prevent: e.g. Always invite one person from a team that uses the files daily
- Check this time: e.g. The frontline representative came and raised a delivery delay
⑪ Pitfall 3 Gaps never get fixed
- What happens: e.g. Only the record remains, and the same gap is found again at the next exercise
- How to check: e.g. Compare the last record with the Gap found column of ⑥
- How to prevent: e.g. Set an owner and deadline per gap in ⑭ and track them on the task board
- Check this time: e.g. The vendor contact gap from last time was still not fixed
⑫ Narrow to three gaps to fix (from the big impact, easy fix group in ⑧)
- Gap to fix 1 e.g. No night or holiday contact on the contact list
- Gap to fix 2 e.g. Nobody has settled the wording for outsiders or who approves it
- Gap to fix 3 e.g. The plan does not say who decides the scope of impact
4/4 Fix the gaps and move on
⑬ Review the exercise after ⑫ with KPT
Keep Continue
- e.g. Everyone wrote on sticky notes first, so everyone spoke
- e.g. The note-taker recorded each decision in one line
Problem Issue
- e.g. We ran out of time at the 1-hour scene
- e.g. The maintenance vendor was not there
Try Next steps
- e.g. Next time, have the vendor join for just 30 minutes
- e.g. Cut the scenario to 4 rows and give each row more time
⑭ What to fix, owner, deadline (the 3 from ⑫ and 1 Try from ⑬)
| What to fix | Owner | Deadline | |
|---|---|---|---|
| Gap 1 | e.g. Add night and holiday contacts to the emergency contact list | e.g. Person from general affairs | e.g. Friday of week 1 |
| Gap 2 | e.g. Settle the wording for outsiders and who approves it | e.g. Management | e.g. Friday of week 2 |
| Gap 3 | e.g. Write in the plan who decides the scope of impact | e.g. IT person | e.g. Friday of week 2 |
| One from Try | e.g. Invite the maintenance vendor to the next exercise | e.g. Facilitator | e.g. The day the next notice goes out |
⑮ Idea for the next scenario (Pitfall 4 the same scenario every year)
- Pitfall 4 The same scenario every year What happens: e.g. People memorize the flow and nobody hesitates How to check: e.g. See whether the prompt matches last time's record
- How to prevent: the next prompt e.g. Start with a client saying "I got an email in your company name that I do not recognize"
- Timing and guests for next time e.g. In six months. Invite the teams that were absent this time, and the maintenance vendor
Task board contents
Preparing 16 items
Set aim and roles
On page 1, write the aim and the 90-minute time plan, then settle the four roles with their people and the ground rules. Once these are set you can send the notice for the day. Press Ctrl+F (⌘F on Mac) and enter 3/4 to jump to page 3.
Open plan, contacts
Open your incident response plan and emergency contact list, and check that the name and phone number of the first person to call are still correct, by comparing them with the staff directory or asking that person directly. Check just one person. Then write one line on the aim note in section ① and you are done (about 15 minutes).
Assign four roles
In the table in section ②, write the names and what to bring for the facilitator and note-taker, management, a frontline representative, and IT. Done when all four rows have a name.
Send ground rules
Put the three ground rules in sections ③–⑤ (no blame, no hunting for answers, keep records) into the notice for the day and send it to participants. Done once sent.
Run the scenario
On page 2, read the scenario by time and discuss the decisions and contacts of management, frontline staff, and IT. This is the core of the exercise and takes 45 of the 90 minutes.
Prep scenario rows
Before the exercise, the facilitator prepares in a separate document the five situations that go into the What happened column of section ⑥. On the day, copy only the row being read into section ⑥ and let participants fill the other columns. Done when all five situations are ready.
Record decisions
Using the four steps in section ⑦, go through section ⑥ one row at a time and fill the decision and contact columns. Done when all five rows have a decision.
Note the gaps
Write anything you hesitated over, or that the plan and contact list do not cover, in the Gap found column of section ⑥. It feeds the review on page 3.
Review decisions
On page 3, line up the gaps found, check the exercise pitfalls, and narrow the gaps down to three to fix. Those three are what page 4 assigns owners and deadlines to.
Sort gaps on 2 axes
Place each gap from the Gap found column of section ⑥ into one of the four impact-and-ease groups in section ⑧. Done when every gap is placed.
Check the pitfalls
For the three pitfalls in sections ⑨–⑪, check whether each one happened in this exercise and write it on the Check this time note.
Pick 3 gaps to fix
Choose from the groups in section ⑧ with big impact and easy fixes first, and write the three gaps to fix in section ⑫. Done when three are chosen.
Fix gaps, plan next
On page 4, review the exercise with KPT, set an owner and deadline for each gap, and write an idea for the next scenario. Track what you decide in the Fixing column of the task board.
Reflect with KPT
In section ⑬, write two items each for what to keep, problems, and what to try next about how the exercise ran. Reflect on the exercise itself, not on the contents of the plan.
Set owners and dates
In the table in section ⑭, write what to fix, the owner, and the deadline for the three gaps from section ⑫ and one Try. Done when all four rows have an owner.
Draft next scenario
In section ⑮, write a scenario idea that starts differently from this time, plus the timing and guests for next time. This final step keeps the scenario from repeating every year.