Managing Your Boss

The overview made the case that managing up is not flattery — it’s the ordinary work of making a working relationship function in both directions. This page starts where every reader has skin in the game: the relationship with your own boss.

Here is the reframe the whole page turns on. Your manager is not a weather system you endure or a judge you perform for. They are a person — with their own boss, their own pressures, their own incomplete view of what you do all day, and a limited number of hours. Once you see them that way, “managing your boss” stops feeling manipulative and starts feeling obvious: it’s figuring out what they genuinely need from you, and giving them that reliably. Do it well and a surprising thing happens — you stop worrying about your manager at all, because you know exactly what they’re getting from you.

Start by diagnosing them, not impressing them

Most people try to manage up by looking good: more updates, more visible effort, more enthusiasm in meetings. That’s aimed at the wrong target. Your boss doesn’t primarily want to be impressed — they want to be able to stop worrying about your area. To give them that, you first have to understand two things about them.

What are they measured on? Every manager answers to someone or something — a director, a board, a set of quarterly numbers, a safety record, a customer-satisfaction score. Their success is defined largely by things happening above and around them that you may never see. When you understand what your boss is judged on, you can see which of your tasks actually move their needle and which are just noise you happen to be busy with.

What are they worried about? Separate from what they’re measured on is what keeps them up at night right now — a slipping deadline, a fragile client, a team member who’s struggling, a budget review next month. Worries are more current and more emotional than metrics, and they change. A boss who’s about to present to their boss cares intensely, this week, about anything that could embarrass them in that room.

