The "just" habit and the words that shrink you

A minimizer is any word that makes your request smaller before the reader has looked at it: just, quick, a bit, sorry to bother you. It is apology tax, paid in advance. The reader takes the discount you offered and prices your ask accordingly.

The standard advice is one line long: delete every "just". I think that advice is wrong, and the rule that should replace it is about where a minimizer sits, not whether you are allowed to have one.

What a minimizer does to your ask

A minimizer tells the reader how much your request is worth, and the reader believes you.

Every request arrives with a price on it. The price is attention: how far up their list it goes, and whether it survives the trip from inbox to actual work.

You set the opening price in your first six words. "I just wanted to check whether maybe you had a second to look at this at some point" prices the thing at roughly zero. It then gets treated as roughly zero, and you go away thinking people ignore you.

Nobody does this deliberately. The minimizer is a flinch, and the flinch is honest: you can see that the other person has their own week, and you feel the cost of walking into it. The trouble is that the flinch attaches to the wrong noun. It lands on the thing you need instead of on the interruption.

Why deleting every "just" is bad advice

Stripping every softener out of your writing does not make you sound confident. It makes you sound like a robot with a clipboard, and people quietly stop enjoying the threads you are in.

Softeners do real work. They are the written version of what your face does when you approach someone who is clearly mid-something. Remove all of them and every message becomes a demand with no wrapper on it.

I would rather work with someone who writes "sorry, one thing before you disappear into the afternoon" than with someone who read a post about assertive writing and now sends bare imperatives at nine in the morning. The first person is being polite. The second is performing a personality.

The advice also lands on the wrong desks. It is aimed at people who apologize for existing, which is a genuine problem, and it gets adopted most eagerly by people who overshoot into coldness, which is a different genuine problem that nobody writes threads about.

Soften the interruption, never the ask

Put the minimizer on the imposition and keep it off the request. That is the whole rule.

Two things happen inside any ask. You take some of the reader's time, and you request a specific thing by a specific point. The first is an imposition, and acknowledging it is manners. The second is information, and information does not survive being made smaller.

Compare two versions of the same message. "Sorry to catch you mid-sprint, can you approve the invoice today?" The apology covers the timing. The ask keeps its edges: what, and when.

Now the leaked version. "Sorry to bother you, I just wanted to see if maybe you could take a look at the invoice at some point?" Same person, same invoice, no date, no request. The reader has been handed a mood instead of a task.

The test takes two seconds. Cover the first clause with your thumb. If what remains still says plainly what you want and when you want it, the softener was manners. If what remains is also hedged, the minimizer has leaked into the ask, and the message now reads as optional.

Impositions actually worth naming are narrower than most people think:

• You are interrupting focused work, or writing outside their hours.
• You are asking for a second favor while the first one is still open.
• You are late with your part, and the ask exists because of that.
• The request sits outside anything they signed up for.

Asking a colleague to do their job is not on that list. Neither is following up on something you already asked for.

The worst offenders, and what to write instead

Most minimizers can be deleted with nothing put back, because the sentence underneath them was already finished.

• "I just wanted to ask" becomes "I'm asking", and the sentence never misses the word.
• "We're a bit behind" becomes "We're two days behind". A bit is a number you decided not to say.
• "I think maybe we should" becomes "I think we should". One hedge is a position, two is a shrug.
• "If that's okay" at the end of a request hands back the decision you just made.
• "Whenever you get a chance" means never, in any week with pressure in it. If there is a date, name the date.
• "Sorry to bother you" stays when you truly interrupted something, and goes when you were doing your job.

Reread those replacements if they feel harsh on the page. They are not blunter than the originals. They are the same messages with the discount removed, and most of them are shorter, which the reader will also appreciate.

My own first drafts are full of the originals. I know the rule and I still type "just wanted to check" because the flinch is faster than the rule, and rereading only helps on the days I remember to reread. Catching it at the moment of sending is what changed things for me: taking the Direct rewrite in Unvent takes the discount off before anyone reads it.

The "quick" trap

Calling your own request quick is a promise you cannot keep, because the clock is on the reader's side of the screen.

"Quick question" means quick for me to type. Whether it is quick to answer depends on things you cannot see: whether they have the file open, whether they remember the decision from two months ago, whether answering commits them to something they will have to defend later.

I have sent a quick question and started a two-day thread. I have received "quick call?" and lost an afternoon.

There is a second cost, and it is the one people miss. Quick is a value label. Tell someone your request is small and you have licensed them to treat it as small, which in a full week means not at all. You cannot get speed and importance out of the same adjective.

So say the real size, or say nothing about size. "One question about the pricing copy, should be a single read" is a claim you can keep. "Quick" is a claim about somebody else's day, made by someone who is not having it.

Where your minimizers cluster

The people you hedge with are a map. Read your last twenty sent messages and mark the ones carrying a minimizer, then look at who is on the receiving end.

Mine are not spread evenly. There are people I send clean, plain requests to, and there are two or three whose threads collect every softener I own, and the difference has nothing to do with how busy any of them are. My wording follows my sense of standing, not my sense of grammar.

That pattern is worth sitting with, because it is information about the relationship rather than about your writing. Asking for help is where it shows up most, and that message has a shape that works better than armor does.

When a whole category of message needs armor before it can leave your outbox, the wording is not the broken part. You are negotiating something in advance, alone, in a sentence, with a person who has not been told a negotiation is happening.

Fix the wording anyway. It is the cheaper of the two jobs, and it holds while you work out what to do about the expensive one.