Beyond Planning Series - Article 3: The Living System

Building Jazz Ensembles: Structuring Structures for Improvisation

(This is the third article in the Beyond Planning Series: Living Systems. The articles explore the intersection of strategy, design, and jazz. You may want to start here with the first article "Beyond Planning Series - Article 1: The Great Unraveling.")

All architecture is what you do to it when you look upon it; Did you think it was in the white or gray stone? or the lines of the arches and cornices? All music is what awakes from you when you are reminded by the instruments, It is not the violins and the cornets, it is not the oboe nor the beating drums, nor the score of the baritone singer singing his sweet romanza, nor that of the men’s chorus, nor that of the women’s chorus, It is nearer and farther than they.

Walt Whitman, “A Song for Occupations”[1]

Prelude · The intelligence in the connections

There were always LEGO bricks in our house. Red ones. Blue ones. Yellow ones scattered among the grey plates across the living room floor. My brothers would sit with me for hours, building alongside me and watching what emerged over days and weeks.

I learned something then that I did not have words for until decades later. The bricks themselves are only part of the system. The deeper ingenuity lives in the connection points. The studs on top. The tubes underneath. The tight engineering tolerance that lets a brick made decades ago connect to one made today. It is a grammar of assembly absorbed through the hands before the mind can put a name to it.

Now I watch my son empty those bricks onto the floor. He builds. He breaks. He rebuilds. The structure teaches him as he shapes it. Each connection carries information about what will hold, what can move, and what might come next.

Organizations work this way too. Their intelligence lives in the connections through which people make sense of a situation and coordinate their response. Plans, leaders, strategy functions, and talented individuals all contribute. Their knowledge becomes consequential when it can travel, meet other knowledge, alter a commitment, and return as action.

People carry part of that connective capacity in themselves. Pierre Bourdieu used habitus for the durable dispositions a person acquires through prolonged experience of a particular social world. Dispositions of that kind operate faster than deliberation. They let a practitioner recognize a situation and act competently before any rule has been retrieved and applied, which is what a grammar of assembly absorbed through the hands amounts to. Bourdieu treated such dispositions as structures formed by past conditions that then work as structuring structures, organizing how subsequent practice is perceived and carried out.[1] An organization contains the same doubling. Its people arrive with dispositions formed by the work they have already done together, and the arrangements those people build go on to form the dispositions of whoever inherits them.

This is the practical meaning of collective intelligence in the Beyond Planning series. The phrase can sound grander than the work. Here it means an organization’s capacity to think and act together. That capacity depends upon where information appears, who can interpret it, how disagreement becomes visible, when people meet, what they are allowed to change, and how experience modifies the system for the next time.

Article 2 stayed with strategic perception: how people notice signals, recognize patterns, and develop a provisional account of the story they may be in. Perception alone does not produce movement. Between recognition and response lies an organizational problem. A signal must cross a boundary. A local observation must enter a shared field. Someone must know who owns the next move. The response must remain coherent with work elsewhere.

Article 3 occupies that middle ground. Its subject is the living organizational system through which distributed knowledge becomes coordinated action.

The word living needs care. An organization remains a social and legal construction, shaped by employment contracts, budgets, power, technology, and human choice. The metaphor earns its place by directing attention to adaptation, interdependence, feedback, memory, identity, and renewal. It reminds us that the performance of the whole emerges from relationships among parts, including relationships that no organization chart can show.

Jazz makes those relationships audible. A small ensemble holds a common form while each player attends to a different part of the music. The bassist carries harmonic movement and pulse. The drummer shapes time and energy. The pianist voices possibility. The soloist develops a line that did not exist a moment before. No player has the whole in isolation. Together, through trained attention and a shared musical language, they create a whole that none could have specified in advance.

Good organizational systems work in the same register. Their structures make work visible. Their rituals synchronize attention. Their policies establish boundaries for action. Their artifacts create common ground. Their feedback loops turn experience into learning. They make room for distinct voices while preserving the identity of the whole.

A living strategy system displaces predictive planning from the center. It consists of recurring practices through which people notice change, construct common ground, exercise judgment, time commitments, learn from consequence, and renew the system itself. Plans remain inside that system as provisional scores. They coordinate action while remaining open to revision as reality changes. Strategic foresight contributes imagined contexts in which assumptions can be examined. Rehearsal lets people encounter consequential situations before the consequences become irreversible. These practices strengthen the connections through which a choice can be understood, made, enacted, and revised. Judgment still determines what the organization should do.

Serendipity needs a system to flow through. So does strategy.

I · When the machine cannot hear

By 2003, the LEGO Group faced a crisis. Reported net sales fell from DKK 11.4 billion to DKK 8.4 billion. An operating profit of DKK 820 million in 2002 became an operating loss of DKK 1.5 billion in 2003. The operating margin fell to minus 17.6 percent. In 2004 the company reported a net loss of DKK 1.9 billion.[2]

The figures document a severe deterioration in performance. Complexity had accumulated faster than the organization’s capacity to coordinate it. Product lines proliferated. Novelty outran the disciplines needed to develop, manufacture, distribute, and learn from it. Different parts of the enterprise could be locally busy and locally rational while the whole became increasingly difficult to understand.

This is a familiar organizational failure. The enterprise appears as a set of functions, and each function is optimized as if the relationships among them will take care of themselves. Strategy sets direction. Design creates products. Operations delivers. Marketing finds the audience. Finance measures the result. The sequence looks clean on a slide because the dependencies have been edited out.

Gareth Morgan described the machine as one of the most powerful metaphors in organizational life.[3] It gave management a language for specialization, standardization, hierarchy, and control. That language remains useful where work is repeatable and variation carries little value. A production line still needs dependable specifications. A safety-critical procedure should not become a nightly jam session.

Trouble begins when the machine becomes the whole theory of the organization. A machine can be decomposed into parts and reassembled according to design. Its components have assigned functions. Its variation is usually error. Organizations operating in unsettled environments face another reality. People interpret the same signal differently. New knowledge enters at the edges. Dependencies shift as the work unfolds. Local variation may be the first evidence that the environment has changed.

The formal chart tells us who reports to whom. It rarely tells us where a problem becomes visible, which team knows enough to interpret it, whose work will be affected, or how quickly a useful response can move. Those are properties of the coordination system.

