The apology you put in front of your question
A Tuesday-morning push for the apology that starts your requests: what it is buying, what it takes off the ask, and the three plain facts that let today's messages arrive at their real size.
It is Tuesday morning, and there is a message half-written in front of you.
The question is one line: the figure on the invoice from the fourteenth, and whether it holds.
The box in front of it starts with an apology. Sorry to bother you. Apologies if this has come up before.
Three lines of it, and the question waits behind them like something you are smuggling into the room.
By this evening you will have written a few more. The meeting you would like moved. The file somebody promised on Thursday. The two minutes you need from the person at the next desk.
What the apology is buying
The apology arrives before anything has gone wrong, and it arrives free. That is why it gets typed first.
It is insurance. The premium is three words, and the cover is the chance that the ask itself is too much.
Too much of their morning. Too much of their patience. Too much of the standing you hold with them.
So the sentence hedges, and the hedge prices the request before anybody has read it.
It works quietly enough that you can type it for years and hear good manners.
At the other end, the person opens the message and meets the apology first.
It answers a question they had yet to ask. It says the thing you were hoping to keep out of the message: this is a bother, and this is optional.
What it takes off the ask
The first cost is size.
A question and a favour cost very different amounts, and an apologised request arrives in the same coat as both.
Somebody with forty unread messages sorts them by what each one costs to start. "Sorry to bother you" makes a two-minute answer look expensive.
The second cost is a small bill handed to the person answering.
A message that opens with an apology invites the reply "of course, any time".
A question that needed one line now takes three. They are asked to reassure you on the way to answering you.
The third cost lands on your own week.
Twenty messages opening with sorry, just, quick, and Friday reads back as a series of impositions you were lucky to receive.
The next ask is harder to write, and the habit gets another turn at it.
Write the ask at its real size
Before you send anything today, put the question in the first line and leave the apology at the bottom of the page.
Then give the person the three facts the apology was standing in for.
How big it is. Two minutes, a paragraph, an hour on Thursday.
When it needs an answer, and what the day after that date looks like.
And what happens when the answer comes back the other way. The version you send anyway. The plan that goes ahead on Friday regardless.
Three plain facts do more for a request than an apology has ever done.
Quick one about the invoice from the fourteenth: can you confirm the figure before Thursday? Two minutes of your time, and after your standup suits me just as well.
The warmth sits at the end, where it reads as warmth rather than as a discount on the question.
Then keep the word for the days it belongs to. You were late. You sent Wednesday's file on Thursday. Somebody rebuilt a morning of work because of you.
That apology takes one sentence, the thing itself, and the fix in the second half.
I sent yesterday's file. The right one is attached, and you have your morning back.
Write three asks this way today.
Some rooms want the softer register: a first note to somebody senior, a client, a person whose week has been heavy.
There the softness arrives as their name and one line about their week, and the request still lands at the size it is.
A sorry that is genuinely owed keeps its full weight. That sentence is about something that happened, and it reads as strength when it arrives plainly.
The ask I send today, with the question in the first line: ___ What it costs the person answering, and by when: ___ The sorry I keep for something that is really mine: ___
The message is one line long, and the person reading it can answer in two minutes. Send it at that size this morning.
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.