Incident Values


Identify what your team values most during incident response and create a plan to live those values consistently.

AND I NEED THIS... WHY?

It's a fact of life: stuff breaks and some amount of downtime is inevitable for even the most reliable products. It's how you handle incidents and downtime that really matters.

So how do you ensure everyone on your team is aligned on the incident response process? Even the most comprehensive incident response plan lacks instructions for more subjective, nuanced situations that can and will arise when $#*! hits the fan.

We think it's best when teams are armed with the right knowledge and guidance. And we've found that the best form of guidance is a set of mutually agreed upon values. A set of values aligns everyone’s behavior during all phases of an incident: identification, resolution, and retrospective.

So... what will your team value when it matters most?

WHO SHOULD BE INVOLVED?

Representatives from each department involved in incident response: engineering, support, marketing/PR, etc.

 

阅读更多 Show less
Any team can (and should!) hold retrospective meetings – here's how.
人员

5 - 10

Prep time

30 分钟

Time

60 min

Difficulty

Easy

Running the play

Your team can run this play either quarterly or biannually to track progress on living out your ideal incident values. 

MATERIALS
  • Whiteboard or butcher's paper 
  • Markers
  • Sticky notes
  • Timer
PREP

Prep (30 mins)

Book a room 30-60 minutes early. Write these 5 basic incident values on a whiteboard or butcher paper.

Draw a long line below to each value that will act as a sliding scale. Number the with 6 notches of equal size, 0-5.

Detect

We know there is a problem before our customers do.

0–––––––––1–––––––––2–––––––––3–––––––––4–––––––––5

Respond

Escalate, escalate, escalate (and communicate with customers). 

0–––––––––1–––––––––2–––––––––3–––––––––4–––––––––5

Recover

$#!% happens, clean it up quickly.

0–––––––––1–––––––––2–––––––––3–––––––––4–––––––––5

学习

Always blameless.

0–––––––––1–––––––––2–––––––––3–––––––––4–––––––––5

改进

Never have the same incident twice.

0–––––––––1–––––––––2–––––––––3–––––––––4–––––––––5

(optional) Copy this Trello template and invite play participants to join the board so they can reference more information about each incident value, take notes during the play, and record goals/action items at the end. 

Pro tip

Note that these are the values that Atlassian incident management teams have converged on. Feel free to copy them verbatim. Or, personalize them for your team/organization. This exercise is all about deciding what your team values.

Pro tip

It's key to have folks from different roles represented (support, dev, etc.) so there are different perspectives coming together in conversation that might not otherwise take place.

STEP 1

Set the stage (5 min)

Welcome everyone and establish the rules of engagement:

  • Embrace a positive spirit of continuous improvement and share whatever you think will help the team improve.
  • Don't make it personal, don't take it personally.
  • Listen with an open mind, and remember that everyone's experience is valid (even those you don't share).

Introduce the basic incident values (see above) and describe each one you have written up during prep on your whiteboard/butcher paper. 

If these incident values don't quite fit your team, take a few minutes now to add, remove, or adjust them.

Pro tip

Project this Trello board during the exercise so participants can have more color into what each value entails.

 

STEP 2

Team Value Ratings (10 min)

Hand out 5 sticky notes and a marker to each participant. Spend 2-5 minutes individually rating how well your team lives each value. (0 = "We are far from living this value... 5 = "We nail this value.") Have them write 1 value per sticky and their corresponding rating.

Once everyone is finished, have participants come up and place their ratings on the sliding scales.

ANTI-PATTERN

Discussions are dominated by one or two people.

This is a sign you may need a stronger facilitator. Find an opportunity to step in and ask what one of your quieter teammates has to say on the topic.

STEP 3

Talk it out (25 min)

The real meat of this play comes from discussing why people rated the team on each value the way that they did. Guide the discussion using the questions below. Feel free to add other questions, too.

  • Which values have the most consensus when it comes to ranking? Why do you think that is?
  • Which values have the most discrepancy when it comes to ranking? Why do you think that is?
  • Any major outliers? Give the people who placed outliers an opportunity to explain the thought behind it.
  • What values do you need to work on?

Write down any issues you uncover (i.e. "We never detect incidents before our customers do" or "We usually blame someone during our post incident reviews") on the whiteboard or on a poster board next to your sliders. 

Take a picture of your sliding scales so you can remember where you ranked during this exercise and compare if you run this play again in the future.

Pro tip

It could be that you don't actually value the values you are ranking low on. Decide whether you want to improve these values or ditch them in favor of something you care more about.

 

STEP 4

Boost your values (10 min)

Referring back to the list of issues you uncovered, discuss how you can better live your values. Use questions like these to guide the discussion:

Detect

  • How can we improve our monitoring and alerting systems so we find out about incidents before our customers do? 
  • What tools or processes are we lacking right now?

Respond

  • What is not working about our current escalation process?
  • How can we share the burden of middle-of-the-night alerts and escalation work?
  • How do we train new members of the team on our escalation process?
  • How are we keeping our customers in the loop during an incident? 

Recover

  • Who is ultimately responsible for incident recovery?
  • How long does it usually take for us to resolve incidents?

学习

  • How do we determine is an incident requires a post-mortem or post-incident review?
  • If you were a customer of your service, would you be satisfied with the level of detail we give out about incidents?

改进

  • Who is responsible for mitigation post-incident?
  • How do you hold each other accountable to making sure the same bug doesn't bite twice?
STEP 5

Action plan (10 min)

Decide as a group on 2-3 changes that will help you live the incident values consistently. Record these on your Trello board or whiteboard and bake the action items into your team to-dos/goals for the month. Start building those muscles before the next incident occurs.

Action items could include things like...

  • Name an incident commander so we have a point person to go to when the next incident strikes.
  • Create guidelines around when we write a post-mortem and who we share it with.
  • Look into consolidating the channels we are using for incident communication.
  • Start running post-incident review meetings after each incident that occurs.
ANTI-PATTERN

Listing action items without owners/dates.

Don't let this be an exercise with no real value. Make sure ideas are turned into tasks with owners, and that those tasks are incorporated into your sprints – don't assume people can just squeeze them in at the edges.

Nailed it?

Be sure to run a full Health Monitor session or checkpoint with your team to see if you're improving.

Find your Health Monitor

Variations

LEADERSHIP OR PROJECT TEAMS

Congruent values are important for all teams in an organization. Leadership and Project teams can run this play by adjusting the values to reflect the work and culture you aspire to. Tweak the value names and descriptions to make it relevant for any team at any org. 

 

Template

Incident Values Trello Board

Follow-ups

Share your results and action plan with your broader team/company to stay accountable.

Re-run this play in a few months to see how you did with achieving the goals in your action plan.

Want even more Playbook?

Drop your email below to be notified when we add new Health Monitors and plays. 

Got feedback?

Drop a question or comment on the Atlassian Community site.

加入对话