Formality creeps in when you are nervous because distance feels safer than exposure. The more a message could go wrong, the more your writing drifts toward the register of a letter from a bank, and the drift starts before you notice you are doing it.
Nobody decides to type "I wanted to reach out regarding the below". Your fingers do that while your brain is busy rehearsing the reply you are dreading.
The reader usually notices, though rarely as a thought they could name. What lands is a small feeling that something is off.
What formality creep sounds like
Formality creep is the gap between how you normally write to someone and how you write to them when you are anxious. Same person, same request, two registers.
The calm version: "hey, can you look at the pricing doc before Thursday? there's one section I'm unsure about."
The nervous version: "Hi Sam, I hope this finds you well. I wanted to reach out regarding the pricing document. When you have a moment, it would be great if you could take a look and share any thoughts at your earliest convenience."
The second version contains no deadline anywhere in it. It also sounds like the opening of a conversation about your performance.
Your reader compares this message to your last one
Formality reads as a signal because it is relative. Nobody carries an absolute scale for professional language; they carry a memory of how you usually sound.
Go two notches above your own baseline and the reader starts looking for the reason. Are you angry? Is this being forwarded to someone? Did I do something?
When someone who normally opens with "morning" sends me "Dear Jo," I read the rest of that message with my shoulders up. The content is almost never bad. The register got there first and set the mood.
This is why the polite version can land worse than the blunt one. Formality withdraws warmth without explaining why, and readers fill that gap with the least flattering story available.
Nerves reach for formality because it works as armor
Formal language is protective, which is the honest reason it shows up under pressure. It puts a layer between you and the answer you are afraid of.
It buys three things, and none of them are real:
- If the answer is no, it lands on a form letter rather than on you.
- The words sound like the words of someone who is allowed to ask.
- The ask stays vague enough that you could later claim you were only checking in.
Every one of those protections works by making the request smaller and blurrier, which is exactly what a nervous message cannot afford. You armor the ask and then wonder why it gets ignored.
I get this worst when I write to someone I admire about the thing I built. First drafts of those messages read like a press release. Knowing the pattern has never once stopped me from doing it; it only shortens the gap between writing the stiff version and fixing it.
Where formality creeps in first
Formality shows up in a small set of predictable places, so you can check all of them in about ten seconds.
- The greeting climbs, from "hey" to "Hi Sam," to "Dear Sam,".
- Plain verbs swap for corporate ones, so ask becomes reach out and answer becomes advise.
- You start narrating your own message with lines like "I am writing to follow up".
- Passive constructions arrive and the actor disappears, as in "it was decided" and "the file has not been received".
- A run-up appears before the request, two or three lines of context nobody asked for.
- The sign-off inflates from thanks to Best regards, occasionally with your job title attached.
- Your contractions vanish. That one is the quietest and the most telling.
Any of these is harmless alone. Stacked in one message they read as someone putting on a costume, and the costume is more visible than the nerves it was meant to hide.
How to bring the register back down
The fastest fix is to open your last message to that person and match it, because your own baseline is the one register that cannot be read as a signal.
- Scroll up in the thread and reuse the greeting you used last time.
- Move the ask into the first two lines and delete whatever was sitting above it.
- Read the draft out loud, and cut anything you would never say to their face.
- Keep the manners in one place, usually a single line about the timing.
- Put the contractions back. They cost nothing and they carry most of the tone.
Something useful happens when you do this: the message gets shorter. The nervous draft and the skimmed draft are frequently the same draft, so lowering the register and raising the reply rate turn out to be one job instead of two.
Doing that edit while nervous is genuinely hard, because the nerves are the thing picking the words. That specific moment is what I built Unvent for. It rewrites the stiff draft in a plainer tone before the message goes, rather than after they reply.
When formal is the right call
Formality earns its place when the reader has no baseline for how you normally write.
An announcement forty people will open at forty different moments with none of your context in their heads, or a first message to a stranger who has never seen your usual voice. Nobody can tell a warm line from a curt one without something to compare it against, so in those messages you carry the meaning with structure and let the register go flat.
The test I use is one question. Does this person know how I sound on an ordinary Tuesday? If they do, write it the way you write.
There is a second half to all of this, and it is what you do when someone gets formal with you. The instinct is to mirror it. Mirroring locks you both into the stiff version for the rest of the thread, and then two people are writing letters to each other about a task that needed one line.
Break it instead. Answer the question in your normal voice, and if the shift did mean something, you will find that out far faster than you would by matching their sign-off.
Keep your normal voice under pressure
Unvent rewrites what you are typing, right there in the box, in the tone you pick, so the stiff draft never has to be the one you send.
Add Unvent to Chrome