Karl Weick’s idea of loose coupling helps clarify the design problem.[4] Parts of an organization need enough connection to preserve identity and coordinate interdependent work. They also need enough discretion to respond to local conditions. Coupling that is too tight transmits every disturbance through the whole and forces decisions upward. Coupling that is too loose produces fragmentation, with teams pursuing locally sensible actions that fail when combined.

The issue is therefore the quality of connection. What information travels? Through what artifact? At what cadence? Under which policy? With whose authority? Where can a team vary its response, and where must the system remain invariant?

LEGO’s recovery involved difficult commercial choices, tighter financial discipline, a reduction in unnecessary product and operational complexity, and renewed attention to the core system of play. The organization had to recover the ability to see the whole before it could safely create at its edges. Later phases added an enterprise platform around core processes and, later still, more participatory approaches to leadership and culture. These developments belong to different moments in the company’s history. Together they illuminate a single principle: local creativity becomes scalable when the connections supporting it are dependable.[5]

That principle distinguishes a living system from a loose collection of initiatives. A system joins sensing to action. It gives people a way to locate themselves in relation to the whole. It carries feedback in both directions. It preserves memory while allowing the current configuration to change.

The metaphor of the jazz ensemble is useful here because it holds freedom and structure together. Jazz creates freedom through disciplined form and coherence through reciprocal attention. Its musicians can depart because they know what must continue.

An organization seeking adaptability must answer the same question: what must remain stable so that everything else can move?

II · The rhythm section creates the conditions for coordination

Duke Ellington led from the piano bench, inside the rhythm section and inside the music. His arrangements could be exacting, but the score was never the entire coordination system. The musicians also shared a pulse, a repertoire, a history of playing together, a sensitivity to Ellington’s cues, and an understanding of what each voice could contribute.

Coordination of this kind can arise without anyone directing it from outside. Bourdieu argued that the practices of a group can be orchestrated while remaining unproduced by any orchestrator’s action, because participants formed under common conditions converge on compatible responses without consulting one another.[6] Ellington’s orchestra is an audible case. Fifteen musicians attack a phrase together because rehearsal, repertoire, and years of playing in the same room have made that attack immediately available to each of them. Organizations reach the same condition through practice, and they inherit its liability along with its speed. Dispositions formed under one set of conditions keep producing coordinated action after those conditions have moved. Deliberate mechanisms are what allow an organization to form such dispositions on purpose and to revise them when the environment changes.

The rhythm section is often described as the foundation of a jazz group. The phrase can make it sound passive, as if bass, drums, and piano merely provide a platform while the soloist does the meaningful work. Listen closely and another system appears. The rhythm section continuously establishes time, harmonic location, energy, transition, and expectation. It tells the ensemble where it is without closing down where it may go.

Coordination research offers a rigorous organizational translation. Gerardo Okhuysen and Beth Bechky identify three conditions that enable people to integrate interdependent work: accountability, predictability, and common understanding.[7]

Accountability means that people can see who is responsible for what, including who owns a commitment, a boundary, or a decision. It is larger than blame and more useful than a list of names beside tasks. In a jazz ensemble, accountability is audible. The bassist holds a particular relationship to the pulse and the harmony. The drummer shapes time. A player may challenge the expected role, but the ensemble can hear who is carrying what.

Predictability means that people can reasonably anticipate one another’s actions while leaving room for variation. Musicians surprise one another constantly. The surprise remains playable because it occurs inside a practiced field of expectations. The form will return. The bridge has a length. A rhythmic figure can become a cue. In organizations, predictability grows through stable interfaces, regular cadence, practiced protocols, and explicit commitments. It lets one team act without waiting to inspect every move of another.

Common understanding means that participants share enough of the task, context, and purpose to coordinate their distinct contributions. Complete agreement would add little and may conceal useful differences. An ensemble can contain different interpretations of the tune and still know which tune it is playing. An organization can preserve disagreement about the future while maintaining common ground about the current situation, the decision at hand, and the boundaries of action.

These conditions are the organizational pocket. When they are present, coordination feels fluid because many small acts of interpretation and adjustment happen close to the work. When they are absent, the organization compensates with meetings, approvals, status reports, and escalation. Activity increases as coherence declines.

The three conditions are produced through tangible mechanisms. Okhuysen and Bechky group these around plans and rules, objects and representations, roles, routines, and proximity.[8] In practice, I often see them as a small ecology:

• Roles and decision rights establish who holds which part of the field and where an issue moves when local authority is insufficient.

• Visual management and information radiators give people a shared view of work, dependencies, evidence, and emerging trouble.

• Cadences and meaningful rituals bring attention to the right questions while the information can still change the work.

• Explicit policies and doctrine define the constraints inside which local judgment can operate.

• Boundary objects and shared models let people with different expertise work on the same situation without forcing identical interpretations.

• Feedback and repair loops reveal when coordination has broken and allow the system to learn from the breakdown.

No single mechanism is the system. A digital platform can make information available while leaving ownership obscure. A recurring meeting can produce familiarity while avoiding the consequential questions. A policy can clarify a boundary and still become bureaucracy when the people doing the work cannot revise it. The mechanisms become a living system through their relationships.

Ritual turns recurrence into shared meaning

Cadence tells a group when to return to the work. Ritual gives that return social meaning. A daily flow review, a weekly decision forum, a monthly portfolio conversation, and a quarterly rehearsal of the future operate at different frequencies because the work they coordinate changes at different speeds. Their value also depends upon what the repeated form asks people to notice, remember, affirm, question, and change.

A routine supports dependable execution. People follow it because repetition reduces effort and variation. A ritual carries a second layer. The repeated actions express something about identity, relationship, or purpose. Kursat Ozenc and Margaret Hagan describe rituals as patterned acts imbued with symbolism and meaning. Their work on ritual design also emphasizes intentionality, a recognizable beginning, middle, and end, and enough flexibility for participants to make the form their own.[9] A recurring meeting becomes ritual when the form marks significance for the people taking part and shapes how they enter the work together.

This distinction matters because organizations already contain rituals, including rituals they have never named. The quarterly business review can enact deference to financial authority. The incident review can enact candor and collective responsibility. The promotion announcement can make one form of contribution visible while leaving another unseen. A strategy retreat can widen the field of inquiry or restage the hierarchy in a different room. Repetition carries a lesson about who belongs, whose knowledge counts, what deserves attention, and how the organization responds when its account of reality fails.

