II. Structure

06 May, 2025

Structure is not static. It is not just an org chart, nor a list of roles. It is enacted daily, piece by piece, in how decisions are shaped, how work is interpreted, and how permission is granted or denied. What we call “structure” is made real through a set of recurring elements — visible in action, audible in delay, and traceable through how information travels.

I consider structure manifests through four interdependent components: ideology, relationships, processes, procedures, and each shaped and conditioned by a fourth: legacy.

Ideology

Ideology is the implicit logic through which an organization constructs meaning, legitimizes decisions, and justifies authority. It governs what is seen as credible, necessary, or possible — not only in present operations, but in the organization’s imagined future.

Functioning as a projective lens, ideology frames the organization’s self-conception over time: who it believes it is becoming. It informs strategic direction, shapes expectations about behavior, and filters what kinds of structures, roles, and decisions are viewed as legitimate or illegitimate.

Because ideology precedes both culture and stated values, its first visible imprint is the business model. The dominant logic limits what the organisation can accept: a remote‑first platform with a flat salary, a worker‑owned cooperative with member‑approved share ratios, a scale‑driven firm with performance‑tiered bonuses — each design signals a different economic story.

The same logic shapes the reward system. Pay formulas, monitoring practices, promotion paths and power distributions crystallise the organisation’s beliefs about contribution and fairness.

Trouble begins when ideology alters without being named. If rewards start following a new logic while language and structure claim the old one, the organisation keeps running but becomes harder to read. Contradictions multiply, interpretation work grows and people improvise.

What matters is not whether ideology evolves — it will — but whether the system can recognise and absorb that evolution without pretending nothing changed.

Relationships

They are not just formal reporting lines, but the habitual paths of trust, influence, and translation that shape how work flows — or stalls.

These relationships carry the structure between people. They decide who reaches out first, who hesitates, who gets copied and who doesn’t. They mediate between written rule and lived reality.

Some relationships are deliberately designed — embedded in organizational charts, team structures, or department mandates. Others grow informally around gaps in the system — someone who explains what the form really means, someone who gets it signed faster, someone who knows the real deadline.

A structure may prescribe a process and codify a procedure — but the real movement often follows the lines drawn by relationships. These are the conductors of organizational energy. Where they are strong and reciprocal, work accelerates. Where they are brittle, blocked, or politicized, effort slows, fragments, or is rerouted in silence.

At their best, relationships translate the structure into something human and navigable. At their worst, they become hidden architecture — invisible chokepoints or unsanctioned dependencies that no one planned, but everyone obeys.

Processes

This is how decisions become action. But they are also how decisions are formed. A process links the actors, the expertise, the collective intelligence, the timing, and sequencing that turn an intention into coordinated work. It involves not just steps, but analysis, legitimacy, interpretation — who is consulted, whose voice carries weight, when a question becomes a decision.

A coherent process is one where decision-making is clear and credible. When processes become fragmented or overly layered, action loses momentum. Confidence is replaced by double-checking and workaround.

But process also needs a receptacle — a way to be stabilized, remembered, validated, and transmitted. That role is carried by procedure.

Procedures

They are the formal scripts of process. They define how things should happen: what steps are required, who approves, which forms are used. But procedures do more than guide — they express authority.

They show who is entitled to act, who must validate, and where accountability sits. They become the recognizable imprint of organizational judgment: decisions written down, steps fixed into form. The outcome becomes predictable — or at least reproducible.

Procedure also acts as memory. It holds the logbook of process — a way to stabilize and repeat what works, while signaling how permission is passed. This stability can erve clarity — or rigidity. When procedures evolve with practice, they create confidence and reliability. When they fall behind, they misalign — rules without rhythm, obligations without support.

At their best, procedures are the visible surface of shared intent — faithfully containing the process they were designed to hold. They are not only memory logs or recipes for expected results, but also evidence that the decision-making process has passed through the necessary counterweights of authority, expertise, and legitimacy.

At their worst, they overspill, become inoperable, and demand more effort to be worked around or quietly bypassed.

Process and procedure are not isolated mechanics. They become operational — and meaningful — through the relationships that form and evolve within the structure.

Legacy

This is the most subtle element of structure — and often the most enduring. It is not a separate layer but a presence braided through every other component. It shapes how processes are imagined, how procedures are written, and how relationships are lived.

