The Four Disciplines of Weave

Practising coherence in an age of complexity

This essay continues the Weave series on leadership in complexity. The first four posts traced the journey from mastery to versatility — how specialisation built the modern world, how complexity broke it, and what the leaders who survived that break had to become. This post turns from seeing to doing.

Every era produces its own leadership language. The industrial age gave us control. The information age gave us efficiency. The age of complexity demands something harder to systematise and easier to lose: coherence.

Up to this point, the Weave series has been about seeing the world differently — recognising that the future belongs to those who can integrate and align, not simply those who can go deepest in the narrowest place. But seeing differently is not enough. The question that follows every useful framework is the same one: now what?

The four disciplines that follow are not a sequence to complete. They are threads you return to, each one pulling on the others. Awareness informs design. Design enables synthesis. Synthesis anchors culture. Culture widens awareness. The loop tightens with each pass, and coherence is what accumulates.

Discipline One: See the Threads

Most leadership defaults to event analysis — what happened, who caused it, how to prevent it next time. It is a reasonable response to a complicated problem. It is an inadequate response to a complex one.

Seeing the threads means asking a different question: not what happened, but what made this possible at all. What assumptions are we treating as facts? What do some people in this system see clearly that others cannot see at all? Where does our map of the situation stop matching the territory?

Ronald Heifetz calls this getting on the balcony — remaining in the dance while also watching its patterns from above. The discipline is not detachment. It is the cultivation of a second perspective that runs alongside the first, noticing what the first perspective, by design, cannot notice.

In practice this means mapping the perspectives in a room, not just the processes on the wall. It means building the habit of asking what a sceptic, an outsider, or someone three levels below you would see that you can't. It means treating assumptions as the primary object of inquiry rather than the invisible background against which inquiry happens.

The signal that this discipline is taking hold is not that you arrive at better answers. It is that your questions change. Strategy conversations begin with framing rather than fixes. Root causes shift from people and tools to patterns and contexts. You find yourself able to hold competing truths for longer before forcing a resolution — which is, more often than not, where the real insight lives.

The pitfall is mistaking analysis for awareness. Analysis works on what is already visible. Awareness attends to what is structurally hidden — the things the system has organised itself not to surface.

Discipline Two: Work the Loom

Most organisations respond to complexity with more rules and more dashboards. The instinct is understandable. The result is an organisation that has tightened the weave until intelligence stops flowing — where people follow procedures in contexts the procedures were never designed for, and information pools at the edges of functions rather than moving through them.

Snowden and Boone's Cynefin framework established the foundational distinction here: complicated systems can be managed with analysis and good practice; complex ones cannot. In the complex domain, cause and effect are only clear in retrospect, outcomes emerge from the interaction of many factors, and the effective leader becomes a sensemaker rather than a controller. Most organisational design still treats complex problems as if they were merely complicated ones. The result is structures that optimise local variables while missing systemic ones.

Systemic design works the other way. It asks not how to control the system more tightly, but how to build structures that let the right things move — information, trust, accountability, and the capacity to adapt without waiting for permission.

Three principles do most of the work. Design for transparency rather than supervision: make decisions and their reasoning visible by default, not just their outcomes. Design for feedback rather than perfection: many short learning loops beat one long one, and the goal of any review is to change a system, not just account for what happened. Design for coherence rather than conformity: shared context produces better alignment than identical methods, and identical methods, enforced at scale, are usually how you get compliance without understanding.

In structural terms this means preferring clear interfaces between teams over hierarchical gatekeeping — service contracts that define what each part of the system owes the others, rather than approval chains that create bottlenecks at every junction. It means building rhythms that create alignment without centralising control: regular reviews, public pattern notes, retrospectives that are allowed to change how work actually happens rather than simply recording that it did.

The signal that this discipline is working is not tidier org charts. It is that teams adapt without waiting to be told — because the rules of interaction are clear enough that people can reason from them, rather than having to escalate every edge case to someone with a bigger title.

Discipline Three: Find the Pattern

In complex systems, information multiplies faster than meaning. The leaders most at risk in this environment are not the ones who lack data — they are the ones who have more of it than they can make sense of, and who confuse the volume of signal for depth of understanding.