Ceremony gives ritual a public audience. It marks an achievement, a loss, an accession to authority, or a change in collective status through witnessed action. Deal and Kennedy described rites, rituals, stories, and heroes as the means through which organizational values become visible in practice.[10] A ceremony therefore reveals more than what the organization says it values. It reveals which contribution receives a stage, which history enters institutional memory, and which people are invited to witness the passage. The absence of ceremony also communicates. Work can end, people can leave, and strategic commitments can be withdrawn with no shared acknowledgment of what has changed.

Ritual gives symbolic form to coordination. A shared artifact provides the group with a focus: a board, an empty chair for the customer, a prototype, a model, a score, or an object carried from one team to another. A trigger separates the occasion from the ordinary flow of meetings. Roles establish who convenes, who reports, who questions, and who can alter a commitment. A sequence moves participants from entry through encounter to closure. The ending returns the group to work with some change in understanding, ownership, or action.

Symbolism without consequence becomes corporate theatre. Operational consequence without meaning remains a routine. Many useful practices contain both.

Thresholds give ritual particular force. Joining a team, assuming authority, completing a merger, retiring a product, recovering from a failure, and leaving an organization all change the relationship between a person and the whole. Anthropological accounts of rites of passage describe a movement through separation, a transitional interval, and incorporation into a changed social order.[11] Organizations usually manage the administrative event and leave the human transition implicit. The calendar invite arrives. Access permissions change. A product disappears from the portfolio. People carry the old identity, unresolved loss, and inherited obligations into the next arrangement.

A transition ritual gives the group a bounded way to acknowledge what is ending, what should be carried forward, and what new responsibilities begin. A product retirement might include the people who built and served it, evidence of what it made possible, an account of why the organization is withdrawing support, and an explicit transfer of knowledge and customer obligations. The form provides closure while preserving learning. Article 6 will develop transition as a strategic problem in its own right. Within the coordination system, unmarked thresholds leave people working from different accounts of which system still exists.

Ritual can also create a temporary change in the quality of time. Operational work tends to flatten experience into an uninterrupted sequence of tasks, alerts, and meetings. A well-designed review creates a protected interval in which the group can slow the flow, place intention beside consequence, and decide what the experience should change. That interval serves the temporal capability developed in Article 5. Article 3 remains concerned with the organizational mechanism: a recurring form that grants people permission to attend differently and brings that attention into contact with authority.

Plurality remains essential. A ritual can create common ground while allowing participants to carry different meanings. People retiring a product may feel pride, relief, grief, anger, or doubt. A designed expression of unanimous enthusiasm would erase information the organization needs. The stronger form establishes a shared occasion, gives several experiences legitimate expression, and connects them to the responsibilities that follow. The group leaves with coordinated commitments and a more truthful memory of the transition.

Power travels through ritual as readily as meaning does. The designer determines who speaks, which object becomes symbolic, what story is repeated, and which ending counts as closure. Participation that is compulsory, emotionally intrusive, or detached from real authority can turn ritual into cultural discipline. A useful ritual therefore exposes its purpose, protects legitimate dissent, and remains open to redesign by the people whose work it coordinates. Ozenc and Hagan’s design research treats local adaptation as one condition of a credible workplace ritual.[12]

Ritual supports accountability when it makes commitments and owners visible. It supports predictability when people know when and how consequential questions will be raised. It supports common understanding when a shared form lets several interpretations encounter one another. The coordination system supplies the test. A ritual earns its place when the understanding created inside it changes a decision, a relationship, an artifact, or a practice outside it.

Cadence detached from purpose becomes meeting theatre. Visual management left outside a recurring practice becomes wallpaper. Policy separated from judgment becomes bureaucracy. Doctrine insulated from feedback becomes dogma.

The rhythm section keeps these elements in relation. It establishes enough continuity for the ensemble to hear deviation, and enough responsiveness for deviation to become information.

JAZZ INTERLUDE [01] · Duke Ellington and His Famous Orchestra · “Cotton Tail”

The call: “Cotton Tail. B-flat. Fast swing. Head in, Cootie takes the bridge, Webster blows, saxes speak as one, brass answer, out head.”

Fifteen musicians. No conductor standing outside the music. Listen to the opening. Brass and reeds strike together as if one mind had produced the attack. The unity comes from a coordination system built through arrangement, role, cue, rehearsal, repertoire, and years of listening.

Ben Webster’s tenor breaks loose early and reveals the system by moving against it. He follows the harmonic form while reshaping its emotional center. The saxophones later speak as a section. The brass answer. Underneath them, Jimmy Blanton’s bass makes harmonic movement and time available to everyone. It is infrastructure you can hear once you know to listen for it.

The ensemble’s coherence preserves difference. Webster sounds unmistakably like Webster. Cootie Williams remains Cootie Williams. Ellington wrote for those particular voices, building human variation into the formal arrangement as a source of musical character.

Your organization has sections too. Can they hand work across a boundary this cleanly? Can one group change the energy without disorienting the others? Does everyone know where the form is, who is carrying the pulse, and what requires a cue?

The lesson: The pocket is a shared field of accountability, predictability, and understanding.

Listen

III · Deep listening requires visible work

John Coltrane’s “Impressions,” recorded at the Village Vanguard in November 1961, creates an extraordinary amount of movement from a spare modal form. The apparent openness intensifies the demand on the players. With fewer harmonic events dictating the path, each contribution carries more information. Listening becomes part of playing.

Organizations praise listening while designing work that makes listening difficult. Information is fragmented across dashboards, slide decks, inboxes, ticketing systems, private conversations, and the memory of people who happened to be present. Each representation answers a local need. Few create a shared field in which a group can see the state of the work and its dependencies at once.

Edwin Hutchins gives us a more useful way to think about intelligence in such settings. His study of navigation shows that cognition can be distributed across people, instruments, representations, and routines. The system accomplishes cognitive work that cannot be reduced to the mental work of any one participant.[13] A ship enters a harbor through relationships among specialists, charts, instruments, spoken reports, and established procedures. The intelligence is in the configured activity.

The same is true of an organization. Its capacity to think depends partly on where memory sits and how representations transform it. A portfolio board remembers commitments. A service map exposes dependencies. A prototype gives physical form to an assumption. A decision record preserves the reason for a choice after the people involved have moved on.

