Blameless postmortem canvas
Discover how Byron Torres does Blameless postmortem canvas in Miro.
Follow this process means that engineers whose actions have contributed to an accident can give a detailed account of:
what actions they took at what time,
what effects they observed,
expectations they had,
assumptions they had made,
their understanding of timeline of events as they occurred.
and that they can give this detailed account without fear of punishment or retribution.
The Blameless postmortem includes the following sections
Step 1: Summary (pre-fill ahead of the meeting)
A high-level summary of the issue, focusing on what is known at this point and what the impact to the customer was. Keep this to a sentence or two.
Step 2: Rough Timeline (pre-fill ahead of the meeting)
A rough timeline of the issue. Depending on how fast-moving the issue was, this timeline could span a few minutes to a few hours to a few days. If your primary focus is on improving the team’s response times during emergencies, you’ll want this down to the second.
As you capture the timeline, be sure to include:
When the issue was reported and by whom/what process
What actions were taken
When communication was made into and out of the team
Remediation Ideas
When you meet to discuss the issue, invite everyone who worked the issue. This includes the production support team as well as the customer support team members that may have been involved.
Review the summary, review the time line and add any missing parts, then move into the remediation ideas.
These questions are formulated to help the team take ownership of the problem. There are some issues that feel like they are outside of the team’s control (data center loses power, etc). But even in events like those, the team can still improve their reaction to the disaster.
Step 3: Detect – How do we detect this problem or a problem like this sooner?
Assume this problem or a problem very much like it will happen again. How can the support team detect this problem faster and find it before a customer does?
Step 4: React – How do we improve our reaction to issues like these?
Assume the issue is reported. How quick was the reaction? Were minutes lost while people were sending emails around trying to get someone to look at the problem?
The next time this issue happens, how can the team react more quickly or in a more organized fashion?
Step 5: Quick Fix – How do we stop the bleeding faster?
When this happens again, is there a ready workaround that we can provide the customer to reduce the impact of the problem?
If this is something that gets worse over time (like a DDOS attack) do we have a quick way to close the flood gates while we figure out the root cause?
Step 6: Prevent – How do we prevent or reduce the impact of issues like in the future?
This is often the only question teams ask in a postmortem. It is an important question and you should spend a lot of time here. However, if you limit yourself to asking only how to prevent an issue, it lets you not take any responsibility for the things within your control (like how you detect, react or quick fix an issue).
As you brainstorm ideas, don’t limit yourself to technical fixes. Better monitoring, better communication paths, better training, making sure the people in customer support know the people in production support by name, etc.
Step 7: Other Areas of Risk – What other areas share this same vulnerability?
Every issue is a hint at where your system is weak. Odds are, for each issue you find, there are dozens lurking in the shadows, yet to be found.
Kind of like if you see a mouse in your kitchen. You don’t have a “mouse” problem, you’ve got a “mice” problem.
There are likely other parts of the system that share the same design assumptions or in some cases the same code (not that anyone would ever copy/paste code).
Spend a few minutes brainstorming for other places that are vulnerable in a similar way.
When teams are stressed and overworked, they will skip this step. I find that this is the most important question to ask to get the team into a proactive mindset and to reduce the occurrence of issues in the future.
Step 8: Next Steps (Actions)
After you’ve identified all the possible things you can do to improve how issues are detected, reacted to, quick fixed and prevented…and you’ve found the other areas of your application that need attention…move on to deciding which actions to take.
The way you prioritize these is up to you. But I do have a few pieces of advice.
Get a name and a date on each one you plan to action before you leave the meeting
If someone in the meeting is passionate about taking one of the actions, encourage them to, even if you think it might not be the most important thing to fix
Names and Dates
Generally, I’ve found that teams enjoy this exercise (provided you can create a blameless environment for the meeting). They like dissecting the problem and brainstorming solutions. However, everyone feels busy and overworked. Unless this meeting wraps with owners and dates next to the things that need to be done, the greatest likelihood is that none of the improvements will happen.
What will happen is that 3 weeks from now when the same problem occurs on production (but this time in a bigger way) someone will say, “oh yeah, we talked about fixing that.” Not a great place to be.
To combat that, simply ensure that there is a name and date next to each action that the group wants to take.
This template was created by Byron Torres.
Get started with this template right now.
DMAIC Analysis Template
Works best for:
Agile Methodology, Design Thinking, Operations
Processes might not seem like the funnest thing to dive into and examine, but wow can it pay off—a more efficient process can lead to serious cost savings and a better product. That’s what DMAIC analysis does. Developed as part of the Six Sigma initiative, DMAIC is a data-driven quality strategy for streamlining processes and resolving issues. The technique is broken into five fundamental steps that are followed in order: Define, Measure, Analyze, Improve, and Control.
Design Sprint Retrogram
Works best for:
Agile, Retrospective
The Design Sprint Retrogram template facilitates retrospective sessions for Design Sprint teams to reflect on their experiences and identify improvement opportunities. It provides a structured framework for reviewing sprint outcomes, discussing what worked well, what didn't, and generating actionable insights. This template fosters a culture of continuous learning and refinement, empowering teams to enhance their sprint process and deliver better outcomes in subsequent sprints.
Backlog Refinement with Jira Template
Works best for:
Agile, Backlog Refinement
The Backlog Refinement with Jira template in Miro improves collaboration among team members. It provides a visual and interactive space for teams to review, prioritize, and clarify upcoming work items together in real time. This collaborative approach ensures alignment on priorities and details, leading to a more organized and efficient workflow. The seamless integration with Jira automatically syncs all changes, reducing the need for manual updates and keeping both platforms up-to-date.
Quick Retrospective Template
Works best for:
Education, Retrospectives, Meetings
A retrospective template empowers you to run insightful meetings, take stock of your work, and iterate effectively. The term “retrospective” has gained popularity over the more common “debriefing” and “post-mortem,” since it’s more value-neutral than the other terms. Some teams refer to these meetings as “sprint retrospectives” or “iteration retrospectives,” “agile retrospectives” or “iteration retrospectives.” Whether you are a scrum team, using the agile methodology, or doing a specific type of retrospective (e.g. a mad, sad, glad retrospective), the goals are generally the same: discovering what went well, identifying the root cause of problems you had, and finding ways to do better in the next iteration.
Lean Coffee by Michael de la Maza
Works best for:
Agile Methodology
Lean Coffee is a collaborative meeting format that encourages open dialogue and self-organization. Participants suggest discussion topics, vote on them, and engage in time-boxed conversations. This template provides a structured framework for facilitating Lean Coffee sessions, enabling teams to address issues, share knowledge, and make decisions collectively. By fostering inclusivity and autonomy, Lean Coffee empowers teams to drive meaningful discussions, build consensus, and drive continuous improvement.
Sprint Planning with Jira Template
Works best for:
Sprint Planning, Agile
The Sprint Planning with Jira template in Miro is a powerful tool designed to streamline and enhance your sprint planning sessions. One of the key benefits of this template is its Jira integration, which saves time and effort when planning and aligning teams. By integrating directly with Jira, the template allows for seamless import and management of tasks, ensuring that all your Jira tickets are up-to-date and easily accessible within Miro. This reduces the need for manual updates and minimizes errors, making the planning process more efficient and effective.