---
title: "Standardization"
description: "Participants settle on one way of doing a thing — a unit, a file layout, a wire protocol, a track width — because each of them saves effort by matching the…"
canonical: https://moa.giglabo.com/strategies/standardization/
locale: en
---

# Standardization

> Markdown twin of https://moa.giglabo.com/strategies/standardization/ — the same content as the HTML page, a fraction of the bytes.
> Every page of this site has one: append `.md` to any URL, or `index.md` to a directory URL.
> Site structure and the full page list for agents: https://moa.giglabo.com/llms.txt

Category: Collaboration · Role: Holds · Depth: 4

Gist: emergent alignment that reduces friction

## Moats

- [#29 Standard and format](https://moa.giglabo.com/moats/29/) (direct, depth 4 · Mine) — Once the industry keeps its work in your form, every rival must be compatible with you and you decide what compatible means: that control of the reference is the Standard and format moat.
- [#5 Switching costs](https://moa.giglabo.com/moats/5/) (direct, depth 2 · Excavator) — Each adopter accumulates archives, configuration and trained staff in the standard form, so leaving a compliant tool for a non-compliant one costs a migration — Switching costs at the level of one customer.

## Summary

Participants settle on one way of doing a thing — a unit, a file layout, a wire protocol, a track width — because each of them saves effort by matching the rest. Once the settlement has happened, whoever defines the reference holds the industry's data. That is a mine on the ruler, and the deepest thing in this category.

## How it works

The mechanism is a convergence with a cost of leaving. Each participant adopts the common form because compatibility with everyone else is worth more than any private improvement; after enough of them have, the choice stops being a choice. Files, archives, contracts, trained staff and tooling all assume the form. The advantage is not that the form is best — it rarely is — but that changing it requires everyone to move at once, and nobody can organise that.

Whoever controls the reference — the specification, the canonical implementation, the compatibility test — sets the terms on which any rival exists. The rival must read and write your form perfectly, and you decide what perfect means this year. Underneath that sits a second, shallower lock: every user who adopted the form has archives and habits in it, so leaving a compatible tool for an incompatible one costs a migration. The standard is the industry-wide version; switching costs are the per-customer version of the same weight.

## Why it holds — or only takes

This holds, and in two layers. Standard and format, depth 4 and a mine, is the direct result: the industry stores and exchanges its work in your form, and compatibility with you is what a rival must buy. Switching costs, depth 2, are the same lock at the scale of one customer: archives, configuration and trained people in the standard form. The first is out of a solo builder's reach and resists AI; the second is reachable by one person and under attack, because agents now migrate data between forms cheaply. The depth here belongs to the reference, not to whoever merely complies with it.

## Do you have it

- You already have this if rivals advertise compatibility with your format by name.
- Other people's tools ship an importer for your files before you have asked.
- Job postings in your industry list your format as a required skill.
- A customer's archive is in your form, and their migration estimate has a line for conversion.

## How to dig it

- Publish the specification and a conformance test; a form nobody can verify against does not become a standard.
- Give the format away and keep the canonical implementation, so adoption spreads while the reference stays yours.
- Get the archive, not the app, into your form: files people keep for years outlast any tool.
- Seed the tooling: libraries, converters, examples in every language the industry uses.

## How it erodes

- Reverse-engineering for interoperability releases the hostages; after that the contest is about the product again.
- A coalition of the largest users publishes an open replacement and a regulator makes it mandatory.
- A change of medium — files to streams, desktop to cloud — makes the old form irrelevant rather than beaten.
- AI converts between forms at almost no cost, and the per-customer switching lock thins first.

## Solo, without capital

A single person does not set an industry's standard; that needs the weight of the largest players or a regulator, and years. What you can do this quarter is ride one: implement the standard first and best in a niche, ship the converter everyone lacks, or define a small open format inside a community you already run. Switching costs you can dig alone — configuration, history, habit — but plan for AI migration to shorten them.

What the matrix says of its moats:

- [#29 Standard and format](https://moa.giglabo.com/moats/29/) — Solo: ✗ no · Capital: ● high · AI: ↑ AI-resistant · Rent: ~ partly
- [#5 Switching costs](https://moa.giglabo.com/moats/5/) — Solo: ✓ solo-reachable · Capital: ○ low · AI: ↓ under attack · Rent: ✗ not for sale

## In nature, in business

Nature: —

Business: language, railway gauge, metric system

- **Autodesk** — Decades of engineering drawings sit in DWG, so every CAD rival has to read and write that format and Autodesk controls what correct reading means.
- **Adobe** — Adobe handed PDF to ISO as an open standard while keeping Acrobat as the reference implementation, and the format became the way documents are exchanged.
- **ISO shipping container** — Malcom McLean's container dimensions became the ISO standard, so every port, crane and ship since has been built to the same box.

## Combines with

- [Union](https://moa.giglabo.com/strategies/union/) — A union is the deliberate route to the same place: rivals sign the form into a charter instead of drifting to it.
- [Omnipresence](https://moa.giglabo.com/strategies/omnipresence/) — A form accepted by default everywhere is what a standard looks like from outside.
- [Composability](https://moa.giglabo.com/strategies/composability/) — Components that assemble in many configurations need a shared interface, and the interface is the standard.
- [Transparency](https://moa.giglabo.com/strategies/transparency/) — Publishing the spec is what turns a private form into one others adopt.

[This strategy on the map](https://moa.giglabo.com/strategies/?view=lanes&hl=standardization)
[Map this combination](https://moa.giglabo.com/strategies/?view=lanes&hl=standardization,union,omnipresence,composability,transparency)

## Fights with

- [Divergence](https://moa.giglabo.com/strategies/divergence/) — Differentiating from the norm and becoming the norm are opposite bets; a standard wins by being what everyone else already does.
- [Secrecy](https://moa.giglabo.com/strategies/secrecy/) — A form nobody can read does not spread; secrecy protects the implementation but starves the standard.

[Map this tension](https://moa.giglabo.com/strategies/?view=lanes&hl=standardization,divergence,secrecy)

## Source

Strategy taxonomy © kepano (Steph Ango), paraphrased with attribution. Role and moat mapping © Moat Atlas. https://stephango.com/

## Related

- HTML version of this page: https://moa.giglabo.com/strategies/standardization/
- Русский: https://moa.giglabo.com/ru/strategies/standardization/
- Previous: Centralization — https://moa.giglabo.com/strategies/centralization/
- Next: Symbiosis — https://moa.giglabo.com/strategies/symbiosis/
- Atlas: https://moa.giglabo.com/
- Catalogue: https://moa.giglabo.com/moats/
- Calculator: https://moa.giglabo.com/calculator/
- Strategies: https://moa.giglabo.com/strategies/
- Site map for agents: https://moa.giglabo.com/llms.txt