This is why visual management matters. An information radiator is a highly visible display that provides current information at a glance.[14] The best radiators do more than report. They reveal relationships that invite action. They show work in progress, blocked flow, conflicting priorities, aging decisions, uncertain assumptions, and responsibilities that have no owner.

I have written elsewhere that a board serves as an information radiator and a social surface.[15] An accurate task inventory can still leave the system unreadable. A social surface gives people a place to stand together. It externalizes part of the work so that attention, disagreement, and judgment can organize around the same evidence.

The board also changes the conversation. In a meeting organized around verbal updates, each person reports a version of reality from inside a function. The work passes through a series of narratives. On a well-designed visual system, the group can examine the same dependency, blockage, or weak commitment. The object holds the problem still long enough for different forms of expertise to meet.

Visibility does not mean flooding the wall with data. More information can make the consequential difference harder to find. A useful radiator is selective. It makes a promise about attention: this is what the group needs to notice together, at this cadence, in order to coordinate this work.

That promise should be designed around decisions. What must become visible before a team can act? Which conditions require escalation? What evidence would cause a commitment to change? What can the people in this room resolve themselves? The answers determine what belongs on the wall and what can remain in the underlying systems.

Explicit policy performs a parallel function. A work-in-progress limit, for example, is more than a number above a column. It makes a collective agreement visible: we will finish, learn, or deliberately stop before we pull more work into the system. The policy protects flow while leaving people room to decide how to respond. It becomes useful when the people governed by it can see its effects, discuss exceptions, and revise it through evidence.[16]

Cadence turns visibility into organizational sensing. A daily review can detect immediate blockage. A weekly review can examine flow across teams. A monthly review can reconsider allocation. A quarterly session can test whether the assumptions holding the portfolio together still describe the world. Each ritual asks a different question because each addresses a different temporal scale.

Timely synchronization preserves periods of independent work and local exploration. It occurs before divergence becomes expensive and after enough experience exists to make the conversation meaningful.

This is where transactive memory becomes practical. Groups develop a working knowledge of who knows what, who has access to which evidence, and where specialized understanding can be found.[17] A living system does not require everyone to know everything. It makes expertise locatable and creates reliable routes through which it can enter the work.

Deep listening, in this sense, is an architectural achievement. People listen more intelligently when the system makes the relevant voices, objects, timing, and consequences available to them.

JAZZ INTERLUDE [02] · John Coltrane Quartet · “Impressions”

The call: “Impressions. D Dorian to E-flat Dorian. Medium-up. Trane solos long. Bass and drums answer. Bring it home.”

Nearly fifteen minutes. A modal frame built from two tonal centers. Four musicians creating enough variation to make the economy of the structure feel expansive.

Coltrane develops a line at extraordinary length, but the performance is never a saxophone monologue with accompaniment beneath it. Elvin Jones answers intensity with density, changes the pressure of the pulse, then opens space. McCoy Tyner’s voicings create weight and orientation. Jimmy Garrison keeps the ground legible while the surface grows volatile.

The form is sparse enough that interaction becomes exposed. A small rhythmic figure can travel across the group. A change in dynamics becomes a proposal. The quartet does not need to stop and agree on the meaning of every contribution. Its members share enough language, form, and history to respond while meaning is still forming.

Around the middle of the performance, the group reaches what musicians call deep pocket. Coordination no longer sounds assembled from separate acts. The players remain distinct, and the music moves as one. That effect rests on years of deliberate practice, a stable rhythm section, immediate feedback, and attention distributed across the whole.

An organization cannot imitate the sound. It can build the conditions: a common field, visible movement, trusted expertise, and information that travels at the speed of the work.

The lesson: Listening becomes collective when the work gives people something consequential to hear together.

Listen

IV · The jam session creates common ground without demanding consensus

A jam session is a temporary organization. People who may never have played together select a tune, establish a key and tempo, negotiate an order, and begin. The score is incomplete. The coordination system is already present.

The musicians draw upon a shared repertoire, commonly understood forms, embodied conventions, and cues that can be read in motion. They also arrive with different histories and intentions. The purpose of the structure is to make those differences playable.

Organizations often pursue alignment by trying to remove difference. Workshops seek a single shared view. Presentations smooth away disagreement before senior review. Language is polished until distinct interpretations sound compatible. The result can look coherent while preserving the very misunderstandings that will later fracture execution.

Common ground is a stronger aim than consensus. Research on joint activity describes common ground as the pertinent knowledge, beliefs, and assumptions that participants treat as shared for the purposes of coordinating their work.[18] It remains partial and revisable. People need enough mutual orientation to act and enough awareness of difference to know where coordination may break.

Boundary objects help create that condition. Susan Leigh Star and James Griesemer used the term for representations that can adapt to the needs of different communities while retaining a recognizable identity across them.[19] A map, prototype, model, backlog, service blueprint, or operating picture can be interpreted differently by finance, design, operations, and technology. Its value lies in allowing those interpretations to encounter one another through a common object.

I saw this during work with two banking leadership groups preparing for a merger. Their language suggested broad agreement about the future organization. Their LEGO models revealed two different theories. One group built a fortress: controlled entry points, a strong center, and carefully protected assets. The other built a network: distributed nodes, porous boundaries, and value moving through relationships.

Neither model was a neutral description. Each embodied assumptions about risk, customers, authority, and identity. In ordinary discussion those assumptions had remained tacit. Once they occupied the table, the leaders could point to them, move them, connect them, and ask what each implied for the combined institution.

The model became a boundary object that made disagreement available for joint work. Judgment about the future remained with the leaders.

This is the deeper contribution of LEGO Serious Play. The bricks may appear to be the artifact. The real system is the sequence of individual construction, explanation, inquiry, shared modeling, and reflection. Each participant first gives form to an interpretation. The group then develops a shared landscape in which relationships and tensions become visible. The artifact supports the conversation because its meaning remains attached to the person who built it while becoming accessible to everyone else.[20]

One workshop can create insight. A living system requires continuation. In the banking work, the more consequential move came afterward: recurring futures-building sessions, a growing library of models, and cross-functional groups that returned to the landscape as evidence changed. The artifact became infrastructure. What had begun as a facilitated event became a practice through which the organization could maintain common ground over time.[21]

Shared futures create common ground

