Platform versus institution

The words «platform» and «institution» are often used as synonyms: both are something large that shared life rests on. But there is a fundamental difference between them, and that difference determines a great deal about how the present is arranged.

01An institution is obligated, a platform provides

An institution — a school, a court, a postal service, a university — carries obligations. It exists for a particular purpose, it has norms, it can be held to account. A platform is built differently: it provides the possibility of connection and takes its cut. It is not obligated — it optimises. When a platform says «we merely connect people», it is precisely shedding institutional responsibility while keeping infrastructural power.

An institution carries obligations. A platform optimises. And in that shift the addressee of responsibility disappears.

02What it means to «become private»

When the infrastructure of shared life — of communication, commerce, work, knowledge — passes to platforms, it becomes private not only in ownership but in logic. The rules are now set not by a public procedure but by a product decision. They can be changed with an update, without explanation or debate. What used to be a matter of norm and dispute becomes a matter of configuration.

This is the quiet revolution of recent decades: vast areas of common life have moved into environments where there is neither a citizen nor a procedure, only a user and an interface.

03Efficiency as an argument

A platform almost always beats an institution on convenience. It is faster, cheaper, more pleasant to use. This is not an illusion — it is a real advantage, and that is exactly why the shift feels natural. But convenience does not measure everything. An institution is slow partly because it is accountable: procedure, appeal, norm — these are the very «brakes» a platform proudly removes.

The question is not what is better in general, but what we lose along with the slowness. Often we trade accountability for speed without noticing the bargain.

04The engineer's view

Here engineering and theory meet literally. Whoever builds platform tooling — and I build it every day — makes decisions of institutional scale in the guise of product ones. Who has access. What is logged. Which behaviour the interface rewards. These are not «settings»; they are the constitution of an environment.

I am not calling for a return to institutions and a rejection of platforms — that is impossible and unnecessary. I am calling for designing with an awareness of scale. If a platform takes on the function of an institution, it is worth asking whether it takes on its responsibility too — and if not, who bears it. That question is almost never raised in a product framing. I think it should be.