Jargon fails at cross-discipline interface boundaries

What it is

Jargon is an efficiency tool inside a single professional community: a dense term can replace a whole paragraph of explanation because the listener already holds the shared background needed to decode it. Jargon fails not because a term is "too hard," but when an interface serves multiple groups that do not share that background at the same time — a chart shared by clinician and patient, a ticket that travels across teams, an engineering dashboard shown to a business stakeholder. At these boundary-spanning interfaces, the same word is compressed code for one side and an empty string for the other.

Why it happens

Jargon's efficiency comes from a shared knowledge background that has already compressed away most of the implicit context, so the term only needs to carry the residual difference. For someone without that background, this compression doesn't just slow decoding down — it often fails outright. What's missing isn't patience, it's the entire background the term depends on, and no amount of extra screen text substitutes for that background. The real issue was never whether the term is well-chosen; it's whether one interface is being asked to serve groups with different backgrounds at all. Serving a single professional group, jargon is efficiency. The moment that same interface becomes a boundary node, the same words turn from efficiency into failure.

Where it stops holding

Within a fully homogeneous professional audience, jargon should not be stripped out — removing it slows experts down and adds explanatory noise they don't need; this is the flip side of expert users tolerating higher information density. Jargon failure occurs only at specific boundary nodes: every handoff screen where a ticket moves from engineering to support to customer, dashboards shared across teams, reporting views shown to managers outside the discipline. Deep, single-audience operational screens in the same system can keep their jargon untouched.

Applying it

• First mark the actual boundary nodes in the interface — screens whose content is seen by two groups with different professional backgrounds, or content that is handed off from one group to another. Only those need jargon treatment; deep single-audience screens are left alone.
• At a boundary node, add a translation layer for the term aimed at the audience without the background, instead of replacing the term outright with a plain-language substitute — the translation field serves the audience lacking context while the original term stays available for the audience that has it.
• Verification: have real users representing both sides of the boundary walk through the same node and paraphrase what they understood. A substantive divergence between the two paraphrases, or one side unable to state the referent at all, confirms the node genuinely needs translation; once the divergence disappears, stop adding more.

Related

• Same group: A11.05.1 The gap between users' words and the system's words · A11.05.3 Abbreviations need a nearby expansion point · A11.05.5 Domain experts tolerate higher information density
• Adjacent: A11.09.4 High-context and low-context preferences for information density
• Search terms: jargon · boundary object · cross-disciplinary interface