Organisational Mimoids

I.

In Stanisław Lem’s Solaris, the ocean that covers the planet produces formations of staggering complexity. Symmetriads rise and collapse over hours, their internal geometries exhibiting architectural precision — arches, vaults, cantilevered structures that seem to obey engineering principles no one taught them. Mimoids replicate objects placed near the ocean’s surface, reproducing their forms with eerie fidelity while containing none of their function. The formations have the appearance of design. They have the structure of intention. But the ocean is not designing anything. It is not trying to build a symmetriad. It produces, and what it produces resembles architecture, and the resemblance is the beginning of a problem that the novel never resolves.

Organisations produce formations too. Reporting lines, team boundaries, committee structures, approval chains, the concentric access hierarchies of any company large enough to have an inside and an outside — these have the form of intentional design. They look as though someone sat down and reasoned about information flow, span of control, the separation of concerns. Occasionally someone did sit down. There was a meeting. A whiteboard was involved. But what emerged from the meeting rarely matches what the organisation became, and what the organisation became — the actual topology of who talks to whom, who approves what, where information accumulates and where it starves — accreted rather than being designed. It formed the way a mimoid forms: by proximity, by happenstance, by the particular pressures that happened to be present at the particular moment a structure was needed, producing something that resembles rational architecture without containing it.

The matrix organisation is a symmetriad. It rises with impressive internal geometry: dual reporting lines, cross-functional integration, the elegant promise that every decision will be informed by both the functional speciality and the business context. Consultants present slides showing the matrix’s logical necessity. The slides are persuasive. The matrix is built. And then it does what symmetriads do — it operates according to its own internal dynamics, which are not the dynamics anyone intended, and which produce coordination failures, responsibility diffusion, and the particular kind of organisational paralysis where every decision requires two approvals and neither approver believes the decision is theirs to make. The matrix has the form of rational design. It emerged from something that is not rational design. The gap between the form and the origin is the gap that Lem spent an entire novel trying — and failing — to close.

II.

Solaristics, in Lem’s telling, is what happens when human beings encounter the ocean. They observe its formations. They classify them. They develop competing theoretical frameworks — the Giese school, the Symmetriadists, the minimalists who argue the ocean is merely complex chemistry — and publish papers and hold conferences and build a library that, by the time Kelvin arrives on the station, has grown so vast that no single researcher can master it. The library was built to understand the ocean. But the library long ago stopped being about the ocean and became about itself. Solarists read other Solarists. They refine taxonomies of taxonomies. They argue about whether Giese’s classification of mimoid subtypes is compatible with Grenaud’s morphological framework, and the argument generates more papers, which generate more arguments, which generate more papers, and the ocean goes on producing formations that no one is watching anymore because everyone is in the library.

Management theory is Solaristics.

The ocean — the thing that actually happens inside organisations — produces formations. Teams form and dissolve. Power accretes around individuals and dissipates when they leave. Information flows through channels that no org chart depicts. Coordination succeeds or fails for reasons that are local, contingent, and rarely visible to anyone not standing in the specific hallway where the specific conversation happened at the specific moment when one engineer told another that the API was about to change. These are the ocean’s productions. They are real, they are complex, and they are happening all the time.

Management theory observes these formations and classifies them. There are taxonomies. Tuckman gives us forming, storming, norming, performing — four stages through which every team supposedly progresses, a morphological classification as clean as anything Giese proposed for mimoids. Mintzberg gives us five structural configurations: simple structure, machine bureaucracy, professional bureaucracy, divisionalized form, adhocracy. The McKinsey 7-S Framework gives us seven elements beginning with S, because the taxonomy must be memorable and the mnemonic is the point. Team Topologies gives us four fundamental team types. The Spotify Model gives us squads, tribes, chapters, and guilds, a taxonomy whose Nordic terminology lends it the authority of an ethnographic discovery, as though the authors had ventured into the field and identified species.

And then the library becomes about the library. Consultants cite other consultants. A paper on “agile transformation” references not the experience of any particular team but the framework proposed by another paper on agile transformation, which referenced a third paper, which referenced a conference talk, which referenced a blog post that described what happened at one company in 2008, and by the time the chain of citation is four links long the ocean is no longer visible. What is visible is Solaristics: a self-referential body of literature that classifies, reclassifies, synthesises, and disputes its own classifications with the productive energy of a field that has long since decoupled from its object of study.

The Harvard Business Review is the Solarist library. It is vast. It is internally coherent. It generates more of itself at a rate that makes comprehensive reading impossible, which is convenient because comprehensive reading would reveal that the library has been producing the same twelve arguments in rotating configurations for forty years, in the same way that the Solarist library produces new classifications of formations the ocean stopped producing decades ago. The library’s growth is not evidence of progress. It is evidence that the recording surface has become self-sustaining.

