Managing Up: Make Your Boss Your Lever, Not Your Ceiling
Topic: Managing Up·4 Principles
"Managing up is not sucking up — it's making your boss's job easier so they can make yours possible." — Julie Zhuo
This week's premise: Many tech leaders misread "managing up" as sucking up or political theater. Wrong. The real name is two-way supply-demand alignment: you learn your boss's real constraints and scoring rubric; they get low-noise, high-quality signal from you; you trade for oxygen, resources, and air cover. Failing at it doesn't mean "your boss dislikes you" — it means your team's good work gets distorted or vanishes in their field of view. Four moves: (1) read your boss's calculus; (2) make work visible without being slimy; (3) persuade up with a one-page memo; (4) be a shit umbrella, not a megaphone.
PRINCIPLE 01
Read Your Boss's Calculus: Whose Score Are They Raising?
Read Your Boss's Calculus
UnderstandingPressureScoring Rubric
One-Line Principle
Your boss is not the endpoint — they have a boss, KPIs, and faction positioning of their own. Before any request or pushback, answer one question: does this add or subtract on their scorecard? If you don't know, go find out before you open your mouth.
Key Quote
"Your boss has a boss. Your boss has goals, constraints, and a worldview that may not be obvious to you. Part of your job is to figure those out."— Julie Zhuo, The Making of a Manager, Ch. 8
Four Dimensions of Your Boss's Ledger (silently run through before any ask)
Scene
Situation: you want a 6-week tech-debt refactor approved. Your boss got grilled last week by their boss on "why are launches slowing down?"
✗ Failing opener
"I want 6 weeks to refactor X — long-term it'll make the code cleaner, the team happier." → Your boss hears: you're adding load, not removing any.
✓ Same ask, aligned to their ledger
"Last quarter launches slipped 9 days on average; root cause is 70% in module X. I'm proposing a 6-week refactor — commitment to you: by Q3, launch cycle drops back below 5 days. That's a number you can hand the VP next quarter. Want me to write it up as a one-pager for review?"
Checklist (before any request)
Can I name 3 specific numbers my boss is graded on this quarter?
Does my ask map to one of those? Am I using their language or mine?
What was the last awkward question they got asked at ELT / skip-level?
Does this give them something they can say upward?
Common Mistakes
Treating your boss as abstract authority. They are not a judge — they're a person with a KPI sheet.
Tech-correct pitch, no business translation. "Cleaner code" is not a KPI; "launch cycle −4 days" is.
Misreading the ledger and not auditing. Rejection → blaming "they don't get tech," instead of asking "which pressure of theirs did I step on?"
This Week + Reflection
Action: Spend 5 minutes writing down your boss's 3 KPIs and 1 recent pain point. In your next 1:1 confirm with a low-risk question: "I'm guessing your tightest one this quarter is X — right?" Either answer is information. Reflect: Your last rejected request — was it really the plan, or did you step on a minus item on their ledger?
PRINCIPLE 02
Self-Advocacy Without Being Slimy: Let the Work Speak
Self-Advocacy Without Being Slimy
VisibilityBrag DocWeekly Update
One-Line Principle
In a big company, no one is obligated to track your team's good work. Surfacing it is your job. Silence ≠ humility; silence = letting other people write your story.
Key Quote
"If you're the kind of person who hopes good work will speak for itself, you're going to be passed over by people whose work is louder than yours."— Tomas Chamorro-Premuzic, Why Do So Many Incompetent Men Become Leaders?
Scene: Two Versions of a Monday Update
Situation: last week your team shipped a latency win, resolved a P0, and signed a staff eng. You owe your boss a Monday update.
✗ Humble (= invisible)
"Last week was fine. Team's on track. Some latency improvement, some hiring progress. Continuing this week."
✓ Facts + impact + attribution
"Three things: (1) P95 latency dropped from 480ms → 310ms (A led). Impact on your OKR: unlocks the Q3 latency-SLA commitment. (2) P0 Wednesday (B diagnosed + fixed in 25 min). Postmortem shared, zero customer impact. (3) Staff offer signed (C). Onboarding 8/1, will pick up the X project you asked about. Asks of you: none. Risk this week: D project is stuck on cross-team review; if no movement by Monday I'll escalate."
Brag Doc — 3 columns, 10 min/week
What: what shipped this week, one line + a number.
So what: concrete impact on boss's KPI / company OKR / customer.
Who: who led (your team member), what role you played (unblocked / designed / negotiated).
Before perf review, promo conversations, and skip-level 1:1s, this doc is the one place you won't have to reconstruct from memory.
Common Mistakes
Claiming team wins as your own. Reports notice and bleed out. Naming them actually raises your credibility as a leader.
"I'll save it for perf review." By then your boss's impression is already filled by high-visibility peers.
All sunshine, no risks. An empty "risk" column = the day something blows up, your boss stops trusting your updates.
Female Leader's Note
Research (Bowles, Babcock) shows female leaders face a double bind in self-advocacy: too quiet = overlooked, too loud = labeled "aggressive." A workable detour: rewrite "I did X" as "the team did X, and what I did was clear Y for them" — credit the team (likability) while anchoring your leadership move (competence). Sandberg calls this the "we language with I anchor" in Lean In, Ch. 4.
This Week + Reflection
Action: Start a Brag Doc, backfill the last 4 weeks. This Monday, send a three-column update to your boss. Reflect: Your team's biggest recent win — does your boss's boss know about it? If not, whose failure is that?
PRINCIPLE 03
The One-Page Memo: The Highest-Bandwidth Way to Persuade Up
The One-Page Memo for Persuading Up
WritingDecision RequestOptions
One-Line Principle
The higher someone sits, the more fragmented their time and the shallower their context. Don't bring problems to your boss — bring options with a recommendation. A 5-minute one-pager beats a 30-minute meeting you can't get to a decision.
Key Quote
"The higher you go, the more you need to write. Senior leaders read; they don't sit through your slides. A crisp one-pager beats a 30-minute meeting."— Camille Fournier, The Manager's Path, Ch. 7
Five Sections of the One-Page Memo
(1) Context, 3 sentences: what, why now, cost of not deciding.
(2) Options, 2–3: each with one line cost / one line benefit / one line risk.
(3) Recommendation + reason: which one, why — this is the most important line.
(4) What you need from your boss: "approve X" / "ping Y team" / "FYI only."
(5) Default if no reply: what you'll do by when if they don't respond.
Scene
Situation: you want to shift the team's on-call rotation from 1 week to 2 weeks. Needs boss approval.
✗ Verbal mode
"Hey, got 10 min? About on-call — the team's pretty burnt out lately, I want to talk through some changes…" → 30-minute meeting, no decision, "let me think."
✓ Drop the memo in Slack (no meeting)
"On-call proposal — Context: over the past 6 weeks, 3 people paged 8+ times in their on-call week, 2 mentioned wanting off the team. Options: (A) status quo (cost: attrition risk high); (B) 2-week rotation with secondary backup (cost: 2 weeks less mental freedom per person, benefit: weekly load −40%); (C) hire external (cost: 1 headcount + 3 months). Recommend B — zero cost, can ship this month. From you: sync with Q team since we share paging boundaries. If no objection by Friday, live Monday."
Common Mistakes
Only one option. Reads as cornering. Three options + recommendation gives them the dignity of choosing.
Burying the recommendation. Put it in section 3, not section 7. Don't make them read to find what you want.
Missing section 5. Without a default action, the memo lands in "later." "If no objection by Friday, live Monday" is the most powerful single line.
This Week + Reflection
Action: Pick one thing you've been sitting on for 2+ weeks. Write it as a ≤350-word, five-section memo. Send it (don't book a meeting). Reflect: Of the asks your boss said "let me think" to in the last six months — how many were problems you brought, instead of options with a recommendation?
PRINCIPLE 04
Be the Shit Umbrella, Not the Megaphone
Shield the Team Without Lying to Them
Air CoverTransparency EdgeNo Anxiety Pass-through
One-Line Principle
Noise from above (reorg rumors, headcount anxiety, your boss's mood) does not get passed down unprocessed. But also — don't hide every real constraint; that's just a different lie. Distinguish: absorb "noise," be transparent about "facts and constraints."
Key Quote
"Your job is to be the shit umbrella, not the shit funnel. But also: don't lie about the weather."— Lara Hogan, Resilient Management, Ch. 5 (paraphrased from the common verbal version)
Absorb vs. Transparent: Decision Map
Scene
Situation: Monday's staff meeting your boss is in a foul mood and hints Q3 might bring a hiring freeze. You have a team meeting Tuesday.
✗ Funnel mode
"Boss was pissed yesterday — Q3 might freeze hiring, brace yourselves." → That night, the team updates LinkedIn photos, two start interviewing. You manufactured panic you could have absorbed.
✓ Umbrella mode (absorb noise, surface fact)
"A few things: Decided — next quarter's priorities are still X and Y. In flux — Q3 headcount is still being discussed; I'll sync the moment it's decided. Doesn't affect the two offers in pipeline. My commitment: anything that touches your projects or your livelihood, you hear it from me the week I know — not from someone else. Bring questions to me."
Common Mistakes
"I'm just as frustrated as you" — seeking empathy. Reports don't need a manager who shares the misery; they need one who can block it.
"Leadership asked me to relay…" — deflecting ownership. Whatever you pass on, you own. Say it in your own words.
Over-absorbing. Carrying everything yourself, telling them nothing = one day a layoff blindsides them + permanent loss of trust.
"It's not decided yet" as a universal shield. "Still undecided" past a certain point is itself information — say so.
This Week + Reflection
Action: List 5 pieces of info you received from your boss in the past 2 weeks. Label each "absorb / transparent." Use this filter to decide what to say at your next team meeting. Reflect: Does your team's trust in you rest more on how much you share, or how much you block?
Going Deeper
If your boss is genuinely the "bad boss" (incompetent, political, volatile), does managing up still apply?
Yes, but the goal shifts. With a good boss, managing up amplifies their leverage. With a bad one, it lowers your probability of being damaged. Concrete moves: (1) every important decision in writing — leave a paper trail; (2) build skip-level visibility so the layer above sees your work independently; (3) define how long you'll tolerate it — set a personal deadline, then activate transfer or external search. Ben Horowitz in The Hard Thing About Hard Things repeats it: what you control isn't your boss, it's your exit options.
In East Asian / collectivist cultures, doesn't self-advocacy get penalized as "not humble enough"?
It's a real risk. Detours: (1) Replace "I" with "the team" throughout, but name individuals — your ownership as manager doesn't need to be spoken, the structure proves it; (2) frame around "promise → delivery," not greatness — "I committed X last quarter; result was Y." Numbers are safer than adjectives; (3) find a sponsor (not a mentor) who talks about you in rooms you're not in. In Asian contexts, the third yields the highest return per unit effort.
What if nobody at your company uses one-page memos? Your boss only takes verbal / group chat.
Use it quietly, don't announce it. In your 1:1, say casually "I wrote the context here, take a look when you can" and attach a link — most bosses will quietly read it. Stick with it for 4–6 weeks and you become known as "the one who thinks before walking in," and it starts being copied back. The memo isn't a replacement for the meeting — it compresses the meeting from "what is it" to "what do we decide". Even if your boss never reads, the memo's real beneficiary is you: it forces clarity, and you walk in the most prepared person in the room.
Air cover (absorbing) vs. transparency — how do you keep the line stable instead of wobbling?
Anchor with one hard rule: anything that touches their livelihood or daily work, I say within the week; everything else, absorb first. Applied: reorg rumor (no impact) → absorb; headcount in flux (not yet impacting) → absorb; signed reorg list (impacts) → say immediately. Wobble usually comes from confusing "I'm anxious and want to vent" with "they need to know." Vent to a peer manager or coach — never to your team.
For a tech lead manager in a big company, how much time should managing up consume?
Heuristic: steady state ~15–20% (6–8 hours/week including 1:1s, memos, upward updates, skip-level prep). During big events (reorg, perf, budget season) it temporarily spikes to 30%. Below 10% usually means your team's results are getting distorted in the system; sustained above 30% for more than a quarter means you're turning into a political animal and drifting from the tech. Calibration: end of each quarter, compare your team's resources / promos / project allocation vs. peer teams — losing out = managing-up debt, pay it down; not losing out and you're still exhausted = you can dial back.