The future is one of the most consequential objects an organization tries to share, and one of the least available to inspection. It enters the room through forecasts, stories, fears, ambitions, and assumptions. A conventional plan usually compresses those differences into one expected future and then hides the compression. The figures carry the authority of measurement while the argument about the world that might produce them has been removed from view.

Scenario planning can reverse that movement when people use it as a social practice for inquiry. It constructs several plausible external contexts and gives each enough coherence that participants can temporarily inhabit it. Its value lies in watching what happens to the organization’s present assumptions when the surrounding conditions change. A scenario may later resemble events, although its usefulness never depends upon winning a prediction contest.

The Oxford Scenario Planning Approach treats scenario work as a designed process of reframing and reperception. Reframing changes the structure through which participants understand a situation. Reperception occurs when they begin to notice something in the present that their former frame had made difficult to see. Participants produce plausibility through the encounter among different forms of knowledge. An expert probability claim serves a different purpose.[22]

Seen this way, a scenario is a boundary object. Economists, technologists, operators, designers, customers, regulators, and executives may read the same future differently. They do not need to agree about how likely it is, or even about what it means. They need a sufficiently shared context in which their interpretations can meet. One participant may see a regulatory shift as a cost. Another may see it as a source of legitimacy. A third may recognize that the organization lacks the capability to respond under either interpretation. The future becomes a common surface for consequential disagreement.

This changes the purpose of the conversation. The question is no longer, Which scenario do we believe? Belief invites premature convergence and rewards the person with the most authority or confidence. The more useful questions concern correspondence: Which assumptions does this scenario expose? Which commitments remain coherent across several contexts? Where does the strategy depend upon one narrow version of events? What would we need to notice early enough to know that the situation was moving in this direction? Which capabilities would matter under more than one future?

Those questions are sometimes described as wind-tunneling a strategy. A wind tunnel creates controlled variation so that hidden weaknesses become visible before the full structure encounters them in flight. A strategic scenario performs similar work. It lets a group apply pressure to a choice, an operating model, or a portfolio while the cost of discovering fragility remains comparatively low.

The practice also contains a political question. Who was invited to construct the scenarios? Whose evidence became a driving force? Which futures were dismissed as implausible because they threatened the present distribution of authority? A scenario process can widen the field of perception, or it can dress the leadership team’s existing assumptions in imaginative language. The artifact becomes part of a living system only when the people affected by the future have a consequential role in making and revising it.

Jazz offers the right discipline. Musicians can take the same composition into several rooms, tempos, instrumentations, and emotional registers without confusing any performance with the definitive future of the tune. The form creates common ground. The variation reveals possibilities and weaknesses in the ensemble’s repertoire. No imagined performance relieves the musicians of having to listen and choose when the real downbeat arrives.

A scenario makes futures available for joint inquiry, exposes where common understanding is thin, and enlarges the repertoire from which judgment can act. Article 4 will take up responsibility for choosing and justifying action. Organizational coordination requires a shared practice through which the future can become discussable while retaining its status as an imagined context.

The principle reaches beyond models and scenarios. A map used once is a picture. A map revisited through a defined cadence, connected to decisions, and modified by people doing the work can become part of the coordination system.

Policies and doctrine perform similar work in language. An explicit policy states how a local choice will be made: what may enter a workflow, what must be true before work advances, when an exception can be made, who can make it, and how the result will be reviewed. Doctrine operates at a higher level. It provides durable principles that guide judgment across recurring situations without prescribing the exact act.

Both are valuable because improvisation requires boundaries that people can understand before the moment of action. Hidden policy produces politics. Excessive policy replaces thought with compliance. Useful policy makes the constraint visible and leaves room for expertise.

Arie de Geus found the same reasoning in a rose garden. Pruning hard cuts a plant back to three of its strongest stems and three or four growth buds on each, and de Geus gives the reason. “That technique forces the plant to channel all its resources into a relatively small number of growth buds. Why would you prune your roses in that way? Because you want the biggest roses in the neighborhood in June.” He prunes long instead, leaving five to seven stems on each plant and five to seven buds on each stem, because he gardens on a hill where April frosts arrive and deer eat rosebuds. “If I prune hard and the nights are frosty and the deer are hungry, I might have no roses in June at all.” The yield he reports is modest and dependable. “I have never had the biggest roses in the neighborhood, but I do have roses every June.” The policy also generates information the gardener could not have obtained any other way. “In two or three years, some of the spindlier stems have grown much stronger and have begun producing buds, and some of the old stems do not produce roses anymore.” He removes the old stems and encourages the new ones. “A tolerant pruning policy gradually renews the rose portfolio.”[23]

A pruning rule has the properties an explicit policy needs. It is stated before the season begins, it can be argued with evidence about frost and deer, and it can be revised when the hill changes. It trades the maximum available in a good year for a yield the gardener can count on in a bad one. Organizations make the same trade whenever they set a work-in-progress limit or a standing envelope for exploratory funding.

Purpose establishes the outer boundary. A team deciding locally needs to understand the larger promise its decision must serve. Roles establish ownership. Interfaces establish how commitments cross into other work. Rituals create the time at which those commitments can be tested. Artifacts create the space in which their consequences can be seen.

Together, these mechanisms create coordinated plurality: many perspectives held in productive relation, with enough common ground to move.

JAZZ INTERLUDE [03] · Toshiko Akiyoshi–Lew Tabackin Big Band · “Kogun”

The call: “Kogun. Sixteen pieces. Watch the flutes. Let the space be as long as it needs to be.”

Toshiko Akiyoshi wrote “Kogun” in 1974 after reading about Hiroo Onoda, the Japanese soldier who emerged from the Philippine jungle that year still fighting a war that had ended twenty-nine years earlier. The title means a lone soldier, an army of one.

Listen to the opening. Lew Tabackin’s flute enters over percussion. Akiyoshi draws upon Japanese musical materials and asks the brass to bend their sound so that another grammar can live inside the big band. This is deeper than decoration. She uses the established sections of the ensemble while changing the relationships among their voices.

A big band is one of jazz’s most visibly structured forms: saxophones, trumpets, trombones, and rhythm, with musicians reading arranged parts. It resembles a functional organization chart. Akiyoshi keeps the sections and gives them a different field of interaction. The voices remain genuinely distinct. The whole coheres because difference has been composed into the system.

