Workshop 3 · Designing the Waterline

Seeing the system is not enough.
Culture changes when practice changes.

Three principles. Three core protocols. One real experiment. Thinking by design to build the habits and protocols that strengthen culture - taking the diagnostic clarity from Beneath the Waterline and the Waterline Lab and turning it into installed routines that shape how teams think, decide, and act together.

← Follows The Waterline Lab. Part of the Beneath the Waterline series.

See how it works

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

THE PATTERN YOU'VE DIAGNOSED

THE PROTOCOL YOU INSTALL

Three workshops. One diagnostic discipline.

How the arc fits together

Each workshop does one job well. Together, they move a team from noticing a problem to running an experiment that changes what the environment produces.

Workshop 1

Beneath the Waterline

Six designed encounters that teach a team to see the hidden operating system. Experiential, not lectured. Friction, permission, signals, meaning, visibility, and constraints, shaping behaviour before anyone names them.

Output: a diagnostic lens participants can use on Monday.

Learn about Beneath the Waterline →

Workshop 2

The Waterline Lab

Same six lenses, aimed at a team's actual recurring patterns. Real friction, not designed puzzles. The output is a System Visibility Map - a sharper question, not an action plan.

Output: a Visibility Map. No action plan - the point is seeing clearly, not fixing yet.

Learn about The Waterline Lab →

Workshop 3 - you are here

Designing the Waterline

The pattern stops being a diagnosis and becomes a habit. Three principles, three practised protocols, and one real experiment with a way to check whether it held.

Output: an experiment card and a personal commitment.

The practice-design spine

From two extremes to one installed habit

Designing the Waterline follows a single movement: name what any group defaults to under pressure, live it, diagnose one real pattern, then design a small experiment a team will actually run.

Two extremes named

↓

Three encounters

↓

One real pattern

↓

Principle diagnosed

↓

Habit and protocol chosen

↓

Time-boxed experiment

↓

Personal commitment

Orientation

The Two Extremes

Passive - thinking concentrates in one person while everyone else just attends. Activist - boundaries blur and people start doing each other's jobs. Both feel reasonable. Both erode the quality of collective thinking.

Encounter 1

Attention

Everyone reads the identical material through a different instructed lens, and notices completely different things. Attention is designed, not passive.

Encounter 2

Accountability

A scripted scenario exposes the moment shared agreement quietly fails to become shared ownership afterwards. Everyone was reasonable. The decision still stalled.

Encounter 3

Alignment

The same decision, rewritten by four organisational layers in sequence. Not sabotage. Not resistance. Drift - and it happens to every clean decision that isn't maintained.

Redesign 1

Select the Pattern

Name one real, recurring pattern from your own context, or bring the Visibility Map from the Waterline Lab and skip straight to diagnosis.

Redesign 2

Diagnose the Principle

Work out which principle is under the most strain: Attention, Accountability, or Alignment. That reading shapes everything that follows.

Redesign 3

Habit and Protocol

Each principle connects to a small family of habits and one protocol practised live in the encounters. The team's job is choosing what fits and owning why.

Redesign 4

Design the Experiment

Not a new policy. A time-boxed experiment: one sentence describing what changes, and a signal that shows whether it's working.

Redesign 5

Gallery and Commit

Experiment cards on display. One personal commitment - something each person will stop, start, or do differently, starting now.

The core design move

One principle. A cluster of habits. One protocol you actually practise.

Three encounters, three principles. Each principle comes with a small family of habits, and one protocol every team practises live before deciding whether it becomes their experiment.

The throughline

AttentionHabits: Reveal, Waterline, Perspective. Protocol: Signal Watch - what signal did this send about what we value?

AccountabilityHabits: Perspective, Reveal, Trace. Protocol: Question Ownership - what must not be allowed to drop, and who's holding it?

AlignmentHabits: Trace, Signal, Shift. Protocol: Decision Trace - who acts, who adapts, who experiences this decision?

Every team practises all three core protocols live, once each, during the encounters. Designing a real experiment just means choosing which principle is under the most strain in your own context.

Each of the three encounters teaches its protocol live, so by the time a team reaches the Redesign Studio, they've already practised the move once.

What the team owns is the why: the specific reason this protocol, applied to their specific pattern, will actually interrupt it.

Not a new policy

What participants leave with

Designing the Waterline deliberately resists the pull toward a big rollout. The output is small, time-bound, and built to actually survive contact with the group's next real decision.

🧪

An experiment card

Principle, protocol, a one-sentence change, and a signal that shows it's working, designed to run for a defined stretch, not forever.

🗣️

A shared vocabulary

Six habits - Reveal, Waterline, Perspective, Trace, Signal, Shift - the team can now name in the moment, not just recognise afterward.

✋

A personal commitment

Not what the group will do together - what each person will personally stop, start, or do differently, starting now.

Practical details

Format & audience

Duration

One full day - three encounters, a break for lunch, and the Redesign Studio through to a signed-off experiment card.

Prerequisites

Follows Beneath the Waterline and, ideally, the Waterline Lab. A team arriving with a System Visibility Map skips straight to diagnosing the principle. Without one, that diagnostic runs compressed, in-session.

Who it's for

Boards, leadership teams, and departments who have already named a recurring pattern
Teams ready to test something soon, not just discuss it further
Anyone who has diagnosed a problem before and watched the insight fade within weeks

Connection to Loom

The pattern a team names here can be logged as an SVP cycle in Loom, and whatever check-in rhythm the team sets is exactly the kind of recurring signal SVP is built to hold. The workshop installs the habit. Loom keeps it visible after the room empties.

Two audiences. Same design discipline.

Workshop variants

For schools

Designing the Waterline:
Leadership

For senior leadership teams, middle leaders, and whole-school staff. Encounters use school-specific scenarios - a fictional set of reports read through different instructed lenses, a stalled improvement decision, a strategy reinterpreted from leadership down to the classroom. Follows Beneath the Waterline and an Observation Sprint, where participants collect real evidence from their own school before the day.

Full-day - three encounters plus the Redesign Studio. Each table leaves with an experiment card and a four-week window to test it, timed to the normal rhythm of a school term.

For governance

Designing the Waterline:
Governance

For boards, governing bodies, and trustees. The same three encounters, reframed through a governance lens - private lens cards over a board pack, a governor role-play around a retention strategy, a decision cascaded through committee and school leadership. Follows Governance 201, and ideally Governance 301, whose Visibility Map lets a board skip straight to diagnosing the principle.

Full-day - three encounters plus the Redesign Studio. Each experiment card names a guardian: one governor whose job is asking, at the fourth board meeting, whether the protocol is holding.

Seeing the system is not enough.Culture changes when practice changes.