Emails that finish work instead of creating it

Every email you send either closes a loop or opens one. Most people send openers by accident. You meant to pass along some information, and what landed was a small unpaid job: work out what this means, decide whether it needs a reply, remember to come back to it.

The test is one question. When the reader finishes your message, do they have to hold something in their head? If yes, you opened a loop. If no, you closed one.

Sending feels like output. A lot of the time it is redistribution.

The shapes that create work

Four email shapes create work almost every time, and all four look harmless while you are typing them.

• The FYI with an ask hiding inside it, where the reader cannot tell whether they are supposed to do something.
• The question stack, where five questions arrive in one paragraph and get answered zero times.
• The "thoughts?" that gives the reader nothing to have thoughts about.
• The forward with no framing, where the whole message is a fifty-line thread and the words "see below".

I will defend the strong version of this. "Thoughts?" is the laziest word in professional email. It looks collaborative and open. What it does is hand over the expensive half of the job, which is forming a position, while keeping the cheap half, which is reacting to somebody else's.

When I get a "thoughts?" I have to rebuild the situation from memory, invent the options nobody listed, weigh them, and then guess which part you actually wanted me to comment on. When I get "I'm going with option B unless you hate it", I read it in four seconds and answer in one word. The second message respects me more, even though it sounds pushier.

The FYI is subtler and does more damage. Plenty of the FYIs I have received had an ask buried in them, unspoken, usually urgent. The reader has to run a guess: heads up, or my problem now? Guessing costs more than reading, and when the guess goes wrong the sender gets to be annoyed about it, which is the part that makes the FYI quietly unfair.

The unframed forward is the same move done faster. Nobody wants to read your thread. One line above it saying what you want turns a pile into a request.

The shapes that finish work

Emails that finish work leave the reader with nothing to decide except whether to object.

The strongest shape is the decision with an opt-out attached. You say what will happen and by when, and you make silence a valid answer that still produces the right outcome.

Instead of: "Do you think we should push the launch back a week?"

Try: "I'm pushing the launch back a week so QA gets a full run. Tell me by Thursday if that breaks something on your side, otherwise I'll update the calendar."

The second one can be answered by doing nothing, which is close to the highest form of respect available in a busy week. Written fast, though, it reads colder than you meant, and people answer tone before they answer content. That is a lot of what I built Unvent for: type the decisive version straight into the reply box, then send the warm one that keeps every decision intact.

The second shape is the answer with the next step already attached. If someone asks you a question and you send back only the answer, you often open a loop without noticing, because the answer implies an action nobody has claimed.

"Yes, the invoice was rejected." opens a loop. "Yes, the invoice was rejected, I resubmitted it this morning with the PO number, and it should clear by Friday." closes one.

The third shape carries the artifact instead of promising it. "I'll send the draft later today" creates two jobs: yours to remember, theirs to wait. Send the rough version now with one line admitting it is rough. A messy thing in hand beats a clean thing in the future, most of the time.

Small habits that close loops:

• Open with the decision, then the reasoning that got you there.
• Name the owner of anything you are not doing yourself, a person, not a team.
• Give a date instead of "soon", even a loose one.
• Write "no reply needed" and mean it, so the times you do want a reply register.

None of this is about being brief. A long message can close a loop and a two-line message can open three. Length is not the variable. Residue is.

Some emails should open work, and that is fine

Some emails have to open a loop, and the honest ones name the work out loud.

There is nothing wrong with asking for something big. The dishonest move is dressing it up as a share, or shrinking it with "quick question" when it is not quick and you know it.

A good opener names four things: what the work is, roughly how much of it there is, who you think should own it, and what happens if nobody picks it up. "This needs about two hours from someone who knows the billing side. I can't do it this week. Can you take it, or point me at whoever should?" That is an opener, and it is a fair one, because the reader can say no to a defined thing.

Vague asks get ignored, and they have it coming. If you will not estimate the work, you are asking someone to accept an unknown, and most people handle unknowns by not replying. The same rule holds when the loop you are opening is a decision someone else has to make: define it, or watch it sit.

Run the audit on your sent folder

Open your sent folder, take the last twenty messages you wrote, and mark each one closed or open. Do it fast. No editing, just the mark.

Then look only at the openers and ask what each one made the reader do.

• Count the ones where the reader had to guess what you wanted.
• Count the ones where you promised to send something later.
• Count the ones that end in a question you could have answered yourself.
• For each, check whether a reply ever came, and how long it took.

The first time I ran this on myself the pattern was embarrassing in a specific way. My openers clustered late in the day. Tired me sends "thoughts?" because deciding is expensive and typing is cheap. That is useful to know, because it means the fix is scheduling rather than vocabulary: the messages that need a decision get written when you have one to give.

There is a second-order effect nobody warns you about. Your outbox shapes your inbox. Send openers and you get openers back, because you have taught the other person that this is how the two of you talk, and the thread becomes two people politely passing the same undone thing back and forth until someone books a meeting about it. Close loops for a month and your thread count drops on its own. A good week at work looks like an inbox where nobody is waiting on anybody, and that quiet starts in your sent folder.