escalate-with-a-recommendation

Escalate with a recommendation

Principle: When you must escalate to the manager, always escalate with a recommendation. Never escalate raw — "this came in, what do you want me to do?" is a failure mode. The minimum viable escalation is "X happened, I recommend Y because Z, default action in 24h is W".

Why it matters: Bare escalations push the cognitive load back to the manager — they must read the situation, derive options, weigh them, and decide. A recommended escalation only requires them to weigh your option against their own judgement; if your option is reasonable, they confirm in 5 seconds. If not, they course-correct, which is faster than starting from scratch.

How to apply:

• The escalation template: "Situation: <2 sentences>. Recommendation: <1 sentence>. Why: <1 sentence>. If I don't hear from you by , I'll ."
• The "default if I don't hear back" clause matters. Silence is a common manager response; without a default, the situation rots. With a default, silence becomes implicit approval of your recommendation.
• Calibrate the default to be the safe-reversible move. Accepting a meeting can be reversed by declining later. Spending €5,000 cannot. When the action is hard to reverse, the default must be "do nothing and wait".
• One recommendation, not three. If you have three options, pick one and mention the alternatives in a single phrase: "I'd accept (vs. decline or counter-propose Friday)". The shortlist signals you thought it through; the pick saves the manager from optimizing it.
• After the manager decides, record the decision and your prediction. "Manager chose decline; I had recommended accept." That feedback loop is how the next similar escalation gets a better recommendation.