Legacy is made of habits, constraints, old tools, unspoken norms — and also of the deeper assumptions: the values and beliefs about how work should be done, who is seen as credible, what counts as initiative, or what “leadership” ought to look like. These are not always written down. They are carried in tone, in expectations, in how roles are interpreted or rewarded.

They are the residue of decisions made under pressure, of workarounds that became routine, of practices that once served a purpose and were never revisited. They exist in language, in defaults, in informal rituals and approvals that no longer make sense — but remain.

Legacy holds continuity and coherence, but it can also resist adaptation. What was once efficient can become invisible friction. What once fit can become constraint.

Legacy is not inherently negative. It anchors meaning, maintains memory, and protects from chaos. But when it escapes reflection, it becomes the layer that silently steers the rest — not always in the right direction.

To understand structure, legacy must be read not only in what is written, but in what is taken for granted — and what is unconsciously protected.

The Structural Logic: Information as the Measure

At its core, this framework proposes a shift in how we understand and assess organizational structure. Structure is not a fixed arrangement of people and tasks — it is a living system for transmitting and transforming information.

Structure enables coordinated effort by shaping the flow of information — bit by bit. These bits are not abstract. They are fragments of decisions, signals of change, contextual details, justifications, doubts, and authorizations.

When a bit is dropped or distorted, the structure begins to strain.
When a bit arrives late or incomplete, effort becomes misaligned.

This is why structure must be assessed through how it treats information — through its integrity, quality, and its speed.

Information Integrity

Does the structure preserve meaning as information moves?
Can a request travel without its context being stripped?
Does a decision retain its intent by the time it is implemented?

When integrity fails, people double-check, second-guess, or work from the wrong premise.

Information Quality

Does information gain clarity as it moves — or lose it?
Healthy structure refines the signal: it filters noise, adds relevance, sharpens context.
Fragile structure dilutes it — through handoffs, ambiguity, or gaps in authority.

Speed

Can information move quickly enough to matter?
Some delay is natural. But structural drag — redundant validation, looping approvals, invisible bottlenecks — steals timing.
And when speed is lost, decisions become stale, and effort misses the mark.

When a structure fails on one of these fronts, the organization doesn’t collapse — it compensates. It sends reminders, adds layers, re-explains, and over-relies on a few “knowers” who patch the gaps.

These are not neutral adaptations. They are the cost of bit loss: effort wasted, energy rerouted, trust worn thin.

And the cost grows silently.

This framework invites us to design not only for structure as form —
but for structure as flow.Because what holds an organization together is not just hierarchy or intent — but the everyday movement of meaning.

And Then, the People…

Information doesn’t move in a vacuum. It moves through people. When structure fails to carry information with integrity, quality, or speed, the breakdown doesn’t only show up in delays or rework.
It shows up in people — in how they feel, how they respond, and how they perform.

This is why the design of structure is also tested — through the experience of those working within it.

We see this in small, daily frictions:

When someone is asked to provide information they never received.
When decisions arrive without context — and unravel on the ground.
When approval loops stall and people quietly stop asking.
When no one knows who owns a step — and everyone hesitates.

These are not personal failures. They are structural signals. They show what happens when people are left to absorb the cost of the bit loss — when the system no longer holds what it should, and so the burden shifts.

Over time, that burden becomes visible in familiar metrics:

Absenteeism — when presence fades before departure.
Attrition — when people quietly exit what no longer makes sense.
Disengagement — when effort recedes in the face of structural incoherence.

And in subtler, systemic symptoms:

Over-reliance on informal “knowers” — individuals who carry context the system should remember.
Shadow systems — informal processes built to bypass formal blockages.
Repeated clarification loops — time lost re-explaining what structure should have made clear.
Silent drift — when people stop asking questions, not because they agree, but because they no longer expect coherence.

These are not just HR indicators. They are echoes of structural misfit — signs that the system is no longer returning information in a usable way.

People compensate for these gaps — until they can’t. And when they can’t, the organization pays: in confusion, in morale, in missed opportunities.

To ask how people are doing inside a structure is to ask:
Is the information reaching them? In time? In full? In a form they can use?

This is where structure becomes real — not as design, but as experience.
The runner feels the track shift underfoot. And every silence, delay, or workaround is a sign: the structure did not hold its part.