The department that vanished

A week into the job, Britain’s new prime minister broke up the department that ran government technology and split its work three ways. No single minister is in charge of it now. The people who modernise the state’s computers were moved to their third home in two years.

On the surface this is office politics - boxes on an org chart, redrawn. But the boxes are not decoration. Who sits next to whom, who shares a boss, who has to ask to talk to another team: those lines decide a lot. Months in advance, they set what the resulting systems will and won’t be able to do. The reshuffle didn’t just move people. It reshaped the machine they will build.

A rule from 1968

A programmer named Melvin Conway noticed something in the 1960s that has held up for sixty years. Any group that designs a system, he wrote, produces a design that copies the group’s own communication structure. Software ends up shaped like the organisation that made it.

The classic example: a company puts four teams on a compiler, and it ships a compiler with four parts. Not because four is the right number - because there were four teams. Two pieces of software join cleanly only when the two teams building them talk easily. Where two teams barely speak, the software they build meets at a clumsy seam. The wiring inside the organisation becomes the wiring inside the product.

Why government tech never joins up

This is why filling in a government form feels the way it does. You type your address for the tax office, then again for the health service, then again for the licensing agency. Each one is a separate department, with its own budget, its own database, its own contract with its own supplier. Nobody built the bridge between them, because no one team owned both sides - and the two teams answered to different bosses who rarely met.

So the citizen becomes the bridge. You are the integration layer that nobody funded, carrying your own data by hand from one silo to the next. The fragmentation isn’t a bug someone forgot to fix. It is the org chart, faithfully rendered in software.

Seen this way, splitting the one coordinating body across three departments is not a small tidying-up. That body existed to fight the fragmentation - to force the silos to share a standard. Scatter it, and you remove the one place that was arguing for the bridge.

The seam you can see is the meeting you can’t

Once you know the pattern, you start reading it off the outside of things. A merged company ships an app with two login screens and two billing systems that don’t quite agree. It is really two companies, and the code met at the same seam the two staff canteens did. A product where one feature hands off awkwardly to the next usually has two teams behind it who don’t share a manager.

The seam you can feel as a user is a meeting that never happened, or happened badly, inside the building. The outside of a product is a fairly honest map of the conversations that made it. You can often guess an organisation’s private wiring without ever seeing its org chart - just by using what it sells.

Who drew the boxes

Here is the part that hides in plain sight. An org chart looks like a neutral administrative fact - this is simply how the department is arranged. But someone chose that arrangement. And in choosing it, they made a technical decision disguised as a management one. They decided which systems will be able to talk and which won’t, before a single line of code is written.

That choice can serve the person who makes it and still shape everyone downstream. Splitting a department can buy clearer lines of accountability, or political calm, or a tidier Cabinet. Those are real gains for the people drawing the boxes. The citizen re-typing their address is living in the same decision, from the other side. Both things are true at once. The point isn’t that someone did wrong. It’s that a choice which looks like plain administration is quietly setting the shape of the tools millions of people will use.

We are the integration layer

It is tempting to read all this as a lesson about other people’s bad management. It isn’t, quite. The pattern reaches the reader directly. Every time you re-enter the same detail on a new form, you are standing in the gap between two teams who never had to talk. You are the human glue holding together things that were built to be separate.

And none of us is above it. Anyone who has built anything with other people has shipped something shaped like their meetings. Think of the report split by who owned which section, or the kitchen job that shows exactly where two trades didn’t coordinate. We make things in the shape of our conversations without noticing we are doing it.

So the shape of a thing is a map of who talked to whom. The seams in the software, the handoffs that grind, the form that asks twice - they are the conversations that did and didn’t happen, made visible. No one drawing the boxes can see the whole map from their seat, and neither can anyone using what gets built. That is worth holding loosely the next time something feels needlessly broken. You may be looking at a wall between two rooms, not a mistake by one person in one of them.