The Beat Network The Beat Network - overview Present 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. 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. 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 Every beat must earn the next Write each beat as a complete sentence, with one job Apply the position test: if you can move a beat without breaking the logic, the bridge is not built Merge beats that do the same thing Give every beat a signal If you cannot say how you would know a beat has landed, it is not concrete enough. 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. 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. 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. Gates mark where one change depends on another Getting gates wrong is how programmes produce activity without progress. Build the network, then run it as an experiment Name two to five lines of change Frame each with its first and last beat Fill the middle and test each beat's position Connect beats with gates, conditions, and signals Run it and update as beats land or stall Treat the network as a hypothesis to test. 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. Read the full method profound.fyi/playbooks/beat-network Licensed under CC BY-SA 4.0.