The Application Workshop

You've learned to see the operating system.
Now apply the lens to your actual problems.

The Waterline Lab takes the six diagnostic lenses from Beneath the Waterline and puts them to work on your organisation's real recurring patterns. No designed puzzles. No simulated encounters. Your actual friction. Your real pain. Your system - made visible.

← Follows Beneath the Waterline. Can also stand alone.

See how it works

An iceberg split at the waterline - a small visible peak above the surface, a much larger mass hidden below.

YOUR RECURRING PROBLEMS

VISIBILITY MAP

Two workshops. One diagnostic discipline.

How they fit together

Workshop 1

Beneath the Waterline

Six designed encounters that teach your team to see the hidden operating system. Experiential. No lectures. Participants discover - through lived experience - that friction, permission, signals, meaning, visibility, and constraints shape behaviour more than personality or ability.

Output: a diagnostic lens participants can use on Monday. A redesigned artefact.

Learn about Beneath the Waterline →

Workshop 2 - you are here

The Waterline Lab

Your team brings its actual recurring problems. Same six lenses. Same diagnostic discipline. Different material: your real friction, your real patterns. Output is a System Visibility Map for 1-3 patterns - not an action plan, but a durable diagnostic artefact you can return to.

Output: a System Visibility Map. A sharper question. Protection against false fixes.

The diagnostic spine

From recurring problem to system visibility

The Waterline Lab follows a single, clean movement. Each phase builds on the last. Nothing is theoretical. Everything works from material the participants bring.

Recurring problem

↓

System assumption

↓

Normalised behaviour

↓

Hidden cost

↓

Leverage point

↓

False fix

↓

Visibility Map

Phase 1

Seeing Before Fixing

Why familiar fixes - more training, tighter policy, better communication - often leave the underlying pattern untouched.

Phase 2

The Problem That Keeps Returning

Participants surface real recurring friction from their own context. Clustered. Named. No solutions yet.

Phase 3

Pattern, Not Anecdote

Converting complaint into observable system behaviour. "Understanding is assumed once information has been delivered" - not "people don't listen."

Phase 4

Lens Pass

One pattern. Six lenses. Each lens asks a different diagnostic question - revealing what the system must be assuming for the pattern to keep making sense.

Phase 5

Strongest Assumption

Choosing explanatory power over comfort. The best assumptions are slightly uncomfortable - they explain the pattern and implicate the system.

Phase 6

Implication Cascade

Tracing what the assumption produces over time: normalised behaviour → second-order training → eroded capability → systemic cost.

Phase 7

Cost Location

Separating where the cost is felt from where it is produced. Often, the people feeling the pain are not the people who can change the condition.

Phase 8

Leverage & False Fixes

Finding the smallest useful interruption point. Naming the tempting response that would miss the system design issue entirely.

Phase 9

Visibility Map & Transfer

A durable artefact the organisation can return to. A sharper question for the next improvement conversation. The six-W carry-out for Monday morning.

The core diagnostic move

One pattern. Six lenses.

This is where the workshop becomes distinctive. A single recurring pattern - "understanding is assumed once information has been delivered" - is run through all six lenses. Each lens reveals a different system assumption. The group selects the one with the greatest explanatory power - not the most comfortable one.

"Understanding is assumed once information has been delivered."

FrictionWhere is energy consumed by the design, not the task?

PermissionWho can act - and who waits for clarity that never arrives?

SignalsWhat would a rational person learn to do when information is delivered without follow-through?

MeaningDo we share understanding, or just vocabulary?

VisibilityWhat is measured vs what is actually understood?

ConstraintsWhat behaviour does this pattern make normal - and what does it make costly?

The same six lenses taught in Beneath the Waterline - now applied to your material.

If participants have done Beneath the Waterline, they arrive already fluent in the lenses. The Lab is where they put that fluency to work.

If they haven't, the lenses are introduced lightly in Phase 4 - not as a taxonomy to memorise, but as tools for reading a pattern.

Not an action plan

What participants leave with

The Waterline Lab deliberately resists the gravitational pull toward premature action planning. The output is not a list of fixes. It's something more durable.

🗺️

System Visibility Map

A completed diagnostic artefact for 1-3 real patterns. Recurring problem → assumption → cost → leverage point → false fix. The organisation can return to it.

🔬

A sharper question

Not "what should we do?" - but "can we see the system clearly enough that the next action is aimed at the pattern, not just the symptom?"

🛡️

Protection against false fixes

Every group names the tempting response that would miss the system design issue. Training. Policy. Monitoring. Named and set aside - before the action-planning instinct kicks in.

Practical details

Format & audience

Duration

One day, covering 1-3 real patterns from recurring problem through to System Visibility Map.

Prerequisites

None required. Works best after Beneath the Waterline - participants arrive already fluent in the six lenses. Works standalone - the lenses are introduced in-session.

Who it's for

Senior leadership teams facing recurring implementation problems
Schools preparing for change, review, or inspection
Cross-functional groups where the same issue is experienced differently at different levels
Boards needing visibility before commissioning solutions
Any team that has tried to fix the same problem more than once

Connection to Loom

Visibility Maps feed directly into SVP cycles in Loom - System Visibility Process, the platform's structured method for logging recurring organisational patterns as trackable evidence, not anecdote. A pattern identified here becomes a signal to track over time. The workshop builds the capacity. The digital SVP sustains the visibility.

You've learned to see the operating system.Now apply the lens to your actual problems.