An exploration of organisations, teams, communities, and research fields as knowledge-processing systems rather than administrative structures -- not management theory, but cognitive science applied at a scale larger than one mind. The central question is the organisational version of a question this site's other series ask about individual and artificial minds: how do groups know things that no individual member fully knows, and what does it cost them to remember, forget, and adapt as a collective rather than as a crowd of separately competent people? The series moves from the basic mechanics of collective knowing, through how that knowledge persists and decays over time, to how trust, delegation, and duration change once a team is temporary, agentic, or spread across an entire discipline rather than a stable group.
A ship's navigation team can fix the vessel's position to within a few hundred metres, continuously, in poor visibility, without any single person on the bridge holding the calculation in their head. One officer reads a…
A new tailoring apprentice doesn't start by cutting cloth. They start by sweeping the floor, fetching thread, and watching. Then they're given buttonholes — a real, useful, low-stakes piece of a real garment — long…
Two developers who've shipped three projects together can fix a production incident over a two-word exchange — "cache again?", "on it" — that would mean nothing to a new hire listening in. The new hire isn't missing…
Every team has a version of the same story. A system has one person who really understands it — not the person listed as the maintainer in the documentation, the person everyone actually asks when something breaks in a…
A finance team still runs a manual reconciliation step every month that exists because a specific vendor's invoices, years ago, occasionally double-billed. The vendor relationship ended three years ago. The step is…
A company can send every employee on a training course every year, publish a glossy learning-and-development report, and still make the same strategic mistake every three years on schedule, each time with the air of a…
A manager who hands a hiring decision to a trusted deputy and a manager who writes a fixed scoring rule for a hiring algorithm have both stopped making the decision personally. Only one of them has delegated it.…
An emergency response team assembled from strangers at the scene of a disaster has no shared history, no time to build one, and often no idea who else is on the team until they're standing next to them. It still has to…
This cluster opened by asking whether an organisation can know something no individual member knows , and answered yes, in at least the distributed-processing and emergent-coordination senses — a ship's position fix, a…
For decades, researchers studying a phenomenon can share a background assumption so thoroughly that it stops being treated as an assumption at all — it simply becomes part of how the question gets asked, invisible in…
A database, a knowledge graph, and a large language model each answer a simple question — where is the knowledge, and how is it found again — in genuinely different ways. An organisation turns out to answer it in a…
A new hire with a question spends twenty minutes searching a wiki, finds three contradictory pages, and gives up. An experienced colleague with the same question sends one message to one person and has an answer in five…
An organisational chart is routinely wrong about who actually makes a given decision, who actually gets asked first, and which reporting line people actually use when something urgent happens. It remains, despite being…
A new hire asks why a particular approval step exists, and a colleague who's been there eight years gives a confident, detailed, entirely plausible answer involving a vendor dispute from before either of them joined.…
An earlier page in this cluster opened with a finance team still running a monthly reconciliation step built for a vendor dispute that ended three years ago — a step that costs real effort and protects against nothing…
A product-focused question asks whether the organisation produced the correct output this time. A process-focused question asks something harder and more durable: does the organisation have a dependable, revisable way…
Everything this part of the cluster has argued so far can be granted without answering the question this page actually asks. An organisation can store and retrieve knowledge, maintain a self-model that actively shapes…
"The organisation has decided," "we've always done it this way," "our position is" — each of these compresses a messier reality into a single speaking voice, and the compression is rarely neutral. What "the organisation…