Her achievement offers a demanding organizational lesson. Diversity of perspective does not create value merely by being present. The structure must give different forms of knowledge a consequential role in shaping the work. Common ground must make interaction possible without requiring every voice to become the same.

Akiyoshi treated the big band as an instrument whose internal architecture could be rebuilt. Organizations can do the same. Keep the capabilities. Change the interfaces, cues, permissions, and forms through which they meet.

The lesson: Coherence grows when the system gives difference a form through which to contribute.

Listen

V · Continuous rehearsal turns experience into capability

Art Blakey led the Jazz Messengers for more than three decades. The personnel changed repeatedly. The identity endured. Wayne Shorter, Lee Morgan, Freddie Hubbard, Benny Golson, Cedar Walton, Wynton Marsalis, Terence Blanchard, and many others developed inside the band before carrying what they had learned into ensembles of their own.[24]

Arie de Geus described that pattern with water. A company organized to produce wealth for a few people resembles a puddle, whose drops sit in a hollow until the sun evaporates them. A company organized around its own survival resembles a river, which stays in the landscape while its contents move through it. “No drop remains at the center for long.” “The river lasts many times longer than the individual drops of water it comprises.” De Geus states the conclusion in a single line: “The living company is a river company.”[25] The Messengers were a river. Their continuity lived in the repertoire, the standards, the rehearsal discipline, and the route by which a young player moved from apprentice to bandleader. Turnover carried the identity forward because the system through which people passed stayed legible enough to reproduce itself in each new group.

The Messengers were a performing organization and a learning system at the same time. Rehearsal prepared the band for the stage. The stage also functioned as rehearsal. Each performance placed skill under real conditions, generated immediate feedback, and exposed what needed to be learned next.

Organizations commonly separate these activities. Learning happens in a course. Work happens somewhere else. Reflection waits for the end of a project. Strategy is reviewed at a cadence too slow to influence the decisions through which it is becoming real.

A living system closes those distances. It creates short loops between action, consequence, reflection, and changed practice.

That loop begins with psychological safety. Amy Edmondson defines team psychological safety as a shared belief that a team is safe for interpersonal risk taking and links it to learning behavior.[26] In strategic work, people need to surface bad news, admit uncertainty, ask for help, challenge a frame, and expose an error before the system turns it into a larger failure. General comfort describes too little of what the work requires.

Safety is therefore a property of the coordination system as well as the social climate. What happens when someone places a red condition on the board? Does the ritual create inquiry or interrogation? Can a person stop work at the boundary where they see harm? Does escalation bring resources to the problem or consequences to the messenger? The answers teach the organization what may safely become visible.

Reflection must also remain close to action. The U.S. Army’s after-action review is built around a small set of questions: what was supposed to happen, what actually happened, why the difference occurred, and what should be learned for the next action.[27] Its power lies in disciplined comparison. The review places intent beside reality while memory is still fresh and the people who acted can examine the system together.

Many corporate retrospectives lose that discipline. They collect sentiments, celebrate participation, and create action items that disappear into another system. A useful review modifies something that will shape future behavior: a policy, an interface, a rehearsal, a representation, a role, or a decision rule. Learning becomes organizational when the system changes.

Chris Argyris and Donald Schön distinguish improvements within an existing frame from learning that questions the governing frame itself.[28] Both matter here. A team may improve a handoff while preserving the operating model. It may also discover that the model creates the handoff failure repeatedly. The first adjustment tunes the instrument. The second asks whether the piece requires a different instrument.

The system needs routes for both. Routine reviews can improve flow. Periodic inquiries can examine the assumptions, incentives, and power relationships that make the current flow seem inevitable. Without the second, an organization can become extraordinarily proficient at reproducing a problem.

Communities of practice extend the learning beyond a single team. Jean Lave and Étienne Wenger showed how capability develops through participation in shared practice, with newcomers moving toward fuller forms of contribution.[29] Knowledge is carried through observation, story, correction, imitation, and increasingly consequential work. A manual can support that process. It cannot replace it.

LEGO’s Global Learning Organization illustrates this operationally. During a period of international growth, the company used Training Within Industry methods to build consistent capabilities across plants and cultures. The work treated training as an operating system for developing people through practice, standards, coaching, and continuous improvement.[30]

The Mindstorms community reveals a different learning boundary. After users reverse-engineered the original robotics system, LEGO chose to learn with them. A small group of advanced users participated in developing Mindstorms NXT, and a wider group tested it. The company’s boundary around product expertise became more permeable because the community had demonstrated knowledge the formal organization did not contain.[31]

LEGO Ideas later gave outside creators a structured route into product development. The company itself describes the platform as crowdsourcing and co-creation. Proposals gain public support, qualifying projects enter formal review, and selected ideas become commercial sets. The community expands the field of possibility. LEGO’s review process preserves responsibility for feasibility, safety, quality, and brand.[32]

Permeability can overwhelm an organization when new ideas have no route through review. A closed review system protects the existing repertoire from evidence that might change it. A living system admits learning across an open boundary and uses an explicit boundary to govern commitment.

The same applies internally. A useful experiment needs enough protection to generate evidence and a defined route through which that evidence can affect the larger system. Otherwise the organization accumulates pilots that never alter policy, funding, architecture, or behavior.

Rehearsal works in the small before consequences arrive at scale

Rehearsal builds the organization’s capacity to respond before the stakes become existential. Teams can simulate a disruption, walk through a decision boundary, test a handoff, role-play an escalation, or model how a customer problem moves across functions. The exercise reveals where common understanding thins, where ownership becomes ambiguous, and where the current repertoire proves too narrow. Its usefulness never depends upon forecasting the event that later occurs.

Much organizational learning remains propositional. People are told a method, shown a process, given a case, and asked to carry the lesson into conditions that behave differently from the classroom. They may understand every sentence and still be unable to coordinate when the situation begins moving. Complex performance depends upon knowledge that has passed through experience: the felt recognition of a bottleneck forming, the ability to hear uncertainty in a colleague’s report, the memory of what happened when a team delayed an escalation, and the practiced confidence to intervene without waiting for perfect information.

Hubert and Stuart Dreyfus argued that expertise develops through situated experience.[33] Rules support the early stages by directing attention. Continued practice changes how the person encounters a situation. Patterns become available directly to perception, and action becomes more responsive to context. The competence is embodied in what the practitioner notices and is prepared to do.