III.

The Mimoid Problem, as it applies to organisational formations, is this: you cannot tell from the outside whether a given structure was designed or accreted.

A company has a platform team. The platform team exists because three years ago one engineer built an internal tool, and other engineers started using it, and management noticed that the tool was being used and retroactively designated the engineer a “platform engineer” and gave them a team. The team grew. It acquired a mission statement. It developed a roadmap. It now has quarterly OKRs aligned to the company’s strategic pillars. From the outside — from the perspective of someone reading the org chart or the team’s wiki page — it looks like the platform team was created to fulfil a strategic need. It has the form of intentional design. But it was not designed. It accreted around a tool that one person built because they were annoyed by a deployment process. The strategy was applied after the fact, the way Solarists apply morphological categories to formations the ocean produced for reasons no one understands.

Is this a problem? It depends on whether you believe the distinction between “designed” and “accreted” matters. The platform team functions — or it doesn’t. Its origin is irrelevant to its performance. But the Mimoid Problem is not really about origin. It is about detection. Because the moment you cannot distinguish a designed structure from an accreted one, you lose the ability to diagnose organisational dysfunction. If a team is failing, is it failing because it was poorly designed, or because it was never designed at all — because it is a mimoid, a formation that resembles a team without containing the intentional properties that would make it one? The diagnostic question (“Is this team well-designed?”) presupposes that the team was designed. If it was not designed — if it merely formed — then the question is meaningless, and any answer to it is itself a mimoid: something that has the shape of a diagnosis without containing diagnostic content.

Every framework for assessing organisational health exhibits this property. Take Lencioni’s Five Dysfunctions of a Team, which proposes that teams fail because they lack trust, fear conflict, avoid commitment, dodge accountability, or neglect results. The framework has the structure of a diagnostic instrument. But “trust” is not a measurable property — it is a Mimoid word, a term that imitates precision without containing it. A team either has trust or doesn’t, but the determination of whether it does depends on criteria that are themselves vague (Do people speak up in meetings? Do they share personal information? Do they admit mistakes?), and the criteria are assessed by an observer who must decide whether the observed behavior constitutes “trust” or merely resembles trust, and the framework provides no method for making that distinction. The framework is a Mimoid. It has the form of a diagnostic tool. It is not a diagnostic tool.

The recursive property is the crux. Any instrument you build to detect whether an organisational structure is a Mimoid will turn out, upon examination, to be a Mimoid itself. The Selb Criteria fail in management theory for the same reason they fail in Solaristics: the criteria are made of the same material as the thing they are trying to diagnose. “Does this org structure solve a real coordination problem?” defers everything to the word “real.” “Is this team empowered to make decisions?” defers everything to the word “empowered.” The diagnostic vocabulary is drawn from the same self-referential library that produced the structures being diagnosed, and so the diagnosis can never achieve escape velocity from the library. It remains inside Solaristics, observing Solaristics, producing more Solaristics.

IV.

Deleuze and Guattari describe a mechanism they call the “miraculating machine,” and it is this mechanism, more than any other, that explains why management theory persists despite having lost contact with its object.

Production happens first. Flows connect: people coordinate, information moves, work gets done. Then a recording surface appears — a taxonomy, a framework, a methodology — that inscribes what happened, makes it legible, gives it names and categories. So far so good. The recording is useful. The taxonomy helps people talk about what they’re doing. But the recording surface has a structural tendency to fall back on production and claim to be its cause. The record stops documenting the flow and starts presenting itself as the origin of the flow. The taxonomy that described how teams coordinate begins to look like the reason teams coordinate. The framework that classified organisational structures begins to look like the design of organisational structures. The recording surface has miraculated: it has become an enchanted surface that claims to generate what it merely inscribed.

Conway’s Law is the purest case. Melvin Conway observed in 1967 that systems tend to resemble the communication structures of the organisations that produced them. This was an observation — a recording of something that happens. But Conway’s Law has undergone the miraculating flip. It is now presented not as an observation but as a design principle: “Therefore, design your communication structures to match your desired system architecture.” The recording surface has fallen back on production. The observation now claims to be the cause. And the moment it becomes a prescription, it is no longer falsifiable, because you have arranged the territory to match the map, and any correspondence between them is now guaranteed by fiat rather than discovered by investigation. Conway’s Law as observation was Solaristics at its best — careful description of what the ocean does. Conway’s Law as prescription is Solaristics at its worst — the library rewriting the ocean and calling it progress.

