How to talk to your manager about burnout (scripts that work)

If you've decided you need to talk to your manager about burnout, the conversation is going to go one of three ways. They'll respond well and something will change. They'll respond well and nothing will change. They'll respond poorly. The difference between outcomes one and two is almost entirely about how the conversation is structured. This piece is the structure that works.

Why the obvious approach fails

The obvious approach is to walk in and say 'I think I'm burning out.' This produces three predictable failures:

• Your manager hears it as a personal disclosure they don't know how to respond to.
• Your manager hears it as a request for time off, which they may or may not be able to grant.
• Your manager hears it as a performance issue ("are you saying you can't do your job?") and quietly downgrades you.

All three responses are bad outcomes from the same single ambiguous opening. The fix is to never have that conversation. Have a different one.

The reframe: renegotiation, not disclosure

The conversation that works treats burnout as a capacity-vs-demand mismatch you're noticing and trying to solve. You're not asking for sympathy or a leave. You're flagging an operational problem and proposing structure.

This works for four reasons. (1) It's the most accurate description of what's happening. (2) It puts you and your manager on the same side of the problem. (3) It gives the manager something concrete to act on. (4) It removes the implied performance question. You're not saying you can't do the work. You're saying the current load is unsustainable and we should fix it together.

The four-part script

Part 1: The signal

Lead with a specific behavioral observation, not a feeling. 'Feelings' get filed in the personal-disclosure bucket. 'Behavior' gets filed in the operations bucket.

I've noticed something I want to flag. Over the last six weeks, I've been working through most weekends and I've started missing details I wouldn't normally miss — three small mistakes on the X report and one on Y. That pattern is new for me and it tells me my current load isn't sustainable.

Why this works: it's specific, time-bounded, observable from outside, and uses the data the manager probably already has.

Part 2: The diagnosis

Name the structural cause, not the emotional one. 'I'm stressed' is true but useless. 'My workload is exceeding what's possible within my hours' is true AND actionable.

When I look at where my hours are going, it's about 60% on [project A], 25% on [project B], and 15% on [ongoing maintenance / meetings / 1:1s]. The math doesn't fit in a 40-hour week, so I've been backfilling with weekends, and the cost of that is starting to show up.

Why this works: it makes the constraint visible to the manager. If they didn't know how your hours were allocated, now they do. If they did know, you've just made it impossible for them to pretend they didn't.

Part 3: The ask

Bring three options. Not because you can't decide — because giving them options reduces the cost of saying yes.

I think there are three ways to fix this. One: we descope project B for this quarter. Two: we pull in [colleague] to take half of project A. Three: we agree explicitly that I won't do the [ongoing maintenance] work for the next 60 days. I'm open to any of these or a combination. What I'm not able to do is keep absorbing the gap.

Why this works: it's a renegotiation, not a complaint. It's a manager's job to make trade-offs. You're handing them a clean menu.

Part 4: The commitment

Close by committing to your half of the deal.

If we make one of those changes, I'll commit to not working weekends for the next 30 days, and I'll re-check at the end of that window to see if it's working.

Why this works: you've turned the conversation into a 30-day experiment with measurable terms. That's the kind of thing managers are good at saying yes to.

What to do if the conversation goes badly

Sometimes you do this exactly right and the response is still inadequate. Your manager either can't or won't help. In that case the question is: is this manager the problem, or is the system the problem?

If it's the manager: escalate to skip-level. The same script works. You're not complaining about your manager — you're flagging a capacity problem your immediate manager couldn't solve.

If it's the system: the situation calls for different decisions than a script can give you. At minimum, document what you tried so the next conversation (with HR, with your skip-level, or eventually with your next employer) has receipts.

What to do before the conversation

Take the BurnoutIQ assessment if you haven't already. Ten minutes, free. It will give you specific dimension scores and an archetype name — which is much more useful than a vague 'I think I'm burning out' for both you and your manager. If the assessment shows you're in the Volatile, Stranded, or Smoldering archetypes, the right move may be a clinical conversation before the manager conversation, not after.