Technobabble

Definition

Technobabble isn't the legitimate jargon of Hard SF: it's the narrative substitute when the author hasn't solved the problem the scene poses. Reversing the plasma flow polarity to save the ship at the last second isn't science — it's a Deus ex machina dressed in lexicon. Used sparingly, a technical term sets the world; in excess, vocabulary becomes a smoke screen hiding missing Internal coherence and preventing the reader from anticipating or understanding stakes.

What it's for

In SF revision, spotting technobabble distinguishes what keeps the genre promise (constraints, costs, failures) from what cheats. A technical briefing can be dense if every term points to a rule established earlier. A climax resolved by three never-planted neologisms betrays the reading contract. The goal isn't zero jargon — it's that every term pays something: tension, characterization, or future constraint.

Variants by genre

• Space opera: jargon accepted as color (Star Trek) if the scene doesn't depend on babble to resolve.
• Hard SF: real or extrapolated terms with traceable logic; the reader should reconstruct the causal chain.
• Cyberpunk / near-future: neologisms anchored in existing tech (AI, networks, bio) rather than invented in bursts.
• Humorous SF: self-parodic technobabble assumed — the reading contract shifts, the cheat must be visible.

Common pitfalls

• Resolving the plot with a term invented at the last moment: experienced SF readers sense the cheat.
• Inconsistent vocabulary across chapters (same tech, three different names with no in-world reason).
• Technical Infodumping that stops action: the character explains what the whole crew already knows.
• Opaque jargon without translation into gesture: the solution is named, not what it costs.
• Confusing credibility with length: ten real terms poorly chained beat one clear physical constraint.
• Technobabble to impress the non-expert reader while excluding the expert — double failure.

Examples

• Star Trek: The Next Generation — systemic technobabble as color, often criticized when it replaces dramaturgy.
• Liu Cixin — The Three-Body Problem: dense technical vocabulary but held causal chain (counter-model).
• Andy Weir — The Martian: problems named simply, solved in verifiable steps — little babble, strong credibility.

Writing tips

• Max 2 invented words per page: beyond, reader drops off. Below 1 per chapter, your universe lacks texture. Frame: fantasy/SF worldbuilding.
• Implicit-definition test: every technical term must be understood by context within 2 pages, no glossary needed. Otherwise rename.
• No "solves everything": a technical term that appears only at climax to save the day = disguised deus ex machina. Must be seeded in act 1 minimum.
• Level consistency: don't mix military, biological, quantum jargon in one scene without clear hierarchy. See system consistency checklist.
• Terminology bible: keep 1 sheet per term (root, spelling, pronunciation, 1st occurrence). Without it, you reinvent the wheel every 20 chapters.

Revision checklist

• Has every technical term in my climax been planted or explained in advance?
• Can the reader summarize what's happening without the jargon?
• Does the solution have a visible cost (time, energy, risk) in the scene?
• Have I confused scientific density with Infodumping?
• Does my text keep the Hard SF contract I implicitly promised the reader?