November 15, 2026 Jo Builds 7 min read

How to give your boss feedback in writing

Hand-colored engraving of a Medon butterfly, Drury 1837

Feedback to your manager works when it names one behavior, says what that behavior costs the work, and asks for one specific change. Everything else in the message is padding, and padding is what earns you a warm reply and no difference.

I send these in writing, and the reason has nothing to do with courage.

In a room, your manager reacts in front of you. There is no time to arrange the face, and the reflex that arrives first is defense. In writing they get the flinch in private, along with the reply they type and delete. By the time they answer you, they have already argued with you once and come out the other side, so the answer is about your point instead of about the moment.

The cost is that a document outlives the mood that made it. So write a document.

Attach a cost to the behavior

Feedback your manager can act on describes a behavior and its cost. Feedback they cannot act on describes their character.

"You micromanage" is a verdict on a person. There is no version of next week where they fix it, because you have not told them what to stop doing. "The Tuesday review on the migration doc means I rewrite the status twice a week and the work waits for the second pass" is a cost. It has a specific meeting in it and a specific thing that is not happening.

The test is whether the fix is smaller than their personality.

Write the cost down in one plain sentence before you write anything else. If the only cost is that the thing irritates you, you have a preference and not feedback. Preferences are allowed, and you can ask for one as a favor, in those words. Dressing a preference as a business problem is the move managers notice, and it spends credit you will want later.

Most of the upward feedback I have wanted to send was a preference in a good suit.

One thing, once

Put one piece of feedback in a message and leave the history out of it.

The urge is to prove the pattern, so you collect evidence: three incidents, dated, with quotes, in case a single example gets waved off as a bad week. What you have built is a file, and a file makes the reader defend themselves line by line instead of thinking about the point.

Give one clear example. Say in a short sentence that it is an example of a pattern, if it is. Then stop.

Two things happen when you stop. The message stays short enough to be read between meetings, which is the only time it will be read. And the reply comes back about the thing, because there is nothing else in there for it to be about.

Speak for yourself, never for the team

Write "I" and mean it, even when three other people agree with you and you know their names.

"A few of us have noticed" feels safer, because the weight is shared and no single person is exposed. It costs far more than it saves:

Your own experience is the only material you can defend under questioning. If the others want their version delivered, they can write it.

The whole message, assembled

The whole message is four moves and usually under a hundred words.

Here it is assembled. "I want to flag something about how the client updates get approved, because I think it is slowing us down. The last two went out three days after they were ready, waiting on sign off while you were at the offsite, and the client asked about the gap on the second one. Could I send the routine updates myself and hold only the ones with numbers or scope changes for you?"

Notice what the message leaves out. No theory about why the approvals are slow, and no mention of the four earlier times it happened. The ask is narrow enough that saying yes to it is not an admission of anything.

Narrow asks are how upward feedback actually gets adopted. Your manager can grant a small change without agreeing that they have a flaw, and once the small change is running, the general point makes itself.

What to cut before you send

The delete pass matters more than the writing pass. Here is what comes out of every one of mine.

Timing is the last cut. This message needs a reader with room in their day, so it does not go out on a Friday evening or an hour after something went wrong.

The last cut is the one I have to make on myself. My draft of one of these always lands a notch sharper than I would ever say it out loud, and I cannot see that on the first read, only on the second one hours later, which is time the message does not have. So I type the sharp version and swap it for the level one in the box, which is the shape Unvent ended up taking.

When not to send it at all

Skip the message when the only outcome you actually want is for them to feel bad.

The desire hides well. It shows up as a draft that is technically about process and keeps growing one more sentence at the end. If cutting that sentence guts the message for you, it was never about the process.

Skip it too when the thing you want changed was handed to them. Feedback about a constraint their own boss set is a request they cannot grant, and all it tells them is that you have noticed the box they are in. Ask what the constraint is instead, and you will often get a more honest answer.

Some managers punish this. You usually know which kind you have, and if you do not, one small piece of feedback is a cheap way to find out. Send something low stakes and watch what happens to it. What comes back tells you more about the job than your feedback told them about themselves.

After you send it

Judge the response on what changes in two weeks, not on the reply that arrives in ten minutes.

First replies to upward feedback are written under pressure by someone who has just been told something about themselves by a person they manage. They come out stiff, and they sometimes carry a small counterattack that gets quietly dropped later. Read it once and put it down.

Do not chase agreement either. "Noted, let me think about it" is a complete answer, and pushing for a confession turns your feedback into a disagreement you did not plan to have. You said the thing. It exists now.

The part nobody warns you about is what happens to you afterwards. Once you have sent one of these and the sky stayed up, the next one costs almost nothing, and you start noticing how many of them you were carrying around unsent, in a folder in your head, going stale.

Upward feedback that gets used

Unvent rewrites the draft right in the box you typed it in, in the tone you pick, so the observation reaches your manager without the heat that found it.

Get Unvent for 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.