Failure Map

Failure Map image
A failure map, sometimes called a failure-first map or failure path map, is a simple diagram or list of a user journey's dependencies that records what the user would see if each one were down, slow or returning bad data. Unlike a standard system diagram, which shows how data flows when everything works, it focuses on how things fail.

Why it matters: Architecture diagrams tend to hide failure behaviour. Mapping failure points shows where a system will hurt customers most when something breaks, and turns vague worries about reliability into specific test ideas.

In practice: Building a failure map for one critical journey usually takes four steps:

  • Pick one high-value flow, such as placing an order or joining a video call.
  • List every visible dependency for each step: front ends, APIs, queues, caches, databases, third-party services, feature flags and configuration.
  • For each dependency, ask what the user would see if it were down, slow or returning bad data.
  • Turn each answer into a test idea that simulates that condition in a development or test environment.

Examples:

  • Mapping a claims submission journey and finding that a slow document storage service leaves users with no feedback at all.
  • Noting that a missing feature flag service would hide the checkout button rather than fall back to a default.
  • Using the map to choose which dependency to break first in a team chaos session.

Common pitfalls:

  • Mapping only the down state and missing slow or bad-data failures, which are often more confusing for users.
  • Trying to map the whole system at once instead of starting with one critical user journey.

What is the difference between a failure map and a system architecture diagram? An architecture diagram shows components and how data flows between them when things work. A failure map shows what each dependency failing would mean for the user, so it leads directly to test ideas.

Who should create a failure map? Testers can lead it, ideally with developers and SREs who know the dependencies and how they are configured.
Explore MoT
Test Forward 2027 ยท Software Quality in the age of AI image
Tue, 19 Jan 2027
Test Forward is one afternoon at Station F with the QA and engineering people closing that gap in their own teams.
MoT Software Testing Essentials Certificate image
Boost your career in software testing with the MoT Software Testing Essentials Certificate. Learn essential skills, from basic testing techniques to advanced risk analysis, crafted by industry experts.
This Week in Quality image
Debrief the week in Quality via a community radio show hosted by Simon Tomes and members of the community
Subscribe to our newsletter