methodatlas
Engineering

Fault Isolation

Turns technical problems, hypotheses, and next steps into a tangible result by clarifying the symptom and system boundaries, breaking the fault space into areas, and narrowing the affected area.

Core question
Which system area most likely causes the symptom, and which tests narrow the fault domain further?
MediumWorkshop + async30-180 min
Open runsheetPlan sessionStart comparison
Purpose

The method helps clarify technical problems, hypotheses, and next steps in a concrete way. It breaks a technical problem into testable parts. The result is captured as a fault isolation map, a test log, and excluded hypotheses.

How it works

The team follows the steps: clarify the symptom and system boundaries, break the fault space into areas, prioritize hypotheses, run targeted tests, and narrow the affected area while deriving the next analysis step. Each step is captured visibly. At the end, a fault isolation map, a test log, and excluded hypotheses are available so decisions, tests, or actions can follow directly.

Visual orientation

Method sketch for a quick mental model.

Fault Isolation · Narrowing DownBreak the fault space into testable system areas, run targeted tests, and document excluded areas visibly
Fault IsolationThe visual shows a reproducible symptom, a fault space decomposed into components, targeted tests, excluded areas, and a narrowed fault area.Shrink the fault space step by step to the failing areaFault Isolation splits a system into testable sections and documents which areas were excluded by tests.Fault spaceTest 1: Client okTest 2: Queue okTest 3: DB reproducesTests include or exclude areasShrink fault spaceSymptomreproducible and clearlyboundedClientexcludedAPIunclearQueueexcludedDBsuspiciousNarrowed fault areaDB timeout under high loadNext analysischeck hypothesis or root cause

Flow

  1. 1Clarify the symptom and system boundaries
  2. 2Break the fault space into areas
  3. 3Prioritize hypotheses
  4. 4Run targeted tests
  5. 5Narrow the affected area and derive the next analysis

The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Technical troubleshooting
  • Integration failures
  • System outages

Not good for

  • Open strategy questions
  • Non-testable conflicts
  • Pure ideation

Deep dive

In detail

Fault Isolation works by narrowing the search instead of guessing. A complex system is broken down into components, interfaces, states, and dependencies. Through targeted tests, comparisons, and control questions, the possible error area is gradually reduced. The result is not the root cause right away, but a well-narrowed location or mechanism.

Facilitation

Start with a system sketch and clear symptoms. Plan tests so that each one truly reduces the fault space. Document excluded areas so the team does not keep testing the same hypotheses.

Output artifacts
Fault Isolation MapTest LogExcluded HypothesesNarrowed Fault Area
Tags
troubleshootingdiagnosisengineering

Sources

Fault detection and isolation - Wikipediaen.wikipedia.org
Artifact templates
Fault Isolation Working TemplateCompact working template for Fault Isolation with context, input, output artifacts, and next step.
canvas

fault-isolation-working-template.md

Compact working template for Fault Isolation with context, input, output artifacts, and next step.

Fault Isolation Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Fault Isolation Map:
  • Test Log:
  • Excluded Hypotheses:
  • Narrowed Fault Area:

Open questions

  • ...

Next step

Owner, date, and success signal.

When to choose differently

Short decision aid for existing alternatives.

Root Cause Analysis

Statt Fault Isolation, wenn du Ursachen systematisch eingrenzen und nicht bei Symptomen stehen bleiben willst.

Fault Tree Analysis

Statt Fault Isolation, wenn Ausfälle logisch von oben nach unten zerlegt werden sollen und einzelne Tests noch nicht reichen.

Similar methods

All methods
Engineering
Hypothesis-Driven Troubleshooting

Turns technical problems, hypotheses, and next steps into a tangible result by collecting symptoms, formulating hypotheses, and refining them through testing.

Operations
Change Analysis

Turns workflows, data, causes, and improvements into a tangible result by describing the deviation, choosing a comparison case, and deriving causes and actions.

Engineering
Goal Question Metric

Moves technical problems, hypotheses, and next steps toward a concrete result through "formulate the goal clearly", "derive probing questions for each goal", and "set the review cadence".

Operations
Causal Factor Analysis

Turns workflows, data, causes, and improvements into a tangible result by collecting event data, reconstructing the timeline, and deriving root causes and measures.

Engineering
Failure Scenario Analysis

Turns technical problems, hypotheses, and next steps into a tangible result by defining the system or process, collecting plausible failure scenarios, and deriving tests, prevention, and response.

Engineering
Golden Path

Turns technical problems, hypotheses, and next steps into a tangible result by choosing a common use case, describing a best-practice path, and integrating feedback and exceptions.