I see this shift whenever teams run the getKanban simulation. In roughly four hours they live through a quarter of product development. They make prioritization decisions, encounter bottlenecks, watch work accumulate, feel the cost of delay, and see financial consequences emerge from choices that sounded reasonable when discussed abstractly. Somewhere around the middle, the language changes. Participants stop reciting principles and begin responding to the physics of flow. The board and rules recede from attention. The team starts to cope with the system as a system.[34]

The compression of time matters. A real organization may take months to reveal the consequence of overloading a delivery system. By then, personnel have changed, memory has thinned, and the chain connecting decision to result has become disputable. A simulation shortens the loop. People can make a choice, observe its consequences, revise their coordination, and try again while the original reasoning remains available for examination.

Repetition alone, however, can make a team fluent in the wrong response. Useful rehearsal introduces variation. The customer behaves differently. A critical role disappears. The available data arrives late. The constraint moves. A trusted supplier fails. The scenario should be plausible enough to engage professional judgment and unfamiliar enough to prevent the participants from executing a memorized script. The exercise builds a richer repertoire of recognizable situations and possible responses.

Simulation and experimentation serve different purposes. A simulation is a bounded representation of a system. It allows people to rehearse coordination and encounter modeled consequences while leaving the operating environment unchanged. A safe-to-fail probe intervenes in the real system at a scale where failure can be contained and detected. The probe gathers evidence about how a complex situation responds.

In a complex system, the outcome of an intervention cannot be known in advance. Snowden therefore recommends several small and even contradictory probes run in parallel. When a probe begins to produce a beneficial pattern, the organization amplifies it. When it produces harm, the organization dampens or stops it.[35] That approach requires boundaries, sensors, an accountable owner, a review cadence, and a route through which a positive pattern can receive more resources. An organization lacking those mechanisms launches small projects and interprets them after the fact. It has no dependable experimental system.

Article 4 will consider the judgment required to choose, constrain, and interpret such probes. The concern here is the instrument through which that judgment becomes executable: whether the organization can detect what the intervention is producing, stop it before damage escapes its boundary, and carry a promising local pattern into wider practice without stripping away the conditions that made it work.

Rehearsal prepares people to operate that learning system. It lets them practise detecting a threshold, calling attention to a weak condition, transferring authority, stopping an intervention, and conducting the review through which the system decides what changes next. The object of rehearsal is therefore larger than the scenario. It is the network of roles, representations, cues, and permissions that must work together when the unexpected arrives.

The debrief completes the loop. A simulation without reflection can produce excitement without learning. A review should place intention beside consequence: what did we expect, what occurred, which assumptions failed, what did the system make difficult, and what will change before the next repetition? The answer must alter something durable, such as a policy, interface, signal, threshold, role, model, or practice. Otherwise the lesson remains inside the people who happened to be in the room.

This is how learning in the small becomes capability at scale. The organization does not attempt to script every future performance. It develops people who have encountered variation, a system that can make consequential differences visible, and pathways through which useful responses can spread. When the real moment arrives, they may not have seen that exact event before. They have practised how to notice, coordinate, adapt, and learn together.

The performance still matters. Rehearsal without contact with real work becomes theatre of another kind. Blakey’s musicians developed because the learning had to survive the bandstand.

JAZZ INTERLUDE [04] · Art Blakey and the Jazz Messengers · “Moanin’”

The call: “Moanin’. F minor. Bobby calls, horns answer. Lee first, Benny second. Keep the shuffle under it. Take it home.”

The opening makes coordination visible. Bobby Timmons states the phrase. The horns answer. Call and response is the composition, but it is also the learning system. A proposal enters the shared field. The ensemble recognizes it, returns it, and gives it greater force.

Lee Morgan’s trumpet solo arrives with a voice already unmistakably his own. Benny Golson follows with another vocabulary and another shape. Blakey does not ask either musician to disappear into the band’s identity. The Messengers’ identity is strong enough to develop individual voices and permeable enough to be changed by them.

Listen to Blakey beneath the soloists. He teaches through pressure, accent, space, and propulsion. The feedback is immediate. A phrase that lands is met by the band. An opening becomes an invitation. The performance tells the musician what the classroom cannot.

The band’s long history reveals how the system renewed itself. Musicians entered, learned the repertoire and discipline, contributed their developing voices, and left to lead. The personnel renewed the organization while the practice carried its identity forward.

Every organization needs places where emerging leaders can hold real responsibility with a practiced ensemble around them. The work must be consequential enough to teach, and the system safe enough to learn.

The lesson: Capability grows when practice, performance, feedback, and succession become one loop.

Listen

VI · The living orchestra is a designed ecology

The language of living systems can tempt us toward vagueness. We speak of emergence, adaptability, trust, and flow as if an organization might acquire them through aspiration. The jazz ensemble helps because its apparent spontaneity rests on visible disciplines. The musicians have instruments, roles, forms, repertoires, rehearsal practices, cues, and standards. They have also built the relational capacity to use those structures under pressure.

The organizational equivalent is a designed ecology. It combines formal and informal elements whose interaction produces the capacity to think and act together.

Five questions help test that ecology.

Can people see the state of the work and the situation?

Visibility includes more than progress. People need to see dependencies, constraints, uncertainty, commitments, and the evidence behind important claims. The representation should be close enough to the work to remain current and selective enough to direct attention.

The test is behavioral. When the display changes, does anyone know what to do? A display that leaves behavior unchanged is reporting. Visual management connects the representation to action.

Do cadence and ritual fit the work?

Every recurring practice establishes a clock. Some work needs daily coordination. Some assumptions should be revisited quarterly. Some principles should endure for years and change only through deliberate review. A single planning cycle cannot hold every frequency.

Ritual adds a second design question: what meaning should the occasion carry? A daily coordination practice usually needs low intensity and a dependable form. A product retirement, leadership succession, or post-merger transition may happen once and require stronger symbolism, witness, and closure. Frequency, intensity, and consequence should fit the work and the people living through it.[36]

The useful question is whether information encounters authority while it can still change the outcome. A monthly meeting cannot coordinate a service that changes hour by hour. A daily meeting should not repeatedly reopen a durable strategic commitment.

Are the boundaries of action explicit?

