You’ve read a manual before. You probably skimmed it, got confused, and figured it out by trial and error. No big deal — until the manual you’re reading is for maintaining a jet engine, and the ambiguity between “tighten” and “secure” costs 300 lives.
This isn’t hypothetical. Ambiguous technical documentation has contributed to real disasters. And the fix exists. It’s been around since 1986. It’s called Simplified Technical English, and most people have never heard of it.
The most dangerous sentence in any technical document is the one that can be read two ways.
STE was born in the aerospace industry — specifically, out of the European Association of Aerospace Industries. The problem was simple and brutal: aircraft maintenance manuals were being written in English, then translated into dozens of languages, then interpreted by technicians around the world. Each translation introduced drift. Each ambiguous word introduced risk. Something had to give.
So they built a controlled language. STE restricts vocabulary to roughly 900 approved words. It limits sentence structure. It bans synonyms — if “make” is the approved verb, you don’t use “manufacture,” “produce,” or “create.” One word, one meaning. Every time.
Now here’s where most people get it wrong. They look at STE and think: “Oh, it’s about making documentation easier to read.”
No. It’s about making documentation impossible to misread.
Readability is a preference. Unambiguity is a liability shield.
Think about what happens when a global manufacturer ships a product without STE. They write the manual in standard English — rich, nuanced, full of synonyms and idioms. Then they send it to translation teams in 40 countries. Each team interprets phrases differently. Each language has words that don’t map cleanly. The German translator picks one meaning; the Japanese translator picks another. Now you have 40 versions of the truth, and none of them are exactly what the original engineer meant.
The cost of this chaos is invisible until it isn’t. A misassembled component fails in the field. A warranty claim turns into a lawsuit. A recall wipes out a quarter’s profit. And nobody traces it back to the manual that said “ensure proper alignment” instead of “align the marks on the housing.”
STE kills this problem at the source. When you constrain the language, you constrain the interpretation. There’s no room for creative reading because there’s no room for creative writing. The constraint IS the feature.
Every word you remove from a manual removes a way to get it wrong.
Aviation adopted STE because the stakes are existential. But the same logic applies to manufacturing, medical devices, industrial software, pharmaceutical equipment — anywhere a misunderstood instruction can cause real damage. If you work in any of these spaces, your documentation is either a safety system or a liability. There’s no middle ground.
The resistance to STE is predictable. Writers feel constricted by it. Engineers find it simplistic. Managers don’t want to pay for the training and implementation. It feels like dumbing things down.
But here’s the economic reality: STE reduces translation costs by up to 40% because controlled language is faster and cheaper to translate — and in many cases, machine translation becomes viable where it wasn’t before. It cuts documentation maintenance overhead because there’s a single source of truth. It reduces support calls because users actually understand the instructions. And it creates a paper trail that holds up in court: you can demonstrate that your documentation met an international standard designed to prevent exactly the kind of misinterpretation that caused the incident.
The companies that treat documentation as a cost center are the ones that pay for it in settlements.
There’s a deeper lesson here that goes beyond technical writing. We live in an era of information overload, where everyone is trying to say more — more features, more nuance, more caveats, more CYA language. STE represents the opposite philosophy: say less, but make every word load-bearing.
The best documentation doesn’t impress you with its sophistication. It disappears. You follow the steps, the thing works, and you never think about the manual again. That invisibility is the point. It means the language did its job — and nothing was lost in translation.
If you write, translate, or manage technical content, ask yourself one question: could someone in another country, speaking another language, reading a translated version of your document, perform a safety-critical task correctly on the first try?
If the answer isn’t an immediate yes, you don’t have a documentation problem. You have a risk problem.
Clarity isn’t kindness. It’s engineering. And in the industries where it matters most, it’s the difference between a routine procedure and a headline.
FAQ
Q: Isn't STE just dumbing down technical content?
A: No — it's weaponizing clarity. Dumbing down means losing information. STE means removing every word that could be misinterpreted while keeping 100% of the technical precision. The constraint forces you to be more accurate, not less.
Q: Is STE only relevant to aviation and aerospace?
A: No. Any industry where documentation is translated, used across borders, or involved in safety-critical procedures benefits. Manufacturing, medical devices, pharmaceuticals, industrial software — anywhere a misunderstood instruction costs money or lives.
Q: What about open standards? Is there a free alternative to ASD-STE100?
A: Here's the dirty secret: STE is a proprietary standard controlled by ASD, and it costs money. There's no comprehensive Creative Commons equivalent. Plain English guidelines exist but lack the rigor — approved word lists, grammar rules, and validation tools — that makes STE actually enforceable. The absence of an open standard is arguably the biggest barrier to wider adoption.