Tuckman’s stages perform the same operation. Bruce Tuckman observed that groups he studied appeared to move through phases. He recorded this observation, and the recording was published in 1965, and the recording entered the library, and the library distributed the recording into management training curricula worldwide, and now every team that forms is told it will storm and norm and perform, in that order, and the team’s experience of its own development is shaped by the taxonomy it was given, so that when conflict arises someone says “we’re just in the storming phase” and the taxonomy that was built to describe the process becomes the lens through which the process is experienced. The recording surface has miraculated. The team does not go through Tuckman’s stages because Tuckman discovered a natural law. The team goes through Tuckman’s stages because someone put the slide in the onboarding deck.

The Spotify Model is a more recent and more instructive case, because its miraculation happened fast enough to observe in real time. In 2012, Henrik Kniberg and Anders Ivarsson published a paper describing how Spotify organised its engineering teams at that particular moment. It was a recording — a description of what one company was doing. The recording entered the library. The library distributed it. Within five years, hundreds of companies were reorganising themselves into squads, tribes, chapters, and guilds — not because those structures emerged from their own organisational dynamics, but because the recording surface told them that these structures were the cause of Spotify’s success. The record had miraculated. And the irony — noted by multiple former Spotify employees — was that Spotify itself had already moved on. The formations the recording described no longer existed at the company that produced them. The ocean had changed. The library hadn’t noticed.

The two-pizza team is perhaps the most elegant Mimoid in the management canon. Jeff Bezos proposed that teams should be small enough to be fed by two pizzas. This was a heuristic — a rough guide, a rule of thumb. But the recording surface did its work. “Two-pizza team” entered the library, and the library transformed it from a heuristic into a principle, and companies began structuring their teams around the principle, and the principle generated its own secondary literature (What counts as a pizza? Are we talking New York slices or personal pan? What about teams of hungry people versus teams of people who just ate?), and the secondary literature generated more secondary literature, and the heuristic that was meant to point at something simple — keep teams small — became an object of Solaristic study in its own right, generating more library without generating more understanding.

V.

In Solaris, the question that haunts the station is whether contact between the scientists and the ocean is possible. The ocean produces formations that look like responses. The scientists produce interpretations that look like understanding. But neither side can confirm that anything has been transmitted. The scientists study the ocean. The ocean does something. The scientists interpret. The ocean does something else. The cycle continues indefinitely, each side producing formations in the presence of the other, and the formations resemble communication, and the resemblance is the cruelest part, because it is never quite enough to constitute proof and never quite little enough to justify giving up.

The relationship between management theory and organisations is the same relationship. Management theory studies organisations. Organisations do something. Management theory interprets. Organisations do something else. Occasionally the theory is applied — a framework is imported, a methodology is adopted — and the organisation changes, and the change looks like the theory was correct, and this is the Mimoid property at its most insidious: the fact that applying a framework causes changes that the framework predicted does not demonstrate that the framework understood the organisation. It demonstrates that the recording surface has been inscribed onto the territory. The map has been laid on top of the land, and now the land, where you can see it, matches the map, but this is not the same as the map being accurate. It is the map asserting itself.

The consultants know this, or they would know it if they read Lem, which they don’t, because they are too busy reading each other. They arrive with frameworks. They diagnose using frameworks. They prescribe using frameworks. And when the prescription fails — when the agile transformation does not transform, when the squads do not squad, when the matrix produces the exact paralysis that the matrix was supposed to prevent — the failure is attributed not to the framework but to the implementation. “The framework is sound. You didn’t execute it properly.” This is the Solarist’s defense against every negative result: the ocean is comprehensible in principle; we simply haven’t found the right classification yet. The library grows. The ocean is unchanged. The researchers go on reading.

There is a moment in Solaris where Kelvin considers the possibility that the ocean has been studying the humans all along, that the formations are not responses but experiments, that the scientists are the specimens and the ocean is the scientist. Lem does not confirm this. The possibility just hangs there, unresolable.

There is an equivalent possibility in management theory, and it is this: that organisations are not the object of study but the medium in which the study propagates. That the frameworks do not describe organisations but are produced by organisations — that the two-pizza team, the matrix, the squad, the OKR, the agile manifesto are not tools for understanding organisational life but are formations that organisational life produces, mimoids that rise from the surface and look like understanding without containing it, and that the consultants and theorists and authors who believe they are studying the ocean are themselves formations the ocean produced, and the library they are building is not a record of the ocean but another production of the ocean, and the distinction between observer and observed was never real, and the whole enterprise of management theory — the journals, the conferences, the bestsellers, the certifications — is a symmetriad of enormous scale, rising and collapsing and rising again, architecturally precise and internally consistent and utterly, magnificently, uncontactable.