Structuration
v.2026.02.23
Why Structures Emerge and Why That Changes Everything
Structures are not built; they crystallize from recurring interactions between deeper forces, and lasting change requires working at the level of those forces.
Most organizational change efforts target structures directly: new reporting lines, redesigned processes, merged departments. Most fail within months, with old patterns quietly reasserting themselves. Structuration explains why.
Structures are not root causes. They are effects. Stable configurations that crystallize from recurring interactions between deeper organizational forces: the quality of relationships, the flow of information, the boundaries that shape what is inside and outside, the values that guide selection, and the processes that encode repeated action.
The Flexflow ontology calls this continuous process of crystallization structuration, and it is one of the most practically consequential ideas in the framework. Understanding it changes how you approach every organizational intervention, from a team redesign to a full-scale transformation.
Strategic Imperative
Organizations routinely undergo restructuring cycles every 18 to 24 months. New org charts are drawn, new teams assembled, new processes mandated. Initial optimism gives way to gradual reversion.
Old patterns reassert themselves. People become cynical about change itself. The phrase "here we go again" becomes common. This recurring failure is not caused by poor execution or insufficient commitment. It is caused by a fundamental misunderstanding of where organizational form comes from.
Restructuring targets the visible surface. Structuration reveals the invisible substrate from which that surface continuously regenerates.
Core Definition
Structuration is the continuous process by which interactions among organizational primitives crystallize into stable configurations, persist for a time, and eventually dissolve as underlying conditions change.
Structures are always forming, always persisting, always dissolving. They are not designed once and maintained indefinitely. They are the temporary, visible expression of deeper dynamics. When recurring patterns of relation, information flow, value selection, and boundary negotiation stabilize, a structure appears. When those underlying patterns shift, the structure will eventually follow, regardless of what the org chart says.
This means structures encode the past. Every workflow, team boundary, and governance protocol is a crystallized record of the conditions that produced it. This is useful when those conditions still hold. It becomes a trap when they have changed and the structure has not.
In the Framework
Structuration operates across all three Core Layers.
A (Infrastructure) is where structures are most visibly crystallized: protocols, workflows, data systems, cultural norms.
B (Operation) is where structuration is most actively managed: B1 (Compass) senses when structures have become misaligned with current reality, B4 (Formations) explicitly designs for fluid team structures that can dissolve and reform.
Living Charter (A1) serves as the conscious record of structuration, making the evolution of organizational form traceable and transparent rather than silent and accidental.
Stability vs. Evolution
To change a structure sustainably, change the conditions from which it crystallizes.
Restructuring without changing the underlying patterns of relation, information, value, and boundary is like pruning branches to reshape roots. The visible form returns to its prior shape because the invisible substrate remains unchanged.
The Invisible Substrate
Every organization has two realities. There is the visible one: org charts, job titles, documented processes, official policies. And there is the invisible one: who actually talks to whom, where information really flows, which values are rewarded in practice regardless of what the handbook says, and where the real boundaries of power and trust lie.
Most management attention goes to the visible reality. Structuration says the invisible one is where organizational form is actually determined.
Examples
Org chart, process documents, role descriptions, governance policies
Relationship quality, information flow patterns, enacted values, trust boundaries
How it changes
Mandated from above, redesigned on paper
Shifts gradually through daily interaction, or suddenly through crisis
When misaligned
The org chart says one thing; the organization does another
People route around official processes because the real paths work better
What it encodes
Intentional design
Accumulated history, habits, and unspoken agreements
The ontology names the primitives that constitute this invisible substrate:
Relations (P.REL), the actual quality and pattern of connections between people.
Information (P.INF), what is shared with whom and at what speed.
Values (P.VAL), not the stated ones but the ones that actually guide selection and reward.
Boundaries (P.BND), the real lines that determine who is inside, who is outside, and what flows between.
Processes (P.PRC), the repeated patterns of action that have become encoded intelligence.
The Five Primitives of the Invisible Substrate
The Flexflow ontology identifies eleven universal primitives from which all organizational phenomena are composed.
Five are particularly central to structuration, as they constitute the invisible substrate from which structures crystallize:
Relations (P.REL)
The connections between agents, including their quality, directionality, and strength
The relational fabric determines which structures can form. Structures that contradict the actual pattern of relationships will not hold.
Information (P.INF)
Signals that reduce uncertainty, flowing through and between agents
Information flow patterns create the channels along which structures crystallize. Where information flows freely, coordination structures emerge naturally. Where it is blocked, silos form.
Values (P.VAL)
Active selection criteria that guide decisions and behavior, existing in both explicit (stated) and implicit (enacted) forms
Values determine which structures are reinforced and which are resisted. A structure that conflicts with enacted values will be quietly routed around.
Boundaries (P.BND)
Semi-permeable membranes that define inside and outside, shaping what flows between
Boundaries determine the edges of structures: who is included, who is excluded, and what can pass between. Misaligned boundaries produce either isolation or dissolution.
Processes (P.PRC)
Repeatable patterns of action that encode organizational intelligence
Processes are the most visible form of crystallized substrate. They are "the way we do things," and they carry embedded assumptions about all four primitives above.
For the complete ontology, including all eleven primitives, four meta-classes, and eight axioms, see the Ontology section.
The Audit Question
One of the most revealing exercises any team can perform: look at any established structure (a workflow, a meeting rhythm, a reporting line) and ask, "What has this structure assumed on our behalf?" Every structure carries embedded assumptions about what matters, who should be involved, and how work should flow.
These assumptions were often appropriate when the structure formed. They may no longer be. Making them visible is the first step toward conscious structuration.
A 170-Year-Old Technology
The organizational chart was invented in 1855 by Daniel McCallum, a Brigadier General managing the New York and Erie Railroad.
It was a genuine innovation: a visual tool for representing command hierarchy and reporting relationships in a complex operation. The original chart, hand-drawn and remarkably detailed, looks almost identical to the org charts produced by modern software today.
This is worth pausing on. The fundamental tool we use to represent organizational structure has remained essentially unchanged for 170 years, through two industrial revolutions, the rise of knowledge work, the internet, and the emergence of complexity science.
The resistance to evolving this representation is not laziness. It reflects a deeply embedded assumption: that organization is hierarchy, that structure is reporting lines, and that the most important thing to know about an organization is who reports to whom.
Structuration suggests a different view. The org chart captures one visible layer of organizational reality (vertical authority relationships) while leaving invisible the substrate that actually determines how the organization behaves: lateral trust networks, information flow patterns, enacted values, and the real boundaries of inclusion and influence.
The map is not just incomplete. It is encoding the wrong dimension.
Embedded Normativity
The Values Your Systems Chose for You
There is a specific form of structuration that deserves its own name because of how consequential and how invisible it is. The ontology calls it embedded normativity: the process by which values get absorbed into systems, processes, and infrastructure until they operate automatically, without anyone consciously choosing them.
Every tool, workflow, and protocol carries values within it, whether the designers intended them or not.
A hiring process that filters for prestigious university credentials has embedded a value: "pedigree signals competence."
A meeting structure where the most senior person always speaks first has embedded a value: "hierarchy determines the worth of a contribution."
A performance review system that measures individual output has embedded a value: "work is produced by individuals, not relationships."
None of these values may appear in the organization's stated principles. They operate beneath the surface, shaping behavior silently and continuously.
The ontology distinguishes between two layers of organizational values:
Surface Codes are the values an organization explicitly declares: mission statements, cultural principles, handbooks, onboarding materials. These are visible, debatable, and relatively easy to change.
Deep Codes are the values that have been absorbed into infrastructure, protocols, tools, and spatial arrangements. These are invisible, undebatable (because no one knows they are there), and extremely resistant to change.
The gap between Surface Codes and Deep Codes is one of the primary sources of organizational incoherence. People experience it as hypocrisy: "We say we value collaboration, but every system we use measures individual performance." The dissonance is real, but the cause is not dishonesty. It is embedded normativity. The systems are enacting values that were never consciously chosen.
The Deep Code Audit
A practical exercise for making embedded normativity visible. Select any organizational system (a workflow, a tool, a meeting format, a compensation structure) and work through these questions:
What behavior does this system reward? Not what it claims to reward, but what actually gets reinforced. If the system measures speed, it rewards speed regardless of what the values statement says about quality.
What behavior does this system make difficult? Every structure enables some actions and constrains others. A rigid approval chain makes rapid experimentation difficult, embedding a value of caution over exploration.
Who does this system center? Whose needs, preferences, and working styles does the system default to? A communication tool that requires constant real-time availability centers extroverts and those without caregiving responsibilities.
What would a newcomer learn about "how things really work here" from observing this system? This question cuts through espoused values to enacted ones. The answer reveals the Deep Code.
Organizations that perform this audit regularly develop a capacity for conscious structuration: the ability to see the values their systems carry and deliberately choose whether those values still serve them.
Working with the Substrate, Not the Surface
If structures are effects rather than causes, then the entire practice of organizational change must be reoriented. The conventional approach works top-down and outside-in: design the desired structure, mandate it, en force compliance. Structuration suggests the opposite: work bottom-up and inside-out. Shift the substrate, and the structure will follow.
This is not slower. It is more durable. A restructuring can be announced in a day and implemented in a month. It will unravel in a quarter. A substrate intervention takes longer to initiate but produces change that sustains itself, because the new structure is crystallizing from conditions that genuinely support it.
Restructuring is surgery. Working with the substrate is changing the diet, the exercise, the environment. Surgery has its place in emergencies. But if the underlying conditions remain unchanged, the same pathology will return.
The framework provides specific leverage points for substrate-level intervention, mapped to the five key primitives:
Relations
Change who connects with whom and how
Introduce cross-team pairing, create shared rituals, redesign physical or digital proximity
Information
Change what is visible to whom
Open previously siloed data, create transparent decision logs, shift from need-to-know to open-by-default
Values
Close the gap between Surface Codes and Deep Codes
Audit systems for embedded values, redesign incentives to reward what you actually want, make implicit values explicit and debatable
Boundaries
Adjust what is inside, outside, and what flows between
Redraw team boundaries around value streams rather than functions, create permeable interfaces between previously sealed groups
Processes
Redesign the encoded patterns of action
Replace sequential approval chains with parallel consultation, shift from periodic review to continuous sensing
None of these interventions mention org charts, reporting lines, or departmental structure. Yet each one, if sustained, will produce visible structural change. New collaborative patterns will emerge. New team formations will crystallize. New governance practices will take root.
The difference is that these structures will be grown from living conditions rather than imposed from a blueprint.
The Structural Lag Problem
There is an inherent timing challenge in structuration. Because structures are crystallized from past conditions, they always encode yesterday's reality. When the environment changes, the substrate begins to shift (new information arrives, relationships reconfigure, values are questioned), but the crystallized structure persists for a time, maintained by its own inertia: documented processes, established roles, familiar habits, sunk costs.
This gap between current conditions and crystallized structure is structural lag. Every organization experiences it. The question is how long the lag persists and how the organization responds to it.
Rigid organizations extend structural lag indefinitely. They defend existing structures against the evidence of changing conditions, treating any pressure to change as a threat. Adaptive organizations practice what might be called conscious dissolution: the deliberate recognition that a structure has outlived the conditions that produced it, followed by a graceful release that makes space for new crystallization.
Living Charter (A1) plays a critical role here. By maintaining a transparent, version-controlled record of structural evolution, it makes structural lag visible. Teams can look at when a protocol was last updated, what conditions it was designed for, and whether those conditions still hold. Without this record, structural lag is invisible, and invisible lag compounds until it produces crisis.
Connecting Thread
Structuration explains how organizational form emerges and changes. But the process of crystallization does not happen in a vacuum. It happens within a continuous feedback loop: the organization senses its environment, orchestrates a response, acts, and senses again. This leads to Core Concept 4: A-B-C Cybernetic Loop, which describes the circulatory system through which structuration is constantly informed, guided, and renewed.
Expand Your Understanding
Your gateway to a deeper exploration of Structuration. The following resources provide practical tools, diagnostic frameworks, and theoretical context for working with organizational form at the level of the substrate rather than the surface.
In Practice Real-world application and concrete examples
The Restructuring That Stuck
A 60-person design agency had reorganized three times in four years, cycling between functional departments (design, strategy, production) and client-facing pods. Each restructuring solved one problem and created another. Functional departments produced deep expertise but poor client responsiveness. Pods produced responsiveness but eroding craft quality. Leadership was preparing a fourth restructuring when they paused to ask a different question: "What substrate conditions keep producing these oscillations?"
The analysis revealed three substrate patterns:
Relations: Senior designers had strong peer bonds within their discipline but almost no relationship with strategists. The two groups respected each other abstractly but did not know each other personally.
Information: Client feedback reached the pods directly but was not systematically shared with the functional leads who could identify patterns across clients.
Values: The stated value was "integrated client service." The Deep Code, embedded in the promotion criteria, rewarded individual craft excellence. People optimized for what was actually rewarded.
Rather than restructuring again, they intervened at the substrate:
Created monthly cross-discipline pairing sessions where designers and strategists worked on small briefs together (Relations).
Built a shared client insight repository visible to everyone, updated weekly (Information).
Redesigned the promotion criteria to include peer feedback on collaborative contribution alongside craft quality (Values).
No structural change was announced. Over the following six months, a hybrid form emerged organically: people naturally began forming project clusters that combined functional depth with client focus. The structure the previous three reorganizations had failed to produce crystallized on its own once the substrate supported it.
Conscious Dissolution at Scale
A regional healthcare cooperative of 400 staff had operated with a traditional departmental structure (primary care, specialist services, community health, administration) for over a decade. The structure had been appropriate when the organization served a single community. But the cooperative had expanded to serve three distinct communities with different health profiles and needs, and the departmental boundaries were producing increasingly visible dysfunction: duplicated outreach programs, conflicting community messaging, and specialists who felt disconnected from the populations they served.
Leadership recognized this as structural lag. The existing structure faithfully encoded the conditions of ten years ago (single community, clear specialization boundaries) while current conditions demanded something different (multi-community, integrated care).
Rather than mandating a new structure, they initiated a twelve-month conscious dissolution process:
Months 1-3: Sensing. Cross-departmental teams mapped the actual patterns of care delivery, information flow, and relationship in each community. The maps revealed that informal networks had already begun reorganizing around communities rather than specialties, working around the formal structure.
Months 3-6: Substrate work. New boundary configurations were tested: community-based teams that included primary care, specialist, and community health members. Information systems were reconfigured to flow by community rather than by department. Budget allocation was experimentally shifted to community-level stewardship.
Months 6-9: Emergence. Three distinct community health teams crystallized, each with a different internal structure reflecting the specific needs of its population. The organization did not impose a single model across all three.
Months 9-12: Codification. The new formations were documented in the Living Charter, including the reasoning behind them, so that future teams could understand what conditions the structure was designed for and when it might need to evolve again.
The key insight: the new structure was not designed by leadership. It emerged from substrate conditions that leadership deliberately cultivated.
Substrate Sensing: A Simple Practice
Before any organizational change initiative, map the invisible substrate using these five questions, one per primitive:
Relations
"Who actually talks to whom? Draw the real network, not the org chart."
Information
"Where does critical information get stuck? Where does it flow freely?"
Values
"What does our promotion and reward system actually incentivize, regardless of what we say we value?"
Boundaries
"Which group boundaries feel natural and productive? Which feel artificial or obstructive?"
Processes
"Which processes do people follow naturally, and which do they routinely work around?"
The gap between the answers to these questions and the current formal structure is the measure of structural lag. The larger the gap, the more urgent the need for substrate-level intervention rather than surface-level restructuring.
Common Pitfalls What to watch out for
The Perpetual Restructuring Cycle
Some organizations become addicted to restructuring. Every 12 to 24 months, a new leader or a new strategy produces a new org chart. Each cycle generates temporary energy (the novelty effect), followed by implementation fatigue, followed by the gradual reassertion of old patterns, followed by the next restructuring. People learn to ride out each cycle rather than invest in the new structure, because experience has taught them it will change again soon.
The trap: Treating structure as the primary lever of organizational change.
What it looks like: The organization has undergone three or more significant restructurings in five years. Each was accompanied by compelling rationale. None produced lasting change. A growing cynicism about "change initiatives" pervades the culture. New hires are told informally: "Don't worry about the new structure. It'll change again in a year."
How to sense it: If the same dysfunctions recur after restructuring, the structure was never the problem. Map the substrate (relations, information, values, boundaries, processes) and identify which patterns have persisted unchanged through every restructuring cycle. Those persistent patterns are where the real intervention is needed.
Substrate Neglect: The "We Already Have Good Culture" Assumption
Organizations with strong social bonds sometimes assume the substrate is healthy by default. "Our culture is great. People love working here." This confuses social warmth with substrate health. An organization can have excellent personal relationships (one dimension of Relations) while having severely dysfunctional information flows, deeply misaligned values, and rigid boundaries that prevent adaptation.
The trap: Equating a positive social atmosphere with a healthy substrate.
What it looks like: Teams enjoy working together and report high satisfaction. Yet strategic initiatives repeatedly stall, cross-functional projects are slow, and the organization struggles to adapt to market changes. Leadership is confused because "the culture is strong."
How to sense it: Assess all five substrate primitives independently, not just relationships. Strong Relations with weak Information flow produces "happy but uninformed." Strong Relations with misaligned Values produces "friendly but pulling in different directions." Social health is necessary but not sufficient.
Premature Codification
When new structures begin to emerge from substrate work, there is a strong instinct to codify them immediately: document the new process, formalize the new team, write it into the handbook. This instinct comes from a good place (capturing what works) but can kill the emergence if applied too early. A structure that is still forming needs space to find its natural shape before being locked into a formal definition.
The trap: Crystallizing structures before they have fully emerged.
What it looks like: A promising new collaborative pattern begins forming between two teams. Leadership notices, gets excited, and immediately formalizes it: new roles, new meetings, new reporting lines. The formalization changes the dynamic. What was organic becomes obligatory. The people involved lose the sense of ownership and agency that made the collaboration work in the first place.
How to sense it: Ask whether the structure has been tested across different conditions (quiet periods and busy ones, smooth projects and difficult ones, with the original participants and with new ones). If it has only existed in favorable conditions, it has not yet proven its robustness. Let it mature before codifying. Document it as an experiment, not a policy.
Questions to Explore Prompts for deeper application
On Structures and Their Origins
Pick any established structure in your organization (a meeting format, a workflow, a team boundary). Can you trace it back to the conditions that produced it? Do those conditions still hold?
What structures in your organization exist primarily because "we have always done it this way"? What would happen if they were dissolved for a month as an experiment?
Where do you see the gap between formal structure and actual behavior most clearly? What does that gap reveal about the substrate?
On Embedded Normativity
What values have your tools and systems chosen on your behalf? Run the Deep Code Audit on one system you use daily.
Where are the largest gaps between your Surface Codes (stated values) and your Deep Codes (system-embedded values)? Who experiences this gap most acutely?
If an anthropologist observed your organization for a week without reading any of your official materials, what values would they conclude you hold? How does that compare to your stated values?
On Organizational Change
Think of a change initiative that failed in your organization. Was it targeting structure or substrate? With the structuration lens, what would you do differently?
Where has structural lag accumulated most significantly? What past conditions are your current structures still encoding?
If you could intervene in only one substrate primitive (Relations, Information, Values, Boundaries, or Processes), which would create the most significant structural shift? Why?
On Conscious Structuration
Does your organization have the capacity to consciously dissolve structures that have outlived their purpose? What would that require?
How would your organization be different if every major structure included an expiration date or a regular "do we still need this?" review?
What is the relationship between structural lag and trust? What happens to stakeholder trust when structures silently drift from the conditions they were built for?
Theory & Context Theory, history, and intellectual context
The term "structuration" originates in sociology and has been adapted and extended in the Flexflow ontology to address organizational design specifically.
Structuration Theory (Anthony Giddens)
Anthony Giddens introduced structuration theory in The Constitution of Society (1984) to resolve a longstanding debate in social science: does structure determine behavior, or does behavior create structure? His answer was "both, simultaneously." Structures are both the medium and the outcome of social action. People draw on existing structures to act, and their actions reproduce or transform those structures. This "duality of structure" means that structure is never static but is continuously produced through practice.
Relevance to Flexflow: Giddens' core insight (structure as both medium and outcome) is the theoretical foundation for the framework's treatment of structuration. Flexflow extends this by identifying the specific primitives from which organizational structures crystallize and by making structuration a conscious design discipline rather than a passive sociological observation.
Institutional Theory (DiMaggio & Powell)
Paul DiMaggio and Walter Powell's work on institutional isomorphism explains why organizations in the same field tend to converge on similar structures, even when those structures are not optimal. Organizations copy each other (mimetic isomorphism), conform to professional norms (normative isomorphism), and respond to regulatory pressure (coercive isomorphism). The result is structural similarity driven by legitimacy-seeking rather than effectiveness.
Relevance to Flexflow: Institutional theory explains why so many organizations share the same basic structure (departments, hierarchies, annual planning cycles) despite operating in radically different contexts. Structuration offers a path beyond isomorphism: by working at the substrate level, organizations can develop structures that respond to their actual conditions rather than copying what appears legitimate.
Organizational Routines (Feldman & Pentland)
Martha Feldman and Brian Pentland's research on organizational routines distinguishes between the ostensive aspect of a routine (the abstract pattern, how people describe it) and the performative aspect (the actual enactment, how people do it). These two aspects are always somewhat different, and the gap between them is a source of both stability and change.
Relevance to Flexflow: This maps directly to the Surface Code / Deep Code distinction. The ostensive routine is the Surface Code; the performative routine is the Deep Code. Feldman and Pentland's work provides empirical grounding for the claim that enacted values diverge from stated values in systematic and observable ways.
Sensemaking (Karl Weick)
Karl Weick's work on organizational sensemaking emphasizes that people in organizations are constantly making sense of ambiguous situations and that their interpretations shape what structures emerge. His famous observation that organizations are "talked into existence" aligns with structuration: the stories people tell about their organization, the meanings they assign to events, and the frameworks they use to interpret experience all contribute to the substrate from which structures crystallize.
Relevance to Flexflow: Weick reinforces the Information (P.INF) and Relations (P.REL) dimensions of the substrate. The narratives circulating in an organization are not just descriptions of reality; they are active forces shaping which structures emerge and persist.
Go Deeper Resources for continued learning
Connection to the Ontology
Structuration is classified as a First-Order Emergent Phenomenon in the Flexflow ontology, meaning it arises from the interaction of primitives but is not itself a primitive. Key ontological connections:
All eleven primitives participate in structuration, but the five substrate primitives (Relations, Information, Values, Boundaries, Processes) are most directly involved in the crystallization of organizational form.
Axiom 4 (Emergence Principle) provides the theoretical basis: structures are emergent properties that cannot be reduced to the primitives that produce them, yet they arise predictably from specific substrate configurations.
Axiom 6 (Entropic Maintenance) explains why structures degrade without continuous investment. Crystallization is not a one-time event; it requires ongoing energy to maintain. When that energy is withdrawn (attention shifts, key people leave, priorities change), the structure begins to dissolve.
The Compositional Tiers describe structuration at increasing scales: Primitives (T0) interact to produce Objects (T1), which configure into Patterns (T2), which arrange into Topologies (T3). Each tier is a level of crystallization.
Structuration and the Coherence Geometry
Structuration and Coherence Geometry are deeply interrelated. Coherence describes the quality of alignment. Structuration describes the mechanism by which that alignment is produced and maintained.
When substrate conditions support coherence across all four axes, the structures that crystallize will naturally exhibit multi-axial alignment. When substrate conditions are misaligned (relationships are weak, information is siloed, values are contradictory), the structures that crystallize will encode those misalignments and perpetuate them.
This means that Coherence Geometry is not just a diagnostic tool but a guide for substrate intervention. If the Coherence Compass reveals weak horizontal coherence, the structuration lens directs attention to the substrate conditions producing that weakness: Where are relationships thin? Where is information blocked laterally? What values and boundaries are reinforcing silos? Address these, and the horizontal axis of the Compass will strengthen as new structures crystallize from healthier conditions.
The Paradox of Conscious Structuration
There is a tension at the heart of this concept. Structuration describes how structures emerge from interactions that are largely unconscious, habitual, and distributed. Conscious structuration asks organizations to become aware of this process and intervene in it deliberately. But the moment you intervene deliberately, you risk reverting to the very top-down engineering mindset that structuration critiques.
The resolution lies in the distinction between designing structures (top-down, specific, imposed) and designing conditions (bottom-up, enabling, cultivated). Conscious structuration does not mean centrally planning organizational form. It means deliberately tending the quality of relationships, the openness of information flows, the alignment of enacted values, the permeability of boundaries, and the intelligence of processes, and then trusting that appropriate structures will emerge from those conditions.
This is the cultivation mindset from Core Concept 1 applied to organizational change specifically. The cultivator does not design the shape of the plant. The cultivator tends the soil, provides water and light, and works with what grows.
Structuration and Time
Structures operate on different time scales. Some crystallize and dissolve quickly (a project team that forms for six weeks). Others persist for decades (a governance model, a departmental boundary). The speed of crystallization and dissolution is itself a property worth designing for.
Organizations that are too fluid (all structures are temporary) lose institutional memory and continuity. The Temporal Coherence axis of the Coherence Geometry suffers. Organizations that are too rigid (all structures are permanent) lose adaptive capacity. The Horizontal and Internal axes suffer.
The art of conscious structuration is calibrating the time scale of each structure to its function. Core identity structures (charter, fundamental values, membership criteria) should crystallize slowly and dissolve rarely. Operational structures (project teams, working groups, experimental initiatives) should crystallize quickly and dissolve easily. The Living Charter (A1) provides the mechanism for this calibration: by explicitly categorizing structures by their intended permanence and reviewing them on appropriate cycles.
Suggested Reading
Giddens, A. — The Constitution of Society (1984): the original structuration theory, dense but foundational
Feldman, M. & Pentland, B. — "Reconceptualizing Organizational Routines as a Source of Flexibility and Change" (2003): the ostensive/performative distinction applied to organizational routines
Weick, K. — Sensemaking in Organizations (1995): how shared interpretation shapes organizational reality
Scott, J. — Seeing Like a State (1998): how top-down structural impositions fail when they ignore local knowledge, a powerful complement to the structuration perspective
Laloux, F. — Reinventing Organizations (2014): documented examples of organizations that allow structure to emerge from practice rather than imposing it from above