Back to Scenarios
SCN-01Wellbeing

An engineer tells you they're burnt out

A trusted engineer says, quietly or directly, that they're running on empty. How you respond in the next 15 minutes shapes whether they recover here or leave.

Share

The signal

They told you in a 1:1, on Slack, or after a release. Tone matters more than the words — flat affect, exhaustion, or unusual irritability are the real data.

What it really means

Burnout is rarely about volume alone. It's the combination of sustained pressure, low agency, ambiguous priorities, and the feeling that the work no longer matters. By the time someone names it, they've been holding it for weeks.

Your first response

Stop the agenda. Close the laptop. Say thank you for telling me. Do not problem-solve in the first conversation — listen, validate, and buy time to act.

The Playbook

1. In the moment: listen, don't fix

Your first job is to make it safe to have said it. Acknowledge the courage it took. Ask open questions and let silence do work.

  • Reflect back what you heard before responding.
  • Ask: What does a good week look like right now? What does a bad one look like?
  • Resist the urge to immediately offer time off — it can feel dismissive.

2. Within 48 hours: reduce load visibly

Burnout deepens when nothing changes after disclosure. Make a concrete, visible reduction this week.

  • Cut on-call rotation, drop a project, or hand off the riskiest deliverable.
  • Take one recurring meeting off their calendar permanently.
  • Protect deep-work time and remove ambiguous expectations.

3. Within two weeks: address the source

If the cause was structural — understaffing, unclear ownership, a thrashing roadmap — the team will burn out next. Fix the system, not just the symptom.

  • Audit their last 8 weeks of work. What was avoidable load?
  • Talk to HR or People Ops about formal leave, EAP, or medical support.
  • Re-scope their next quarter with them, not for them.

4. Long term: rebuild agency

Recovery isn't rest alone — it's regaining control. Give them ownership of something meaningful and small enough to win at.

Things you can actually say

Opening the conversation
Thank you for telling me. That took trust, and I want to honor it. Before we talk about what to do, I want to make sure I actually understand what the last few months have felt like for you. Can you walk me through it?
When they downplay it
I hear you saying it's manageable. I also notice you've shipped through three incidents and a re-org. I'd rather we act early than wait until you're forced to. What's one thing I can take off your plate this week?
Offering leave
If you need formal time off — a week, a month, longer — that is fully available and I will protect your role and projects. This isn't a favor. It's part of the job working the way it should.

What to avoid

  • Treating it as a performance problem or a confidence issue.
  • Promising changes you can't actually deliver ("we'll hire someone soon").
  • Sharing the disclosure with peers or skip-levels without explicit consent.
  • Booking a follow-up 4 weeks out and considering it handled.

The follow-through

  • Confirm changes in writing within 24 hours so they don't carry the memory load.
  • Check in weekly — short, low-pressure — for the next 6 weeks.
  • Track whether the load actually came down. Calendars and PR counts don't lie.

Leadership in your inbox.

Leadership lessons, frameworks, and field notes for modern engineering teams. No motivational fluff.

Trouble seeing the form?Subscribe on Beehiiv instead

Free. One email a week. Unsubscribe anytime.