Rules That Let Things Work Together

A box reaches a warehouse with everything in it that the customer ordered. The goods are sound. The label is wrong.

The warehouse uses a scanner to move deliveries into its records. This label puts the information in a different order and uses a code the system does not recognize. Someone must stop, look up the order and enter the details by hand. The next box arrives. A queue begins.

It is easy to understand why the warehouse wants a standard label. Everyone gains when a routine handover works. The supplier can send goods without explaining each package. Staff can spend less time solving the same problem. The customer has a better chance of receiving the right thing.

Then ask who chose the standard, how much it costs to meet, and whether a small supplier had a chance to comment before the rule became a condition of doing business.

The answers may strengthen the case for the rule. They may also reveal an avoidable barrier. We need to be able to hold the value of coordination and the cost of entry in view at the same time.

The freedom created by agreement

We often speak of rules as limits. Standards show how rules can create possibilities.

Imagine trying to buy a replacement part when every maker measures it differently and no one describes the measurements clearly. You could still arrange a custom part. You would need more time, more expertise and probably a closer relationship with a particular supplier. A shared specification can make the transaction ordinary.

That ordinariness is a form of freedom. You can buy from someone you have never met because the two of you can refer to the same description. You can ask whether the product meets it. Another supplier can try to make a compatible part. A repairer can understand what belongs in the space.

Standards do not guarantee that any of those things will happen. Prices, rights, safety and production skill still matter. But they can remove the need to negotiate every basic detail from the beginning.

The Internet Engineering Task Force states this purpose clearly in RFC 3935. Its 2004 mission document treats compatibility as a central benefit of technical standards and commits to open participation and engineering judgment informed by working implementations. It also acknowledges that technical choices carry values. These are declared principles, not evidence that every affected person has equal influence or that every resulting system serves everyone well.¹

The admission about values is important. We can stop pretending that a technical discussion takes place outside human purposes. A design can favor one kind of connection, control or change over another. Explaining those choices does not weaken the engineering. It makes the engineering easier to judge.

A bridge must stand up. The decision about where to build it also matters. In the same way, a shared technical rule must work, and we still need to ask whose work it makes possible.

The cost of joining

Return to the warehouse. Suppose the new label standard requires software that a large supplier already uses. A smaller supplier must buy it, learn it and change its records.

The requirement may still be justified. Perhaps the old system created costly errors. Perhaps a common format makes it easier for new suppliers to compete once they have joined. The small supplier’s inconvenience does not automatically outweigh everyone’s need for reliable handling.

But the warehouse should investigate whether the same purpose could be met with a simpler export, a free template or a transition period. A requirement can be technically reasonable and badly introduced.

This is where power enters through details that can seem too dull for public attention. The deadline determines who has time to adapt. The test procedure determines who can prove compliance. A licensing condition may affect who can build a compatible tool. A fee may be trivial for one organization and decisive for another.

None of this requires a conspiracy. A team can design around the resources it knows and fail to notice what others lack. The result still deserves correction.

When a standard becomes a doorway to a market or service, its entry costs are part of its public importance. We should ask for evidence about those costs, including the work of small participants. A consultation dominated by those with staff to attend every meeting may miss exactly the problems a consultation was meant to find.

The answer is not to treat every objection as a veto. A supplier may prefer a weaker standard because compliance is expensive, even when the protection is necessary. We need an argument about purpose and feasible alternatives. A cost should be visible before it is accepted or rejected.

Compatibility for whom?

A system can connect neatly to other systems and still be difficult for a person to use.

Consider a booking website that exchanges information correctly with the provider’s calendar. From one technical perspective it works. Now give it to a person who uses a keyboard rather than a mouse. If the date selector cannot be reached or operated, the successful connection between computers does not complete the booking.

Accessibility asks us to widen the test. Who can perceive the information, operate the controls and understand what is happening? The user is part of the working system.

The World Wide Web Consortium’s WCAG 2.2 Recommendation, in its December 2024 version, sets testable accessibility criteria. It addresses a wide range of needs while explicitly recognizing that it cannot address every need. A standard can therefore provide a shared baseline without making direct testing with affected people unnecessary.²

We should be cautious about the comfort of a badge. Saying that a service follows a standard should invite a check of what was tested, which version was used and what the claim covers. It should not end the conversation with someone who cannot complete an essential task.

This is a practical distinction. A test may assess a component in isolation. The user has to complete a whole journey. If the website works but the required confirmation arrives in an inaccessible format, the service still needs repair. If a human alternative exists but no one answers, listing the phone number has not solved the problem.

