Managing up a difficult executive: a step-by-step playbook with scripts

60-Second Summary

‘Difficult’ is not a diagnosis. Name the pattern: volatile, absent, controlling, indecisive, or credit-taking. Each gets a different playbook.
The upward contract is the single highest-leverage move — written, 1 page, covers decision rights, comms cadence, escalation, and what good looks like in 90 days.
Most managers ‘manage up’ by absorbing chaos silently. That trains the executive to keep doing it. Reflect the cost back, in writing, with numbers.
Have a private exit threshold — written, dated, shared with one person outside the company. Without one, you’ll rationalize indefinitely.

‘My boss is difficult’ is a feeling. A playbook needs a diagnosis. The five patterns below cover ~90% of difficult-executive situations and each has a specific counter-move.

Step 1 — Name the pattern

Pattern	Tell	What they fear	What works
Volatile	Tone shifts week to week; you brace before meetings	Loss of control under uncertainty	Predictability — same agenda, same artifact, same time
Absent	No response for days; decisions made without you	Being seen as a bottleneck	Async decision memos with a default if no response by X
Controlling	Rewrites your work; CCs your team without you	Being blamed for your team’s mistakes	Pre-share drafts; invite editing before the meeting
Indecisive	Asks for ‘more data’; reverses decisions	Being wrong publicly	Force a tiny reversible decision; build evidence of safety
Credit-taking	Uses ‘I’ for your team’s wins; ‘they’ for losses	Status anxiety vs peers	Make contribution legible in artifacts; write the email yourself

Step 2 — Build the upward contract

Most manager–executive friction is unwritten expectations. Fix that first. One page. Co-authored. Reviewed every 90 days.

Decision rights — what I decide alone, what I tell you about, what I ask you about, what you decide.
Comms cadence — weekly 1:1 day/time, weekly written update format, escalation channel for urgent items.
What good looks like in 90 days — 3–5 outcomes, not activities.
What I need from you — specific behaviors, not adjectives. (‘Reply to escalation Slacks within 4 business hours’ — not ‘be responsive.’)
How we’ll renegotiate — a date and a trigger.

Script — proposing the contract

‘I want us to be a great team and I think we’re leaving leverage on the table because we haven’t written down a few things. I drafted a one-pager — decision rights, cadence, what good looks like, what I need from you. Could we spend 30 minutes on it Thursday? You’ll edit it freely; I just want one version we both refer back to.’

Step 3 — Run the weekly upward 1:1

30-minute upward 1:1 — same agenda every week

1
1. Headlines (3 min)
3 bullets: green, yellow, red. No surprises ever land outside this slot.
2
2. Decisions you need (10 min)
Each as: context (2 sentences) / options / my recommendation / what I need from you. Default action if no decision.
3
3. Heads-up (5 min)
Things that will hit their inbox from elsewhere. Pre-empt surprise.
4
4. Their agenda (10 min)
Their turn. Listen. Take notes visibly.
5
5. Recap (2 min)
Decisions made + owners + dates. Send in writing within 1 hour.

Step 4 — Reflect the cost back

Silent absorption trains bad behavior. Reflect the cost with numbers, not adjectives, and in writing.

Script — reflecting cost

‘Three things this week I want to flag — not as complaints, as data so we can adjust. (1) The Tuesday reversal on [project] cost the team ~18 engineer-hours of rework. (2) The Slack at 11pm Friday triggered weekend work for 4 people. (3) Two engineers asked me in 1:1s whether the priority is real. I’m not asking you to change today — I’m asking us to look at this pattern in our next contract review. What am I missing?’

Step 5 — Protect the team without lying

Do not pretend the executive is fine. Your team can tell, and lying about it makes you untrustworthy. Do not trash them either — your team will assume you’ll do the same about them.

The honest middle

‘I know the reversal yesterday was frustrating. Here’s what I know about why it happened and here’s what I’m doing upstream so it happens less. I won’t promise it won’t happen again — I will promise that when it does, you’ll hear it from me first, with a reason.’

Step 6 — Set your exit threshold

Without a written threshold you will rationalize indefinitely. Write it down — date it — share it with one trusted person outside the company so you can’t edit it secretly.

Behavioral threshold: ‘If [specific behavior] happens N more times in 90 days, I start interviewing.’
Outcome threshold: ‘If [team metric] doesn’t move by X in 6 months, I leave.’
Health threshold: ‘If I’m still waking at 4am thinking about this in 60 days, I leave.’

Scripts by pattern

Volatile

‘I’ve noticed our conversations land differently depending on the week. To give you my best work I need a predictable channel. Can we commit to the same Tuesday slot, same one-pager format, and route anything urgent to [channel] in between? I’ll stop guessing which mode you’re in and you’ll get cleaner asks from me.’

Absent

‘I’m going to start sending you decision memos with a default action and a deadline — typically 48 hours. If I don’t hear from you, I’ll proceed with the default. That keeps me unblocked and you in the loop. Push back any time and I’ll reverse. Sound fair?’

Controlling

‘I think we can save you time. I’ll share drafts on Monday for anything going out Thursday. You edit directly. By Wednesday it’s yours-and-mine. That way nothing surprises you on Thursday and I don’t spend Friday redoing what you’d have written differently.’

Indecisive

‘This decision is reversible inside 30 days at low cost. I’d like to ship the smaller version Friday and re-evaluate at month-end. If it’s wrong, we revert — I’ll own the call. If it’s right, we’ve learned faster than another round of analysis would have told us.’

Credit-taking

‘Hey — small thing. The board update went out with [project] under your name. The team worked nights on it and noticed. Going forward, can we agree that contributor names appear in the update appendix? I’ll draft it that way by default and you can cut if needed.’

Written by Pawan Joshi.Sources cited inline.

First published 15 Jun 2026See site changelog →