People improvise more confidently when they know where discretion begins and ends. Purpose, doctrine, policy, technical standards, financial limits, and safety constraints provide different kinds of boundary. They should be legible to the people whose judgment they shape.

An explicit boundary can be challenged through evidence. An invisible boundary survives as custom, status, or fear.

Does ownership sit near enough to knowledge?

Distributed decision-making fails when authority is dispersed without accountability. Centralized decision-making fails when ownership is separated from the richest information. The design task is to place decisions where sufficient knowledge, consequence, and responsibility can meet.

Escalation then becomes a purposeful interface. It should add perspective, resources, or authority that the local system lacks. If escalation merely repeats the same conversation at a higher salary level, the architecture is creating delay.

Does experience change the system?

Every organization has feedback. The question is where it goes. Customer behavior, operational failure, experiments, and frontline judgment can disappear into reports without altering a commitment. A living system converts experience into changed practice. It revises an explicit policy, a model, a role, a threshold, a rehearsal, or the question being asked.

These tests reveal why technology alone cannot create a living organization. A collaboration platform can accelerate connection and amplify confusion. A dashboard can increase visibility and concentrate attention on the wrong measures. An artificial intelligence system can make knowledge easier to retrieve while obscuring who is accountable for using it. Technology changes the possible speed and scale of the system. Organizational design determines whether that capacity produces coherence.

LEGO’s history helps us separate several layers. The brick system provides a durable technical and conceptual grammar. The commercial turnaround restored focus and discipline. The enterprise platform strengthened common processes over the following years. Open innovation communities changed how knowledge crossed the firm’s boundary. The later Leadership Playground invited employees to shape a shared practice of leadership around three behaviors: being brave, curious, and focused.[37]

None of these elements explains the whole. Together they show an organization repeatedly working on the conditions through which people could coordinate. The platform handled some forms of predictability. Communities created routes for knowledge. Shared behaviors and facilitated conversations supported common understanding. Commercial and design governance clarified accountability.

The system remained human, which means it remained incomplete, political, and capable of failure. Calling it living should heighten our attention to those qualities. It should never romanticize them away.

Power is part of the architecture. Who may place an issue on the board? Whose interpretation becomes doctrine? Which teams can make exceptions? Who absorbs the cost of a local optimization? A visual system can widen participation or become another surface on which authority performs certainty. A ritual can enable candor or discipline dissent. A boundary object can create common ground or conceal that one group retains the right to define reality.

Healthy coordination therefore requires repair. People need a way to say that the system is no longer producing accountability, predictability, or understanding. They need the authority to change the mechanism, and the organization needs a memory of why it changed.

This is where the LEGO brick remains such a useful teacher. The clutch between bricks is dependable. The arrangement is provisional. A structure can be taken apart without destroying the pieces or their capacity to reconnect. The system preserves identity at the level of the interface while allowing enormous variety at the level of composition.

Organizations cannot achieve that degree of modular purity. Their histories and relationships do not separate cleanly. The design principle still holds: articulate the enduring commitments, keep the current configuration revisable, and invest in the interfaces through which people rebuild.

Arie de Geus used the living company to ask why some enterprises survived across generations.[38] The Shell study he reports found that each of the twenty-seven long-lived companies with reasonably well documented histories had changed its business portfolio completely at least once. In de Geus’s account “assets” … “are like oxygen: necessary for life but not the purpose of life.” Stora began as a copper mine in central Sweden and became a paper, pulp, and chemical manufacturer across more than seven centuries. “Stora was in copper in order to exist; it did not exist to be in copper.”[39] An organization that loses that distinction defends its present configuration as though the configuration were its identity, and every coordination mechanism then works to preserve the arrangement while evidence against it has nowhere to travel.

The four traits de Geus reports across those companies each name a property of a coordination system. Conservatism in Financing keeps spare capital available so that options can be taken when competitors cannot take them. Sensitivity to the World Around Them keeps the organization attuned to news it did not commission. Awareness of Their Identity lets employees across widely diversified operations understand themselves as parts of a whole. Tolerance of New Ideas permits experiments and eccentricities at the margin that stretch what the organization understands.[40]

Articles 6 and 7 take up that larger question through transition and regeneration. Continuity depends upon a system capable of renewing its arrangement while carrying identity and learning forward.

The Jazz Messengers did this through repertoire, leadership, rehearsal, and succession. LEGO does it through a compatible system of play that supports continuous recombination. An organization does it when its knowledge can move, its commitments can be examined, and its people can alter the structure without losing the purpose that makes them a whole.

The result is coherence without uniformity. It is also freedom through disciplined form.

Coda · The instrument does not decide

Whitman puts music somewhere unexpected. It is what awakes from us when the instruments remind us. The instrument matters. Its shape establishes what can resonate, which notes can be reached, and what kind of touch the sound will answer. Yet it waits for a player, a room, and a moment.

Organizational systems work in the same relationship. A board gathers attention. A ritual gathers people inside a meaningful interval. A policy establishes a boundary. A model gives disagreement a form. A feedback loop carries consequence back into practice. Together they make coherent action possible.

Judgment remains the human work.

That boundary matters as this series turns from perception and coordination toward judgment. A living system can bring weak signals into view, connect them to operating reality, and place different interpretations in productive relation. It can locate expertise, clarify ownership, and shorten the distance between experience and learning. The choice still carries uncertainty.

The quality of the instrument shapes the quality of the possible music. The quality of the musicians shapes what becomes actual. Strategy requires both.

Coleridge heard the same relationship in an Aeolian harp placed in an open window. The instrument had a form. The air supplied motion. The sound emerged between them.

Methinks, it should have been impossible Not to love all things in a world so filled; Where the breeze warbles, and the mute still air Is Music slumbering on her instrument.

[…]

And what if all of animated nature Be but organic Harps diversely fram’d, That tremble into thought, as o’er them sweeps Plastic and vast, one intellectual breeze, At once the Soul of each, and God of All?

Samuel Taylor Coleridge, “The Eolian Harp”[41]

Leadership in a living system has at least three obligations. Build the instrument well enough that knowledge can move through it. Keep it tuned by allowing experience to change its mechanisms. Then accept responsibility for the judgment that no instrument can make.

The next article begins there, in the interval between what the system can reveal and what a leader, a team, or a community must choose.

Next in the Series

Article 04 · Navigating Uncertainty: Negative Capability, Strategic Judgment and the Gift of Limits