One of the most common managing up mistakes is getting the escalation dial wrong in one direction or the other: either escalating too much (creating dependency, clogging your manager's queue, undermining your own authority) or too little (getting caught in problems you should have flagged, surprising your manager with crises they needed to know about).

The goal is not to escalate more or less. It's to escalate better — with better judgment about what actually requires a higher-level call and what doesn't.

The Escalation Matrix

Andy Grove's framework in High Output Management is useful: every employee should have a defined decision-making domain — what they're authorized to decide without escalation. Managers define this. Your job is to know when a situation has moved outside that domain.

Use four dimensions:

  • Reversible vs. irreversible: can we undo it cheaply if wrong?
  • Contained vs. broad blast radius: does the consequence stay inside your team or hit customers, revenue, legal, brand, or other teams?
  • Non-urgent vs. urgent: is there time for normal alignment, or does delay create damage?
  • Authority required vs. not required: can you make the call, or does someone above you own the tradeoff?

Then choose the escalation category. This is the practical decision rule for most ICs: if the decision is reversible, contained, and inside your authority, handle it; if it is irreversible, broad, urgent, or outside your authority, escalate with a recommendation.

Then choose the escalation category:

| Situation | Category | What to do |

|---|---|---|

| Reversible, contained, within your authority | Handle yourself | Make the call. Mention later only if useful. |

| Contained, low urgency, but useful for context | FYI only | Send a short note: “I’m handling this; no action needed.” |

| Ambiguous, moderate risk, you own the decision | Ask for advice | Bring the frame and ask for perspective, not permission. |

| Broad blast radius, irreversible, or authority gap | Escalate for decision | Name the decision, deadline, tradeoff, and consequence. |

| Urgent, high blast radius, active customer/legal/security/revenue risk | Escalate immediately | Interrupt the normal channel. Bad news should travel fast. |

This matrix prevents two common errors: asking permission for recoverable calls, and treating high-consequence decisions as if they are just another task.

What Escalating Too Little Looks Like

The under-escalator's pattern: handles things they shouldn't, gets caught in problems beyond their scope, surprises their manager with crises that developed slowly and were never flagged, and eventually loses trust because their manager can't see what's happening.

The cost: loss of trust (your manager stops trusting their own model of what you can handle), crises that could have been managed with early intervention become unavoidable, and your manager starts micromanaging to compensate.

The cure: build a better internal model of what "recoverable on my own" actually means. When in doubt, flag — briefly. "FYI, this came up. I'm handling it, but wanted you to know" takes 30 seconds and prevents surprise.