Assume your skip-level will read about nine minutes of your writing this quarter. Not per document — in total. Nine minutes across thirteen weeks, in fragments, mostly on a phone, mostly while something else is happening.
The number is invented and the constraint is not. Work out roughly how many people report into someone two levels above you, multiply by the documents each of them produces, and the arithmetic gets grim quickly. Whatever the true figure is, it is small, it is fixed, and it is yours to spend. Most people spend it on a comprehensive document, which is a way of spending it all at once on nothing.
The budget is the whole design constraint
The mistake is treating each update as a self-contained document that should stand alone. It should not. It is one withdrawal from a small account.
Two consequences. First, you are not trying to inform this person fully; you are trying to leave them with a correct impression and one actionable thing. Second, most weeks you should send nothing at all, because an update with no decision in it and no change of state spends budget to buy nothing, and it teaches the reader that your name in their inbox is safe to skip — which is a cost you pay later, in the week when it is not.
Send when one of three things is true: a commitment they have repeated to someone else has changed, a decision needs them specifically, or they are about to be surprised in public. Otherwise, stay out of their inbox.
What a skip-level actually needs
Three things, and none of them is progress.
Whether the thing they told someone else is still true. They have repeated a date or a scope to a peer, a board, a customer. Your update’s first job is to confirm or correct that sentence.
Whether there is a decision only they can make. Not one they could make — one that is blocked without them. Anything else is being sent for visibility, and visibility is not a reason to spend the budget.
Whether they are about to be surprised in front of other people. This is the one that earns you standing. A skip-level who has never been caught out by something in your area will read your next document.
Notice what is absent: effort, process, how hard it was, what the team learned, how many tickets closed. All of it is real and none of it belongs here.
The update, in full
Subject: Atlas — holding 12 October, need your call on the two legacy account types
Atlas is on track for 12 October. That is the date you gave the customer council; it has not moved since the last update and I do not expect it to.
One decision needs you. Two rare account types — about 40 customers — will not migrate by 12 October. Either they stay on the old flow until November, or we hold the whole migration for them. I recommend the first, and Priya agrees; it is your call because the customer council heard “all accounts”.
I need a yes or no by Thursday 24 September. If I have not heard, I proceed with the first option and we tell the 40 accounts on the 25th.
One thing you might be asked about: those 40 accounts are on our largest reseller. They will notice.
Detail, if you want it: [link]. Otherwise nothing else needs you.
A hundred and eighty words. Under a minute of the budget, and it does everything the nine minutes exist for.
The linked detail matters even though it will not be read. It is there so the reader knows the compression was a choice and not the extent of your thinking, and so that the one person on their staff who does check has somewhere to go.
The line that survives being forwarded without you
This one:
Atlas is on track for 12 October — but two rare account types, about 40 customers on our largest reseller, stay on the old flow until November.
Write it deliberately, because it will travel. A skip-level’s main use for your document is not reading it; it is repeating one sentence from it in a room you are not in, from memory, three days later, under mild pressure. That sentence is your actual output.
Three properties make a sentence survive:
It is true standing alone. Strip every antecedent — no “as discussed”, no “the above”, no “this”. A sentence that needs the paragraph above it will be forwarded without the paragraph above it.
It contains the caveat. If the good news and the exception are in separate sentences, the good news travels and the exception does not. Someone will then be surprised in November, and you will have technically written it down, which is worth nothing. Bolt the exception to the claim with a dash or a “but” so it cannot be cleanly severed.
It names the concrete thing. “Some edge cases” survives as “it’s fine”. “Forty customers on our largest reseller” survives as itself, because it is specific enough that repeating it vaguely feels wrong.
Write that sentence first, then write the update around it.
What they will never read
Worth naming, because each of these feels obligatory and each is a withdrawal against nothing.
- Effort. Nights, weekends, heroics. It reads as either a complaint or a bid, and a skip-level has no mechanism to respond to it.
- Process. How you decided, who you consulted, which framework you used. If the decision is right, the process is invisible; if it is wrong, the process is not a defence.
- Blockers you have already cleared. The narrative of the obstacle you overcame is for people who share your day. Two levels up it reads as noise with a happy ending.
- Anything with an acronym they would have to ask about. They will not ask. They will form an impression of the sentence containing it, and the impression will be worse than the truth.
- Thanks and framing. “Wanted to give you visibility into” is four words of budget spent announcing that a document exists, in a document.
The version that failed
Subject: Atlas migration — September update
Hi — wanted to share where we’ve landed on Atlas as we head into the final stretch. It’s been a busy few weeks: the team has done excellent work on the account-merge path, and after the dry-run findings in early September we reorganised around the legacy account types, which turned out to be considerably more involved than our original scoping suggested. We’ve since stabilised the nightly dry migration and are seeing consistent results.
Current status is green for 12 October. There are a couple of open questions around the rarer account types which we’re working through with Priya, and we’ll have a recommendation shortly.
Happy to walk through any of this in more detail — let me know if a session would be useful.
It is compressed along the wrong axis: it shortened the detail and kept the shape of a report.
“Status is green” and “a couple of open questions” cannot both be true; the reader either notices and now distrusts the green, or does not notice and is surprised in November. “We’ll have a recommendation shortly” is the ask, disguised — no date, no name, nothing to do, so nothing happens and you write the same paragraph next month. The closing offer of a session hands the initiative over: a reader who takes it books thirty minutes to be told something that fitted in two lines, which is the outcome the written update existed to prevent.
The tell runs through all of it and starts in the first sentence. A document that opens by explaining that it is a document has not yet decided what it is for.
What this costs
You lose nuance, and you can be held to what survived. The forwarded sentence is now the version of reality that exists in rooms you are not in. If it was slightly optimistic, that is the one that gets quoted back. Write it as the version you would defend in November, not the version that reads best in September.
It can look like less work than it was. A hundred-and-eighty-word update from someone who spent a quarter on something reads, to an inattentive reader, as a small thing. There is no clean way around that. The compensating move is the linked detail, and your own manager, who reads the long version and knows what is in it. Your skip-level is not the audience for the evidence of your effort.
Compression is slow. The short update takes longer to write than the long one, every time. Budget an hour for something that will be read in fifty seconds, and expect the first draft to be four times too long.
If they did not ask for it
Most of this assumes an established expectation. If nobody asked you for a skip-level update, do not start one unilaterally — an unrequested document arriving from two levels down reads as either a bid or an escalation, and it will be received as whichever one your manager is more worried about.
Send it to your manager and ask whether they want it forwarded or want to forward it themselves. They will usually do the second, which is the correct outcome: the same sentence arrives, it arrives with their endorsement attached, and you have not routed around anyone to deliver it.