FAULT LINE

Build the company. Break it. Learn why.

The only risk workshop where you can point at the part that failed.

Risk registers describe items. They do not show how the items break each other.

Risk registers describe individual items. They do not show how the items break each other. A vulnerability in a supplier system, a single point of failure in an authentication dependency, a response procedure that assumes staff availability — each looks manageable in isolation. Together, they become an incident.

Risk architecture decisions are almost always made without a shared model of the system. Different people hold different mental maps. Assumptions go untested. The consequences of one control choice on another remain invisible until something breaks in production.

FAULT LINE makes the architecture physical. Your team builds it together, stresses it together, and sees the failure cascade together. The insight that takes months to surface in a risk register review surfaces in forty minutes at the table.

The risk you have not modelled is the risk that bites you.

THE WORKSHOP

What FAULT LINE actually is

FAULT LINE is a risk architecture workshop that uses LEGO as the physical medium. Your team builds a model of your organisation’s technical and operational structure — systems, dependencies, third parties, response procedures — then introduces realistic failure events and watches the model break.

The LEGO model is not decorative. It is a shared representation of your architecture that everyone in the room can see, point at, and argue about. When a failure event is introduced, the physical model makes the cascade immediately visible in a way that a diagram or slide deck cannot.

Sessions run 120 minutes or more, depending on the complexity of the architecture being modelled. Participants are typically risk managers, technical leads, and security architects — the people who make or influence control decisions. The workshop surfaces the assumptions and gaps that exist between them.

THREE ACTS

How FAULT LINE is structured

Build (40-50 min)

Your team constructs a physical LEGO model of your organisation’s architecture: systems, dependencies, third parties, and the controls that connect them. Disagreements about the model are the first useful output.

Stress (60-90 min)

Failure events are introduced one by one. The team watches what breaks, what holds, and what the cascades reveal about dependencies they did not know they had. The physical model makes invisible risks visible.

Debrief (30-45 min)

The model stays on the table. The team identifies the leverage points — the controls and dependencies that matter most — and leaves with a prioritised list of architecture decisions to revisit.

LEARNING OUTCOMES

What your team walks away with

Shared physical model

A shared, physical model of your organisation’s risk architecture

Cascade visibility

Visible understanding of how individual risks interact and cascade

Single points of failure

Identified single points of failure and high-leverage control decisions

Resolved assumptions

Resolved assumptions between risk, security, and technical teams

Prioritised decisions

A prioritised list of architecture decisions worth revisiting

Shared mental model

A team that has shared the same mental model for the first time

Who this is for

FAULT LINE works for risk managers, security architects, and technical leads who need to build a shared understanding of their organisation’s risk architecture — and find the gaps between their individual mental models. It is particularly valuable when different functions (IT, security, risk, operations) hold separate views of the same system and need to align before making significant control decisions. Groups of five to fifteen work well. The session does not require prior knowledge of LEGO or risk frameworks — it requires participants who are willing to be wrong in the room and learn from it.

What does your risk architecture actually look like when it is under stress?

FAULT LINE runs on-site. All materials provided. Groups of five to fifteen.

We don't use cookies

Notice there’s no cookie banner here.
That’s intentional and the site is still GDPR-compliant. I chose to avoid cookies and stick to basic, privacy-friendly stats.
Instead of Google Analytics, I use Altcha (altcha.org), an open-source, cookie-free approach.
Result: no annoying popups, and I can still see if people visit.

Everybody wins.