Managing up through the transition.
For the manager whose boss still wants the deck. Managing up isn’t politics — it’s the same four questions pointed at the seat above you. This guide covers the weekly note, the map of your boss’s seat, and how to sell the record upward, scripts included.
The four questions, pointed up
Tell · Do · Tell
A boss who hears nothing fills the silence with worry. Manage up with facts, not fear.
The idea
Everyone has a boss. The individual contributor has a manager, the manager has a director, and the CEO has a board. Managing up is not politics; it is the same four questions pointed at the seat above you, and the same loop — tell people what you'll do, do it, tell them you did it.
The principles are the same at every level. What changes is that you carry the context. What the seat above you needs is not status. It is confidence that the right things are handled, and evidence they can reuse in the rooms you are not in.
| Your seat | Seat above | What they need from you |
|---|---|---|
| Individual contributor | Manager | That the work is moving and they won’t be surprised. Judgment questions, not status. |
| Manager | Director | That the team’s work serves the goal they’re accountable for, and early warning when it doesn’t. |
| Director / VP | Executive | A number and a sentence they can repeat. Decisions framed, with a recommendation. |
| CEO | Board | Confidence that the right things are handled — and bad news before it’s a surprise. |
Right now it matters double, because the transition itself has to be sold upward. Your director still wants the deck. Your board still wants the annual plan. And the running record that could replace both stays invisible until somebody shows them what it can do. That somebody is you.
Map the seat above you
You can't give someone confidence without knowing what worries them. Fill this in once, in twenty minutes, and update it each quarter. If your boss has a user manual, read it first; if they don't, section 5 is a good reason to ask for one.
Fill it in once; update it each quarterTHE SEAT ABOVE ME Updated: [date] Who: [name, title] 1. WHAT THEY'RE MEASURED ON The number(s) their boss asks them about: _________________ What a bad quarter looks like from their chair: ___________ 2. THE ROOMS THEY'RE IN THAT I'M NOT Room: They get asked: ____________________ _______________________________ ____________________ _______________________________ 3. WHAT THEY CAN'T ANSWER TODAY The question about my work they'd struggle with, if asked cold: ____________________________________________________ 4. WHAT THEIR SILENCE FILLS WITH If they don't hear from me for two weeks, they worry about: __________________________________________________________ 5. HOW THEY TAKE IN INFORMATION (Read their user manual if they have one. If not, ask.) Format: [ ] written [ ] live [ ] numbers [ ] story Cadence they'd pick: __________ Length they'll read: ______ 6. WHAT THEY STILL NEED FROM THE OLD WAY The deck / plan / report they rely on: ____________________ What they actually USE it for (not what it contains): __________________________________________________________
Section 6 is the one that makes the transition possible. Your boss doesn't love the deck. They use it for something — to answer their own boss, to feel on top of things, to catch problems. Replace the use, not the artifact, and the artifact retires itself.
The weekly upward note
Five lines, sent on the same day every week, before anyone asks. The status update you volunteer costs you two minutes. The one someone has to request costs you their confidence.
Send it weekly, before they askUPWARD NOTE — week of [date] (5 lines. Facts, not fear.)
MOVED What changed this week, with a receipt.
[result] — [link / number / name of who saw it]
NEXT What I'm committing to, and when you'll see it.
[commitment] — by [day]
DECIDE A decision I need from you, by when, and my recommendation.
[question] — need it by [day]. I recommend [option], because
[one line]. (If none: "Nothing needed from you this week.")
EARLY A risk, before it's a problem — and what I'm already doing.
[risk] — [what I'm doing] — [when I'll know more]
(If none, say so. Silence here should mean "none".)
REUSE One line you can repeat in the rooms I'm not in.
"[a sentence, with a number in it]"Two lines do most of the work. EARLY is where trust is built: bad news with a plan attached, before it's a surprise — and when there's nothing, saying so, so that silence here always means “none”. REUSE is where you become valuable: a sentence with a number in it that your boss can say in a room you'll never be in.
Keep it to five lines. The note that grows into a report becomes the deck again.
Sell the record upward
The mistake is to argue. “The deck is obsolete” is a claim about your boss's judgment, and it will lose. Show, in parallel, and let them choose.
- Keep delivering what they ask for. The deck, the plan, the report — on time, in the format they know.
- Build it from the record, and say so. The deck prompt below does it with receipts attached. Note how long it took.
- Add the one section they didn't ask for: what the record caught that the old format would have missed — the drifting project, the decision nobody closed.
- Pre-answer their boss. Before their big meeting, send the three questions they'll likely get, and the answers, linked. Do it once, unasked. It makes the case better than any argument.
- Propose one swap, for one meeting. Not “kill the deck” — “can we try the record for the next review?” Then measure whether it was better, honestly, and let them call it.
Build the deck from the recordFrom the record below (meeting notes, commitments, what shipped, and open risks from [period]), draft the update my boss expects, in their usual format: [paste or describe their format: the deck outline, the report headings] --- [paste the record, or point to it] Rules: - Every claim links to where it happened in the record. No link, no claim. - Keep their headings, so it's recognizably "the deck". - Add ONE section they didn't ask for, at the end: "What the record caught" — decisions, risks or drift the old format would have missed. - Don't round up. If something slipped, say how much. - Then tell me how long this took, so I can say so.
If your organization wants a harder number than “it felt better”, run the Org Health Assessment before and after. A score that moves is a case that sells itself.
The scripts
Seven conversations that come up in every transition. Don't read them aloud — say them in your own words. But say them; the conversation you avoid is the one that gets decided without you.
Say it in your own words — but say it1. ASKING FOR A PARALLEL RUN (instead of arguing against the deck) "I'd like to keep sending you the monthly deck — but for the next four weeks, I'll build it from our running record instead of by hand, and send you the record alongside it. At the end, you tell me which one you actually used. If it's the deck, we keep the deck." 2. WHEN THEY ASK "WHERE'S THE DECK?" "It's here — [link]. It took me twenty minutes this month instead of a day, because it was assembled from the record. The record has one thing the deck didn't: [the risk it caught / the decision it surfaced early]. Want me to walk you through that part?" 3. SHOWING WHAT THE RECORD CAN DO "Before your meeting with [their boss], here are the three questions I think you'll get about our work, and the answers — each one linked to where it happened. You didn't have to ask me for any of it. That's the point I've been trying to make." 4. THE ANNUAL PLAN CONVERSATION "I'll write the annual plan — you need it for [the board / budget]. I'd like to add one thing: a monthly check of the plan against what the record says we actually did, so we find the drift in weeks instead of at the year-end review. It's one page. Can I try it for a quarter?" 5. BAD NEWS, UPWARD "Heads-up before it's a problem: [what's slipping], by about [how much]. The cause is [the real cause, not the polite one]. I'm already doing [action]; you'll know if it's working by [date]. What I need from you: [a decision / cover / nothing yet]." 6. NAMING THE VERB (when AI plans reach your team) "Before we decide how to roll this out: are we using it to replace the work people do, or to empower the people who do it? Both are choices. I'd like us to make this one on purpose — and here's what I think it looks like on my team if we choose empower: [one concrete example]." 7. ASKING FOR JUDGMENT, NOT GIVING STATUS (for your 1:1) "Status is in the note — I won't repeat it. What I'd like your judgment on is this: [the one target or decision I'm unsure of]. Here's what I'm weighing: [two options]. What would you do?"
Script 6 is the one to have early. Every AI plan picks a verb, whether or not anyone says it: replace the people doing the work, or empower them. Naming the verb out loud is how you make sure it's chosen on purpose rather than by drift.
Run it with your AI partner
If an agent holds your record — meetings, commitments, what shipped — the note drafts itself and nothing slips out of it quietly. (The Work OS keeps that record for you.) Give it this standing brief:
A standing brief for your AI partnerStanding brief: help me manage up. My boss is [name]. Their "seat above me" map is [link]; their user manual (if any) is [link]. 1. Every [Thursday] afternoon, draft my 5-line upward note from the record: MOVED (with receipts), NEXT (with dates), DECIDE (with my recommendation), EARLY (risks, with what I'm doing), REUSE (one repeatable line with a number in it). 2. Never soften a slip or a risk. If the record shows something slipping and I haven't mentioned it, put it in EARLY and flag it to me. 3. Before any meeting my boss has with their own boss or the board, list the three questions they're likely to be asked about my work, and the answers from the record. 4. If I haven't sent my boss anything in 7 days, tell me. Silence fills with worry. 5. Once a month, check my map of their seat against what they've actually asked me about. Suggest updates.
What stays yours: which risk is worth your boss's attention, the recommendation in DECIDE, and the decision to be honest in the note. An AI can draft your status update. It cannot decide to be honest in it.
What not to do
- Sell with fear. “We'll fall behind if we don't” buys attention once and trust never. Sell with facts: time saved, a risk caught, a question pre-answered.
- Over-claim. If the record saved four hours, say four. The first inflated number is the last one they believe.
- Surprise them in public. Anything that could embarrass your boss in a room reaches them first, in private, in EARLY.
- Go around them. Pre-answering their boss's questions goes through your boss, never past them.
- Send status theater. A long note that says nothing is worse than a short one that admits a slip.
- Go quiet. The week you have nothing to report is the week to send “nothing slipped, nothing needed”.
The short version fits on a sticky note: manage up with facts, not fear. Then point the same loop at yourself, in your weekly review.
From chapter 17 of Everyone Is a Manager Now, on what happens to managers when the relay half of the job is automated — and the half that just became the whole job.
More field guides
Copy-paste playbooks you can run todayA private, file-based chief of staff you run in Claude Code — the TRAM loop as a folder of markdown.
A prompt pack that turns Claude into an org-health analyst — feed it your data, get the 21-point scorecard and spider chart.
The hand-it-to-Claude-Code build spec for a personal AI work OS — vision, a legible data model, a full prompt pack, and a phased build plan.
A one-page delegation brief — intent, context, constraints, definition of done, review plan. Brief a machine the way you’d brief a bright new hire.
A fifteen-minute weekly review on the FIT loop — Feel, Inventory, Target. The 1:1 you owe the first report on your own org chart.
One honest page about how to work with you — how you decide, how you take bad news, what your silence means — plus an extended version, the prompts to draft it, and the habit of reading each other’s.
The record, ready for the room.
Write the upward note by hand and you'll see the difference in a month. Let Ari keep the record — meetings, commitments, what shipped, what's slipping — and the note drafts itself every week, receipts attached.