November 9, 2026 Jo Builds 5 min read

The fear of sounding stupid in writing at work

Hand-colored engraving of a Acraea butterfly, Drury 1837

The fear of sounding stupid does not make people write less. It makes them write more. Bigger words, a long run-up before the point, a caveat on every claim, background nobody asked for. The reader does not take any of that as intelligence. They take it as someone who is bracing.

It took me years to accept the obvious version of this. The plain draft was always the one that made me look competent, and the padding announced the exact thing I was using it to hide.

What the fear does to a message

Fear of sounding stupid shows up as four habits, and every one of them adds words.

Each move feels like insurance while you type it. It is not. Read the message back a day later and all four say the same thing about the writer.

The run-up is the expensive one. It puts your weakest material where the reader's attention is strongest, and it saves the point for the moment their eyes have already started sliding toward the next thing in the list.

Why big words read as less confident

Long words make a sentence sound borrowed, and borrowed sentences read as uncertain.

When you use a word you would never say out loud, the register of the writing stops matching the register of the person. Readers feel the seam even when they could not name it. "We should hold off" and "we should defer implementation" carry identical information. Only one of them sounds like a decision a human being made.

The colleagues I trust most in writing use short common words and take positions inside them. The ones I skim are the ones whose sentences could have come from anybody.

Early drafts of my own product copy were full of words I would never say in a room. I cut them one at a time. Every cut made the page easier to believe.

Plain writing is the harder skill, which is exactly why it reads as confidence. You cannot hide a half-finished thought inside a small word.

The question you did not ask

The most expensive thing this fear does is stop you asking the basic question.

A task arrives with a word in it you do not fully understand. Asking feels like an admission. So you guess, and you build the thing your guess implied, and two days later somebody asks you, mildly, why it came out like that.

Nobody loses standing for asking what "by end of week" means. People lose standing quietly, over months, for shipping the wrong thing with confidence.

Asking well is a writing problem. Show what you already worked out, name the exact gap, then say what you will do if nobody answers. "I read this as the mobile view only, so I'd start there. Say if that's wrong." A reader takes that as someone who has already begun, which is roughly the opposite of what you were afraid of. The full shape of a good request has its own rules, and none of them involve apologizing first.

The same message with the armor taken off

The plain version is the same message with the armor taken off, and it usually runs about half the length.

Here is the shape it fixes. "So I've been looking at the export bug, and I know there's a lot of history here that I probably don't have, and I might be missing something obvious, but from what I can tell it might possibly be related to how we're handling time zones, though I could easily be wrong about that."

The plain version: "The export bug looks like a time zone problem. I'm not certain yet. Want me to keep digging, or hand it over?"

Both versions admit the same amount of uncertainty. The second says it once, in the open, where the reader can do something about it. The first spreads it over four clauses and hands the reader the sorting.

I still catch the long version in my own drafts, usually in replies where I am half sure. What worked for me was moving the fix into the field instead of keeping it in my head: the Direct rewrite in Unvent drops the run-up and the stacked hedges, and the one honest caveat stays where it belongs.

When the fear is telling the truth

Sometimes the fear is accurate, and it is dishonest to pretend otherwise.

There are teams where a plain question does get filed away and used against you later. If you are in one of those, write carefully in the channels that get quoted, and ask the real questions on a call, where nothing is stored. That is a survival tactic rather than a writing style, and it is worth knowing which one you are running.

The way to tell them apart is to check who you do it with. If the caveats show up in everything you write, the habit came with you and it will follow you to the next job. If they only show up around two specific people, that is not a writing problem. It is information about those two people, and no amount of editing fixes it.

One honest caveat, no hedge pile

Unvent rewrites the draft in the box you are already typing in, in the tone you pick, so what leaves your hands is the short version with the point at the top of it.

Add Unvent to Chrome
u

Jo Builds makes Unvent, a Chrome extension that rewrites whatever you are typing, in place, in the tone you pick. More on the about page.