Method guideOperations

Barrier Analysis

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium

Time2-4 h

Participants2-6

FormatWorkshop + async

MaturityEstablished

Plan Barrier Analysis

Prerequisite

What needs to be finished first

Complete firstBounded subject

The scope and purpose of Barrier Analysis are stated as a concrete question.

Without scope, barrier analysis table becomes arbitrary.

Complete firstAccess to relevant perspectives

Incident or scenario description, system and process data, barrier and test evidence and domain decision makers are available.

Without these perspectives, central claims in barrier analysis table remain unsupported.

Preparation

What needs to be ready before start

Materials

Incident or scenario description, system and process data, barrier and test evidence, shared workspace, source links, and decision log.

People / roles

Investigator · operator · safety/domain expert · control owner

Pre-read

Collect Incident or scenario description, system and process data, barrier and test evidence in advance and mark open assumptions.

Time needed

60–120 minutes

Setup

Prepare hazard-target path plus barrier function, condition, failure mode, and correction visibly and calibrate assessment terms before starting.

Core question

The one question this method answers

Which barrier should interrupt the path, how did it fail, and which independent control is missing?

Flow

Phases with goal, actions, output and pitfall

Barrier analysis defines the hazard, target, and energy or information path. Physical, administrative, and human barriers are tested by function, performance requirement, and actual condition.

barrier analysis table

Fictional worked example

hazard-target path plus barrier function, condition, failure mode, and correction as a precise working structure with a fictional example.

barrier analysis table
Subject	Hazard/Target	Barrier	Condition	Correction/Test
barrier analysis tableWorked example	Unvalidated data → export → customer.	Schema check; preventive; mandatory fields complete.	Present, nulls not covered.	Quarantine stop; null blocks export.

1. Hazard/Target
barrier analysis table
Unvalidated data → export → customer.
2. Barrier
barrier analysis table
Schema check; preventive; mandatory fields complete.
3. Condition
barrier analysis table
Present, nulls not covered.
4. Correction/Test
barrier analysis table
Quarantine stop; null blocks export.

The example demonstrates the domain logic of Barrier Analysis; worksheets remain blank.

U.S. Department of Energy: Accident Prevention and Investigation Program

1
Define path
Define path
Goal
Produce hazard-target path so the core question “Which barrier should interrupt the path, how did it fail, and which independent control is missing?” can be answered with stronger support.
Inputs for this step
- Incident or scenario description
- system and process data
- barrier and test evidence
Actions
- Specify hazard, target, and transfer path.
- Record source, rationale, and open uncertainty directly in hazard-target path.
Output
hazard-target path
hazard-target path · source · uncertainty · next decision
Quality check
Is the unwanted transfer clear?
Pitfall
A control is counted as an effective barrier without function, independence, or a negative test. Test every barrier against a concrete path, performance standard, and negative test.
Timing: 10–20 minutes
2
Inventory barriers
Inventory barriers
Goal
Produce barrier set so the core question “Which barrier should interrupt the path, how did it fail, and which independent control is missing?” can be answered with stronger support.
Inputs for this step
- hazard-target path
- system and process data
- barrier and test evidence
Actions
- Inventory preventive, detective, and mitigating barriers.
- Record source, rationale, and open uncertainty directly in barrier set.
Output
barrier set
barrier set · source · uncertainty · next decision
Quality check
Does every barrier have a clear function?
Pitfall
A control is counted as an effective barrier without function, independence, or a negative test. Test every barrier against a concrete path, performance standard, and negative test.
Timing: 10–20 minutes
3
Analyse failure
Analyse failure
Goal
Produce failure analysis so the core question “Which barrier should interrupt the path, how did it fail, and which independent control is missing?” can be answered with stronger support.
Inputs for this step
- barrier set
- system and process data
- barrier and test evidence
Actions
- Test intended function, actual state, independence, and failure mode.
- Record source, rationale, and open uncertainty directly in failure analysis.
Output
failure analysis
failure analysis · source · uncertainty · next decision
Quality check
Does evidence support the condition?
Pitfall
A control is counted as an effective barrier without function, independence, or a negative test. Test every barrier against a concrete path, performance standard, and negative test.
Timing: 10–20 minutes
4
Improve barriers
Improve barriers
Goal
Produce barrier improvement so the core question “Which barrier should interrupt the path, how did it fail, and which independent control is missing?” can be answered with stronger support.
Inputs for this step
- failure analysis
- system and process data
- barrier and test evidence
Actions
- Add missing or weak barriers and run negative tests.
- Record source, rationale, and open uncertainty directly in barrier improvement.
Output
barrier improvement
barrier improvement · source · uncertainty · next decision
Quality check
Does the test prove interruption of the path?
Pitfall
A control is counted as an effective barrier without function, independence, or a negative test. Test every barrier against a concrete path, performance standard, and negative test.
Timing: 10–20 minutes