Diagnose your boss on one page:

  Measured on   → the 2-3 outcomes their own success depends on
  Worried about → what's fragile or scary for them THIS month
  Your work     → which of your tasks map to the above?
                  (the mismatch is where you're wasting effort)

When your work maps to their real priorities, two things happen. Your effort starts to register — it lands on things they actually care about. And you gain the standing to push back on the rest, because you can say “this doesn’t seem to move the things you’re accountable for” and be taken seriously.

In practice — the same report, reframed

A ward nurse manager kept sending her hospital director a detailed weekly log of shifts and incidents. It was thorough and largely ignored. Then she learned the director was being measured that quarter on patient-discharge times and staff overtime. She kept the same underlying work but led every update with two numbers: average discharge time and overtime hours, with a one-line note on each. Nothing about her actual job changed. But now her reports landed on exactly what her boss was accountable for — and within weeks the director was quoting her figures upward. Same effort, aimed correctly.

The no-surprises principle

If you take one rule from this page, take this one: bad news should reach your boss early and directly, from you. The instinct is the opposite — to wait, to hope the problem resolves itself, to soften it, to avoid the uncomfortable conversation. That instinct quietly destroys trust.

Here’s the mechanism, from first principles. A manager’s core need is predictability — the ability to make commitments upward and have them hold. A problem in your area is survivable; they can re-plan, ask for more time, warn their own boss. But a surprise — a problem they learn about too late to manage — strips away their ability to respond and often embarrasses them in front of the people they answer to. The damage isn’t the problem. The damage is that they no longer know what else you’re hiding.

So the trust-preserving move is counter-intuitive: the worse the news, the faster and more directly you deliver it. “The launch is going to slip — I found out this morning, here’s what I know so far” told on day one is a manageable event. The same news discovered by your boss on the deadline is a betrayal, even if the underlying facts are identical.

The surprise curve:

  Problem exists ──────────────────────────► Deadline
       │                                          │
   you tell them here            vs.        they find out here
   → "thanks for the heads-up"              → "why am I only hearing this now?"

  Same problem. Opposite outcome. The variable is TIMING, not severity.

The common trap — waiting until you have the full picture

The most common reason people sit on bad news is a reasonable-sounding one: “I don’t want to raise the alarm until I understand it fully.” But by the time you fully understand a problem, it’s usually too late for your boss to help. Raise it while it’s still fuzzy — that’s precisely when their extra information, authority, or calm is most useful. “Something’s wrong with the shipment and I’m still digging, but you should know now” is a stronger message than a perfect diagnosis delivered a week late. Flag early, then keep them posted as clarity arrives.

Case study — the 1986 Challenger launch

The night before the Space Shuttle Challenger launched on 28 January 1986, engineers raised concerns that the cold temperature could compromise the rubber O-ring seals. Those concerns existed low in the organization but were softened, disputed, and did not travel clearly and forcefully up to the decision-makers. The shuttle broke apart shortly after launch, killing all seven crew. Investigations afterward pointed repeatedly to a communication failure: warnings that were real but did not reach the people with authority in a form they could act on. The lesson for ordinary managing-up is stark — bad news that stays comfortable and low doesn’t protect anyone. Getting the concern upward, clearly, in time to act is the whole job.

Bring solutions, not just problems

Delivering bad news early does not mean dumping your anxiety on your boss’s desk. There’s a difference between informing your manager and offloading a worry onto them. The second one feels, to a busy manager, like being handed one more thing to figure out.

The upgrade is simple: whenever you bring a problem, bring the shape of a solution with it. You don’t need the answer — you need to have thought about it. Arrive with two or three options, a quick read on the trade-offs, and a recommendation.

Instead of:  "The supplier missed the delivery. What do we do?"

Bring:       "The supplier missed the delivery. Three options:
              (a) switch to the backup supplier — costs ~15% more, ready Friday
              (b) delay the order two weeks and stay with them
              (c) split the order across both
              I'd go with (a) — the deadline matters more than the margin here.
              Your call."

The second version does three things at once. It respects your boss’s time. It shows you’ve done the thinking, which builds their confidence in handing you more. And — quietly important — it shifts the default. Now the conversation is about choosing between good options, not about generating them from scratch. Even if your boss picks a different option, you’ve made their decision faster and better.

There’s a limit, and it matters: don’t over-package. If a problem is genuinely urgent, ambiguous, or above your authority, saying “I’m not sure what to do here and I need your help thinking it through” is the honest and correct move. Bringing solutions is the default, not a law. The goal is to arrive having engaged with the problem, not to pretend you have every answer.

Learn how they actually like to work

Two managers can want the exact same outcomes and yet need completely different things from you day to day, because communication style is personal. A large share of managing-up friction is not disagreement — it’s mismatched format. You’re giving long written updates to someone who processes by talking; you’re pinging someone hourly who wanted a weekly summary.

There are four dials worth reading deliberately:

• Cadence — how often do they want to hear from you? Daily check-in, a Monday summary, or only when something changes? Ask directly: “How often would you like updates from me, and when things are running smoothly, would you rather I stay quiet or still check in?”
• Format — a two-line message, a short doc, a quick call, a number in a shared sheet? Some people read; some need to talk it through.
• Level of detail — do they want the headline and the decision, or the full reasoning behind it? Giving a detail-lover only the headline reads as evasive; burying a headline-person in detail reads as noise.
• Involvement — where on the spectrum do they sit between “keep me out of it until it’s done” and “loop me in on the small stuff”? And which decisions do they want a hand in?

You don’t have to guess. The fastest route is to ask, early: “I want to make this easy for you — how do you like to be kept in the loop, and what do you want to be consulted on versus just informed about?” Most managers have never been asked and will tell you gratefully. Then watch what actually lands: which of your updates get a real response, which get ignored, which prompt “why didn’t you tell me sooner.” Their reactions are teaching you their preferences in real time.

The evidence — style mismatch reads as a performance problem

Managers and researchers who study workplace relationships tend to find the same thing: a large portion of what gets labeled a “performance” or “attitude” problem is really a communication-style mismatch that was never named. Someone judged as “not proactive” was often simply waiting for the cadence their previous, more hands-off boss preferred. The encouraging implication is that a lot of managing-up trouble is fixable with a single explicit conversation about how we’ll work together, rather than any change in the actual work.

Give them the right decisions — not all of them, and not none

Here’s a subtle skill that separates people bosses trust from people they merely tolerate. It’s about upward delegation — deciding what to hand your manager and what to handle yourself.

Two failure modes sit at the extremes. Under-delegating up is deciding everything yourself, including things that were genuinely your boss’s call — the budget trade-off, the promise to a client, the priority when two urgent things collide. This blindsides them and oversteps your authority. Over-delegating up is the opposite and far more common: bouncing every small decision upward, so your boss becomes the bottleneck for your own work. Each time you ask “which should I do first?” about something you could reasonably judge yourself, you’re handing them cognitive load and quietly signaling you can’t be left alone.

The skill is sorting decisions into the right bucket:

Handle it yourself      → it's within your remit and reversible
Decide, then inform     → it's yours, but they'd want to know it happened
Bring options + a rec   → real trade-offs, but you can steer it (see above)
Escalate the decision   → it's above your authority, high-stakes, or
                          irreversible — this is genuinely their call

A good rule of thumb: reversible decisions in your area you make and mention; irreversible or high-stakes ones you take to your boss as a real decision, well-framed. When you do escalate a genuine decision, do it the same way you’d bring a solution — with the options and trade-offs laid out — so you’re handing them a clean decision, not a research project.

Get this sorting right and you become the rarest thing to a manager: someone they can hand an area to and stop checking on. That is what “reliable” actually means. It’s not that you never have problems — it’s that they always find out the right things, at the right time, framed as a decision they can actually make.

How it connects

This page is about the single most important relationship you manage upward. The next pages widen the lens: Mapping Your Stakeholders applies the same “diagnose what they need” thinking to everyone else you depend on, and Setting and Managing Expectations turns the no-surprises principle into a repeatable practice. When influence has to happen without a reporting line, see Influence Without Authority; when a problem needs to go up the chain, Escalation Done Right builds directly on the no-surprises idea here.

Try this

This week, write your boss’s one-page diagnosis: list the two or three outcomes they’re measured on, the one or two things you think they’re worried about right now, and their communication preferences (cadence, format, detail, involvement). Fill in what you know, and mark the gaps. Then, in your next one-on-one, ask one direct question to close the biggest gap — most likely “how do you like to be kept in the loop, and what do you want to be consulted on versus just informed about?” You’ll usually learn more in that one answer than in a month of guessing.

Reflect

1. What is your boss actually measured on — the outcomes their own success depends on? How confident are you, and where did that confidence come from?
2. Think of the last piece of bad news in your area. How and when did your boss find out — and if it were to happen again, what would “early and direct” have looked like?
3. When you last brought your manager a problem, did you bring options and a recommendation, or an open-ended worry? What would the solutions version have sounded like?
4. Which of the four dials — cadence, format, detail, involvement — are you most likely getting wrong with your current boss? What’s your evidence?
5. Are you under-delegating upward (deciding things that were their call) or over-delegating (bouncing small decisions to them)? What’s one decision you could re-sort this week?

Show reflections

1. If your answer is vague (“they want the team to do well”), that’s the finding — you’re managing up half-blind. Confidence should come from something concrete: something they’ve said, a metric they report upward, a topic they keep returning to. If you can’t point to a source, that’s your next conversation.
2. The useful move is to separate the problem from the surprise. Most regret in these situations isn’t about the problem existing — it’s about the timing of the telling. “Early and direct” almost always means telling them while it was still fuzzy and manageable, not after you’d fully diagnosed it.
3. Be honest about the difference between informing and offloading. The solutions version has a shape: here’s the situation, here are two or three options with trade-offs, here’s what I’d do, your call. If you handed over a bare worry, you handed over work.
4. Your evidence is in their reactions — updates that get ignored, “why am I only hearing this now,” or “you didn’t need to check with me on that.” Those responses are your boss teaching you their dials. The fix is usually one explicit question, not a guess.
5. Over-delegating is the more common trap and the easier one to feel virtuous about (“I’m keeping them in the loop”). A good re-sort names one reversible, in-your-remit decision you’ll now just make and mention — and, if relevant, one genuinely high-stakes call you’ve been making alone that actually belongs to them.