Sensemaking is the discipline of closing that gap. Karl Weick described it as the ongoing, collective crafting of plausible meaning — the process by which humans connect dots that were not designed to align. It is not the same as summarising. Summarising reduces. Sensemaking integrates — combining perspectives to produce a better model of what is actually happening, not a shorter version of each perspective in sequence.

The practical distinction matters. A summary of a complex situation leaves each discipline's view intact and lays them side by side. A synthesis asks what each view reveals that the others cannot — and produces something that none of the contributing perspectives could have produced alone. The first produces a bigger slide. The second produces a better question.

What this requires in practice is the willingness to name patterns publicly before they are certain — to put a provisional interpretation in front of the people closest to the work and invite them to refine it. This is uncomfortable for leaders trained to project certainty. It is also how shared understanding actually forms, as opposed to how it is assumed to form. Patterns named in public become language. Language becomes the medium through which teams make consistent decisions without having to escalate every judgment.

The signal is subtle but distinctive. People start repeating phrases that encode cause and effect — not because they were told to, but because the phrases map accurately to what they experience. Conflicts shift from positions to patterns, which means they become solvable rather than merely manageable.

Discipline Four: Create the Fabric

Culture is not the soft stuff. It is the hidden loom that holds every other thread in place — the accumulated set of answers to the question of how we do things here, operating mostly below the level of conscious decision.

Edgar Schein's foundational work on organisational culture identified three levels at which culture operates: the visible artifacts of an organisation, its espoused values, and — deepest of all — the basic underlying assumptions that most members have never consciously examined. The gap between the second level and the third is where most cultural change efforts fail. Leaders rewrite the values statement and leave the underlying assumptions untouched. The organisation nods, adapts its language, and continues behaving as before.

The Weavist treats culture as infrastructure, which means treating it as something that requires deliberate maintenance rather than periodic campaigns. Values stated on a poster and values that show up in how time and money are allocated are two different artefacts. The first is aspiration. The second is culture. The gap between them is where most organisational energy quietly disappears.

Closing that gap requires three things done consistently rather than occasionally. First, purpose repeated until it becomes a design criterion — not a motivational statement invoked at all-hands meetings, but a filter applied when making trade-offs, and applied visibly enough that people can see the connection. Second, shared language curated deliberately — key terms defined precisely enough that decisions made in different parts of the organisation, by different people, with different information, still cohere. Third, stories told about coherence rather than just performance — short, specific accounts of moments when alignment between values and action produced something it could not have produced otherwise.

Amy Edmondson's research on psychological safety establishes why this matters structurally: teams that feel safe to speak up engage in the learning behaviours — feedback-seeking, raising concerns, testing interpretations — that drive actual performance. Psychological safety is not about comfort. It is the condition under which the other three disciplines can function. Without it, people perform awareness, design, and sensemaking in private rather than in common, which is precisely where coherence collapses.

The signal that this discipline is working is not that people can recite the values. It is that new joiners navigate quickly without extensive onboarding — because the context is legible from how decisions are actually made. Teams make consistent trade-offs without escalation, because the criteria are embedded in practice rather than residing in a policy document that nobody reads until something goes wrong.

Culture, at its best, is how collective memory becomes collective momentum. Not control, but continuity.

The spiral

The four disciplines are not a checklist. They are movements in a continuous spiral — and the spiral is the point.

Seeing the threads more clearly changes what you design. Designing better structures produces richer patterns to find. Finding those patterns and naming them gives culture something real to anchor to. And a culture that embeds coherence into its daily practice sharpens the perception of everyone inside it, which means the next pass of the spiral starts from a higher point than the last.

This is how coherence scales. Not by adding control, but by adding connection. Not by tightening the structure, but by strengthening the threads that run through it.

The practical implication is that none of these disciplines has an end state. The question is never have we done this? It is always how well are we doing this now, and what would doing it better reveal?

Leaders who sit with that question — who are willing to keep returning to the loom rather than declaring the fabric finished — are the ones who build organisations that hold together under pressure. Not because they controlled for every variable. Because they wove something strong enough to flex.