Manage Your Boss

Use when — Use when your updates keep landing flat — they skim your docs, or zone out in your meetings.

Drucker’s sharpest distinction: readers take in information on the page and resent being talked at; listeners process out loud and won’t read your memo until you’ve walked them through it. Sending a 600-word email to a listener is shouting into a void. Cornering a reader for a verbal ramble feels to them like an ambush. Same content, wrong channel, dead on arrival.

Peter Drucker, “Managing Oneself” (HBR, 1999)

Use when — Use whenever you catch yourself thinking of your boss as someone to obey rather than a relationship to manage.

Gabarro and Kotter’s foundational reframe: you and your boss are mutually dependent. They depend on your cooperation, honesty, and output to succeed; you depend on their decisions, backing, and access. Seeing it as one-way — you serve, they command — is exactly why people stay passive and resentful. Recognize the dependence runs both directions and you’ll start managing the relationship like the adult, two-way thing it actually is.

Gabarro & Kotter, “Managing Your Boss” (HBR) — mutual dependence

Use when — Use when something’s gone sideways or a choice is needed, and your reflex is to “flag it” and let the boss figure out what to do.

An open-ended problem is work you’ve outsourced upward — you’ve made yourself a cost, not an asset. The fix is to do the thinking and arrive with “here’s what I’d do.” Bruce Tulgan calls this coming with proposed solutions; Andy Grove ran Intel so the person closest to the problem brought a recommendation and the manager simply decided. A recommendation also reveals your judgment, which is exactly what gets you trusted with bigger calls.

Bruce Tulgan, It’s Okay to Be the Boss; Andy Grove, High Output Management.

Use when — Use when you do strong work that quietly disappears, and you worry self-promotion will make you look like a peacock.

“Good work speaks for itself” is the most expensive myth in any career — work that nobody can see can’t be rewarded or defended. But bragging backfires. The bridge is to report results, not effort: give your boss specific, repeatable outcomes they can carry upward to their own boss. You’re not selling yourself; you’re arming your sponsor with ammunition. Frame it as the team’s win and your role inside it.

Adam Grant, “Give and Take” — generous contributors still need their value made visible to be rewarded.

Use when — Use when your boss is clearly out of their depth — new to the role, missing the domain, drowning — and the gap is starting to drag your work down with them.

The temptation is contempt: to expose the gap, route around them, or let them fail and inherit the role. All three usually backfire — you look disloyal, you lose your sponsor, and a flailing boss takes you down with them. The principled move is to become the scaffolding: fill the gaps quietly, make them look good without humiliating them, and earn the de facto authority that comes from being indispensable. Their success is, infuriatingly, still your success. A boss you’ve rescued becomes your fiercest advocate.

Mary Abbajay, “Managing Up”; Gabarro & Kotter, “Managing Your Boss” (mutual dependence)

Use when — Use after you’ve been thrown under the bus once — or work for someone you suspect would do it — and want to make the next time impossible.

A boss can only rewrite history that wasn’t written down. The people who get scapegoated are usually the ones whose decisions, approvals, and handoffs lived only in hallway conversations. Bus-proofing isn’t paranoia or politics — it’s leaving a quiet trail of confirmations so that “who decided this?” always has a clean, neutral answer. Done right, it never has to be deployed; its existence changes the incentive to blame you at all.