The Beat Network

A method for sequencing organisational change.

The Beat Network

A method for sequencing organisational change

Most change programmes fail on sequencing

Most programmes pick reasonable interventions, then sequence them badly or not at all.

The typical plan is parallel workstreams, a Gantt chart that nobody reads, and governance that looks like coordination.

What it lacks is causal logic.

profound.fyi

The method borrows the beat sheet from screenwriting

Studios use beat sheets to check that a story works before they commit to production. The structure is flat and sequential, with nowhere to hide.

An organisation has many groups living through change at once, so the Beat Network adds dependencies across groups, conditions on the ground, and observable signals.

profound.fyi

Six primitives, no more and no fewer

  • Beat: one change move, written as one complete sentence
  • Changes: an ordered line of beats with a name, a scope, and an owner
  • Gate: a named point where one set of changes waits on another
  • Condition: the state of the ground a beat needs to work
  • Signal: observable evidence that a beat has landed
  • Stall: a signal that does not arrive when expected
profound.fyi

Every beat must earn the next

  1. Write each beat as a complete sentence, with one job
  2. Apply the position test: if you can move a beat without breaking the logic, the bridge is not built
  3. Merge beats that do the same thing
  4. Give every beat a signal

If you cannot say how you would know a beat has landed, it is not concrete enough.

profound.fyi

A stall tells you something

Check the condition before a beat. If the ground is not ready, no amount of upstream progress helps.

When a signal does not arrive, choose one response: wait, re-sequence, rework, or dissolve.

Stalls travel through gates, and the network makes that knock-on effect visible.

profound.fyi

Groups move at different speeds, and that is expected

Like players in a multiplayer game, groups progress through their own quest lines and meet only at named convergence points.

Unlike a game, you design the map while you play it.

The network has no durations and no Gantt bars. It says what order things happen in and why. It never says when.

profound.fyi

Leadership decides, the network holder makes decisions visible

  • Network holder: tracks signals, surfaces gates and stalls, and prepares decisions
  • Network authority: the leadership team, which decides on stalls and approves or dissolves changes

The two meet on a regular cadence, fortnightly in most contexts.

profound.fyi

Gates mark where one change depends on another

Getting gates wrong is how programmes produce activity without progress.

profound.fyi

Build the network, then run it as an experiment

  1. Name two to five lines of change
  2. Frame each with its first and last beat
  3. Fill the middle and test each beat's position
  4. Connect beats with gates, conditions, and signals
  5. Run it and update as beats land or stall

Treat the network as a hypothesis to test.

profound.fyi

Ask whether each beat has landed

"Are we on track?" invites false confidence.

"Has this beat landed, and if not, what does that tell us?" invites a decision.

profound.fyi

Read the full method

profound.fyi/playbooks/beat-network

All slides

Most change programmes fail not because they choose the wrong interventions, but because they sequence them badly or not at all. The typical programme plan presents a hierarchy of workstreams running in parallel, connected by a Gantt chart that nobody reads and a governance structure that creates the illusion of coordination without establishing causal logic.

The Beat Network borrows a structural discipline from screenwriting - the beat sheet - and extends it into a networked model for organisational change. Where a screenplay has one audience following one sequence, an organisation has multiple groups experiencing change concurrently from different starting points. The Beat Network preserves the rigour of the beat sheet (flat, sequential, no hiding in hierarchy) while adding the cross-cutting dependencies, ground-truth conditions, and observable signals that organisational change demands.

A Beat Network is a set of concurrent, numbered sequences (changes), each describing a coherent line of organisational change. Each set of changes is a flat list of beats - complete sentences, one job per beat, each earning the next. Sets of changes are connected at explicit synchronisation points (gates) where progress in one set depends on progress in another. Every beat is grounded in an observable condition and validated by an observable signal.

The playbook is structured in seven parts:

  1. Primitives - the six elements of the method and how they relate.
  2. Writing Beats - rules for writing beats, changes, and connections.
  3. Conditions and Stalls - working with ground truth and what happens when signals do not arrive.
  4. The MMO Principle - the structural metaphor and what the method is not.
  5. Governance - two roles, one interface, and how the network is held.
  6. Worked Example - a sketch of three sets of changes for a product operating model adoption.
  7. How to Use It - the sequence for building and running a Beat Network.

The method is new. It will develop through use. This document is itself a beat sheet for the method: each section earns the next, and the test is whether the argument lands.

Licensed under CC BY-SA 4.0.