Artifact

What comes out at the end

Sketch: what the artifact looks like

Barrier Analysis · SchutzschichtenQuelle, Barrieren und Ziel als Wirkungslinie mit prüfbaren Schutzschichten sichtbar machen

Form

Versioned barrier analysis table with date, sources, owners, and next review.

Versioning / ownership

Retain date, source, assumption state, and decision for every version of barrier analysis table.

Tool alternatives

barrier analysis table as board or document
Source and evidence register
Decision and action log

barrier-analysis-working-template.md

Plan Barrier Analysis around its domain steps and the concrete decision question.

Barrier Analysis: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Full workshop Time: 60–120 minutes

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: Incident or scenario description, system and process data, barrier and test evidence, shared workspace, source links, and decision log.
Roles: Investigator · operator · safety/domain expert · control owner
Advance information: Collect Incident or scenario description, system and process data, barrier and test evidence in advance and mark open assumptions.
Overall time needed: 60–120 minutes
Setup: Prepare hazard-target path plus barrier function, condition, failure mode, and correction visibly and calibrate assessment terms before starting.

Prepare for the work steps

Define path: Define path

Incident or scenario description
system and process data
barrier and test evidence

Inventory barriers: Inventory barriers

hazard-target path
system and process data
barrier and test evidence

Analyse failure: Analyse failure

barrier set
system and process data
barrier and test evidence

Improve barriers: Improve barriers

failure analysis
system and process data
barrier and test evidence

barrier analysis table

Subject	Hazard · path · target	Function · type · standard	Present · effective · independent	Change · owner · negative test
barrier analysis table

barrier analysis table: Worked example

Enter only real input, sources, and decisions.

U.S. Department of Energy: Accident Prevention and Investigation Program

Define path: Define path

Expected artifact: hazard-target path

hazard-target path · source · uncertainty · next decision

Entry:

...

Is the unwanted transfer clear?

Inventory barriers: Inventory barriers

Expected artifact: barrier set

barrier set · source · uncertainty · next decision

Entry:

...

Does every barrier have a clear function?

Analyse failure: Analyse failure

Expected artifact: failure analysis

failure analysis · source · uncertainty · next decision

Entry:

...

Does evidence support the condition?

Improve barriers: Improve barriers

Expected artifact: barrier improvement

barrier improvement · source · uncertainty · next decision

Entry:

...

Does the test prove interruption of the path?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/barrier-analysis/run-sheet

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

barrier-analysis-beispiel.md

Concrete filled scenario, fictional example

Hazard: unvalidated data. Target: customer decision. Barrier 1 schema validation: present, but did not cover nulls. Barrier 2 four-eyes review: present, but the same person produced and reviewed the report. Missing independent barrier: automatic quarantine stop for mandatory-field errors. Test: injected nulls block export.

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

Define pathA control is counted as an effective barrier without function, independence, or a negative test.View in phase
Inventory barriersA control is counted as an effective barrier without function, independence, or a negative test.View in phase
Analyse failureA control is counted as an effective barrier without function, independence, or a negative test.View in phase
Improve barriersA control is counted as an effective barrier without function, independence, or a negative test.View in phase