Standards are most valuable when they help people discover and fix failures. They become less valuable when compliance language is used to dismiss the evidence of a failure.

Keeping old connections alive

Changing a shared rule creates a second problem: people have already built around the old one.

The warehouse may want a better label. Suppliers may have stocks of printed packaging and systems tied to the earlier format. An abrupt change can waste that work. Keeping the old format forever can preserve errors or block improvement.

A responsible change has to deal with the transition.

There may be a period when both formats are accepted. There may be a conversion tool. There may be a date after which the old version is no longer supported, explained far enough ahead for people to plan. The right approach depends on the risk and the cost. A serious safety defect can justify speed that an ordinary improvement does not.

What should not happen is an invisible transfer of all transition costs to the people with the least room to absorb them.

Suppose a public body buys a new records system. The supplier proposes a convenient format that only its own software handles well. That might meet today’s needs, but the body should ask how it could move its records later, who would help and what the move would cost. A decision about format can become a decision about future bargaining power.

Specialized tools can have real advantages. The point is to include the cost of leaving and the possibility of future connection in the decision made at the start.

A cheap purchase can become expensive if it closes off later choices. An open format can also be poorly documented or badly implemented. The label alone does not settle the comparison. Ask someone to demonstrate the transfer with realistic records before trusting a promise about it.

The work behind an open door

An open meeting is better than a closed meeting when affected people need a voice. It does not follow that everyone can use the opening equally.

Picture a committee considering a technical rule. The documents are public. The discussion is in a language familiar to some participants and difficult for others. Meetings take place during working hours in one part of the world. A large organization sends someone whose job includes following every revision. An independent repairer reads the papers after closing the shop.

Both may formally participate. Their practical capacity differs.

A right to speak is stronger when people also have access to the material, time to understand it and a fair chance to have their reasons considered. Technical knowledge matters; removing the need for it would not improve a technical standard. The question is how an institution can learn from people who have relevant experience but lack a permanent seat in the room.

It could publish clear explanations of consequential choices alongside the technical text. It could seek tests from smaller participants. It could make an unresolved objection visible rather than bury it in a long discussion. It could support participation where the value of that participation exceeds what an individual can afford to provide.

These are proposals, and they have costs. Someone must organize the work and decide whose contribution is useful. A process can become so slow that the problem it addresses moves on without it. We should measure that risk too.

The aim is a process that learns enough to make a sound decision, records its reasons and remains able to correct a mistake. Endless consultation is not accountability if nobody can tell when or how a decision will be made.

The standard and the claim about it

There are at least three questions to ask when someone invokes a standard.

First, what does the document actually require? A title can sound broader than the tests inside it. A standard for one part of a product may say little about another part that matters to you.

Second, how was compliance assessed? A supplier’s own statement, an independent test and a continuing inspection are different kinds of evidence. The appropriate check depends on the risk. We should understand the claim before using it as reassurance.

Third, what happens after a failure is discovered? A person may need a correction now, even if the formal revision of the standard will take longer. There should be a way to report the problem and a responsible party able to act on it.

These questions do not require every buyer to become a testing laboratory. They help us see what institutions should make legible. A clear claim lets a consumer group, purchaser, regulator or specialist inspect it on behalf of others. An ambiguous claim spreads reassurance without making responsibility easier to locate.

In some settings a standard is taken up by law, regulation or a contract. In others it is a voluntary reference. We have to inspect the actual jurisdiction and instrument before claiming a legal duty. The existence of a document on the web does not settle what a particular organization is legally required to do.

That boundary protects the argument from becoming careless. We can recommend a better practice without pretending it is already mandatory everywhere.

A shared rule should remain a shared resource

By the end of the day, the warehouse has a choice. It can treat the bad label as one supplier’s failure and carry on. Or it can discover whether the standard is clear, the instructions are accessible and the test can be completed without buying unnecessary extras.

Perhaps the supplier did ignore a reasonable requirement. Perhaps the instructions contradicted the sample. Perhaps a small change would prevent the problem for everyone. The investigation should be allowed to reach any of those conclusions.

Good coordination depends on people being able to rely on a rule. It also depends on people being able to improve it. If every participant must invent a private workaround, the promise of a shared standard is starting to fail.

I want more of the freedom that common rules can create: the freedom to repair, connect, compare and enter a market without a special relationship with whoever is already powerful. That requires standards whose purposes are clear and whose revision processes can hear more than the best-funded voices.

The label on the box may look like a minor matter. Behind it is a decision about whether people can work together on fair terms. There is nothing minor about that.

Sources and limits