Managing up: pushing back, then committing

Being overruled costs you nothing — how you respond to it is the whole game.

The idea

Managing up isn’t flattery. It’s learning how your manager decides, disagreeing well when you should, and then — once the call is made — committing without relitigating.

The counter-intuitive part: you build the most credibility not by winning the argument, but by disagreeing thoughtfully in private and then executing loyally after you lose it. That’s disagree and commit. Both silent caving and public relitigating quietly drain the same trust that a clean disagree-then-commit compounds.

How it works

It’s a sequence, and the order matters as much as the moves:

1. Learn the manager.  Fast or deliberate? Data or narrative?
   Decisive or consensus-seeking? Match how you raise it to how they decide.
2. Disagree in private.  One clear objection + the evidence + a
   recommendation. Not “I don’t like it” — give them a path.
3. Accept the decision.  Being overruled costs you nothing.
   Your response to it is what moves credibility.
4. Commit fully + set a checkpoint.  Execute as if it were your idea,
   and agree a date or metric to revisit. Loyalty now, learning later.
5. Close the loop.  Review it blamelessly at the checkpoint.
   Never “I told you so” — being right is not a licence to be righteous.

Notice what compounds: a real disagreement, heard and respected, followed by loyal execution. Skip step 2 and “commit” is just caving. Skip step 4 and a good disagreement curdles into a grudge.

When to use it

Watch out for

• Disagreeing in public first. Challenging your manager in the room, even when you’re right, puts them on the defensive and reads as grandstanding. Raise it privately first.
• Silent caving. The quiet killer. You say nothing, do the minimum — and the manager feels you disengage while the withheld judgment surfaces later as “why didn’t you say something?”
• Relitigating after the decision. Bringing it back up in standups or to peers is the fastest credibility bleed there is: you look unable to align, and the team gets mixed signals.
• “Commit” without the disagreement. Disagree-and-commit only builds credibility if the disagreement was real and heard. Jumping straight to compliance is caving with a nicer name.
• Weaponising a bad outcome. If it goes wrong exactly as you warned, “I told you so” spends every ounce of credibility your loyal execution just earned. Run the retro, don’t run a victory lap.

Worked example

A classic behavioral prompt: “Tell me about a time you disagreed with your manager.” A weak answer is either “I convinced them I was right” (misses the point) or “I just did what they said” (no judgment). A strong one walks the path: “I thought our launch date was too aggressive and I had the defect data. I raised it one-on-one with a recommendation to slip two weeks. My manager weighed it and decided to hold the date. I disagreed, but I committed — I ran the launch hard and asked that we track escaped-defect rate as our checkpoint. When that metric confirmed the risk, I brought it to a blameless retro rather than saying I’d called it, and we changed how we set launch dates.” Judgment, loyalty, and growth — in one story.