The MMO Principle
The structural metaphor is the massively multiplayer online game. In an MMO, multiple players progress through different quest lines at different speeds. Some quests are independent. Some are gated by completion of quests in other lines. Coordination happens at convergence points, not through centralised scheduling. Players can see their own quest line and understand what the current objective is. The game designers have solved the dependency graph in advance, but in organisational change, you are designing the graph while running it.
This metaphor carries three important implications. First, different groups experience change at different speeds and from different starting points, and that is expected, not a problem to solve. Second, coordination is achieved through named convergence points (gates), not through synchronised timelines. Third, the overall narrative emerges from the interaction of multiple quest lines, not from a single master plan.
The key difference from a real MMO is that the dependency graph is itself a hypothesis. Changes get re-sequenced. Beats get rewritten. New changes emerge. Old ones dissolve. The network is a living document, not a fixed design.
What it is not
The Beat Network is not a programme plan. It has no durations, no resource assignments, no Gantt bars. The question it answers is not "when" but "in what order and why." It is a logical sequencing tool, not a scheduling tool.
It is not a dependency tracker in the project management sense. A dependency tracker assumes the plan is correct and monitors execution. The Beat Network assumes the plan is a hypothesis and uses signals and conditions to test it. Beat work is iterative. The network you build before starting is not a blueprint. It is the first experiment.
It is not a replacement for sensing. The sensing framework provides the signals. The Beat Network provides the structure that makes those signals actionable. They are complementary.
Licensed under CC BY-SA 4.0.