If you are in immediate crisis or thinking about harming yourself, this article is not the right resource right now. In the United States, call or text 988 to reach the Suicide and Crisis Lifeline (free, confidential, 24/7). Outside the US, the International Association for Suicide Prevention maintains a list of crisis lines at iasp.info/resources/Crisis_Centres. If your employer offers an Employee Assistance Program (EAP), the number is usually on the back of your health insurance card or in your benefits portal. EAP calls are confidential and free.
The first time I tried to tell my boss I was burning out, I ruined the conversation in the first sentence. I sat down, took a breath, and said: “I think I might be overwhelmed lately and I wanted to flag it.” She nodded sympathetically. She asked if I needed to take a day. She told me to let her know if it got worse. Twenty-five minutes later I walked out of her office with nothing actually different about my workload, my deadlines, or her expectations of me. Two months later I quit.
The mistake I made in that conversation is the mistake almost every manager I have coached on burnout has made: I framed it as a personal weakness I was asking permission to feel, instead of a system problem I was reporting up. The conversation I had was structurally designed to produce no change. The script below is the conversation I should have had.
This article is one cluster under the Stress & Wellbeing hub. The diagnostic foundation lives in manager burnout signs — if you are not sure whether what you are feeling is burnout or just a hard quarter, start there. If you suspect burnout is already shaping your decisions, the Are You Burning Out? free assessment takes about four minutes and gives you a five-dimension read on where the load is heaviest. This article assumes the diagnostic is done and the conversation needs to happen.
Why most “I’m burning out” conversations fail
Three patterns, in order of how often they show up. If your last attempt to surface burnout produced no real change, the version below almost certainly contained at least two of these.
1. The conversation is framed as asking permission instead of reporting a problem. “I think I might be overwhelmed” is a request for validation. “I am working sixty-five hours a week and the math on the next quarter does not work” is a report. Managers respond to reports because they can act on them. Managers respond to requests for validation by validating, which feels caring and produces zero structural change. The frame is the first thing the manager hears, and the frame determines what conversation they think they are in.
2. The conversation describes a feeling without describing the system. “I’m exhausted.” “I’m stressed.” “I’m not sleeping well.” These statements are true and they are also operationally useless to a manager. Without specific load numbers, specific deadlines that conflict, specific decisions that have been pushed onto you, the manager has nothing to work with except sympathy. Sympathy without action is the standard outcome of every burnout conversation that fails. Both of you walk out feeling like something happened. Nothing happened.
3. The conversation does not contain a specific ask. Most people raise the burnout and stop. The manager fills the silence with whatever feels supportive in the moment — usually “take a day,” “let me know if it gets worse,” or a vague promise to “look at your workload.” None of these are actions. Without a specific ask from you, the conversation produces whatever drift the manager defaults to, which is almost always nothing. The ask is not optional. The ask is the conversation.
The seven building blocks below assume you have done the work to fix all three. If you have not, the most polished script will still leave you where you started.
What a conversation that lands actually does
Four conditions, in order. The seven blocks below are structured around them.
- It opens with a system frame, not a feelings frame. The first sentence sets what conversation you are in. If the first sentence is about how you feel, you have entered the sympathy track and it is very hard to switch. If the first sentence is about the system you are inside, the conversation moves toward operational adjustment from the start.
- It contains specific, citeable data. Hours per week. Number of concurrent projects. Number of escalations carried personally. Sleep hours. Whatever the data is, it is specific and quantified. “I am tired” produces nothing. “Forty hours of meetings on a week with three Friday deadlines” produces a calendar audit.
- It contains a specific ask. Not “support.” Not “help.” A specific reallocation, a specific deprioritization, a specific change to the next two weeks that you have already thought through and are proposing. The manager’s job becomes evaluating your proposal, not generating one from scratch.
- It contains a stated contingency. What happens if nothing changes. You are not threatening. You are stating the math. If the conditions stay the same, X will happen by Y date. The contingency is what turns the conversation from advisory into operational.
When all four are present, the conversation lands. When any one is missing, it leaks. The seven blocks below are organized around these four.
The seven building blocks of the conversation
Each block follows the same format: what the block does in the conversation, the version most people default to, the version that actually moves something, and what makes the second land.
Block 1: The opening line
What it does. Sets the frame. The first ten seconds determine whether you are in a sympathy conversation or an operational one. Almost impossible to recover the frame later.
Bad version:
“Hey, do you have a few minutes? I wanted to talk to you about how I have been feeling lately.”
Good version:
“I want to walk you through some load numbers I have been tracking on my work. The trajectory is not sustainable and I want us to look at the next two weeks together.”
Why it works. The second version puts the manager into a problem-solving posture from sentence one. “Load numbers I have been tracking” is operational. “The next two weeks” is concrete and short-horizon, which is the timeframe a manager can actually act on. “Together” makes it a joint problem, not a request for them to fix you.
Block 2: The specific data
What it does. Replaces vague feeling-language with citeable numbers. Gives the manager something concrete to work with.
Bad version:
“I have just been so swamped lately. There is so much going on. I feel like I am drowning.”
Good version:
“Over the last six weeks I have averaged sixty-three hours per week tracked, with three weeks above seventy. I am currently carrying four concurrent projects with overlapping critical paths in the next ten days: the Q3 plan, the launch readiness review, the vendor escalation, and the headcount paperwork. The escalation alone has been four hours a day for two weeks.”
Why it works. Three different numerical anchors (hours per week, project count, hours per day on one issue). Each one is verifiable. Each one is something the manager can either dispute or accept and act on. You moved from “I feel” to “here is the data.” That changes the conversation.
If you have not been tracking hours, start now. Two weeks of rough tracking is enough to ground the conversation. If you are uncomfortable with the precision, use a range (“between sixty and sixty-five hours”) rather than abandoning the number entirely. A range is still operational. “A lot” is not.
Block 3: The reframe to system
What it does. Names the gap as a structural mismatch between commitments and capacity, not a personal failing. Removes the implicit moral judgment (“I am not strong enough”) from the conversation.
Bad version:
“I do not know if I am cut out for this. Maybe I am just not handling it well. I feel like I should be able to manage this.”
Good version:
“The shape of the work over the last quarter is that the original plan assumed three concurrent projects, and we have been running at five since March. The work expanded; the capacity did not. I do not think that is sustainable for anyone in this role, and I am the one in it right now, so I am surfacing it.”
Why it works. “Anyone in this role” depersonalizes. The manager hears: this is a structural issue I would have whoever sat in this seat. That removes the conversation from the “is this person tough enough” track and puts it in the “is the role designed correctly” track. The second is where useful adjustments happen.
This reframe is the single most important move in the conversation. If the manager hears “I am not handling this,” they cannot help without making it about you. If they hear “the system is overloaded and I am inside it,” they can adjust the system without anyone losing face.
Block 4: The ask
What it does. Converts the conversation from advisory to operational. The manager evaluates a proposal instead of generating one.
Bad version:
“I just need some support. I do not know what would help, honestly. Maybe we could figure something out?”
Good version:
“Three asks I have already thought through. First, I want to deprioritize the vendor escalation for the next two weeks and have Priya hold the relationship through the immediate fire — she has more bandwidth right now and the customer knows her. Second, I want to push the Q3 plan first draft from Friday to the following Wednesday. Third, I want to skip the next two leadership stand-ups; I can read the notes. If those three move, the next two weeks become workable.”
Why it works. Three specific, bounded, time-limited asks. Each one names a person or a decision, not a vague category. Each one has a duration (“next two weeks,” “until the immediate fire is held”). The manager’s response narrows to yes, no, or counter-proposal on each item — all three of which are operational responses. The “no” responses are also useful, because they surface which constraints are real and which are flexible.
The number three is deliberate. One ask sounds like a small adjustment. Five sounds like a list of complaints. Three sounds like a plan.
Block 5: The contingency
What it does. States what happens if nothing changes. Converts the conversation from optional to consequential, without threatening.
Bad version:
“I just do not know how much longer I can keep this up.”
Good version:
“If the load stays where it is for another four to six weeks, my read is that something will fail. Most likely the Q3 plan will go out half-baked, the vendor escalation will require me to bring in an outside firm at expense we have not budgeted, or my own health will force a multi-week leave. I cannot predict which one breaks first. I am telling you so that the timing of which thing fails is a decision we make, not one that happens to us.”
Why it works. Three specific failure modes, each tied to a piece of business the manager cares about. The frame is “we are choosing what fails” rather than “I am threatening to quit.” Operationally these are the same outcomes; emotionally they are completely different. The first invites planning. The second invites defense.
Do not deliver the contingency as a threat or an ultimatum. Deliver it the way you would deliver any risk in a project review: this is the projection if the inputs stay constant. The flatter your tone, the more weight the projection carries.
Block 6: The close
What it does. Ends the conversation with a concrete next step on the calendar. Without this, even a productive conversation produces no action.
Bad version:
“Anyway, I just wanted to flag it. Let me know what you think. Thanks for listening.”
Good version:
“I would like to leave this conversation with three specific decisions on the three asks, and a fifteen-minute check-in on Friday to see how the first week is landing. Can we make those decisions now, or do you need to come back to me by end of day tomorrow?”
Why it works. You have not handed the conversation back to the manager to do whatever they want with it. You have offered two specific paths — decide now, or decide by a stated deadline. Either path closes the loop. Either path produces a calendar item by tomorrow.
The Friday check-in is critical. It converts a one-time conversation into a system. Without it, even agreed changes drift back to the prior state within ten days. With it, the manager has a calendar event reminding them that the conditions of the conversation are still in effect.
Block 7: The follow-up email
What it does. Documents what was agreed, sent within twenty-four hours, in writing. Creates the paper trail that prevents the conversation from quietly dissolving over the following week.
Bad version (no email).
Good version (sent same day or next morning, before nine AM):
Subject: Recap of our 1-on-1 today — workload adjustment
Hi [Manager],
Thanks for the conversation today. To make sure we are aligned, here is what I understood we agreed:
- Vendor escalation hands off to Priya for the next two weeks, starting tomorrow. I will introduce her to the customer contact today.
- Q3 plan first draft moves from Friday to Wednesday the 27th.
- I will skip the next two leadership stand-ups and read the notes instead.
- We have a fifteen-minute check-in scheduled for Friday at 3pm to assess.
If I got any of this wrong, let me know by end of day tomorrow so we can correct.
[Your name]
Why it works. Three things happen at once. First, you have written documentation of an operational agreement, which protects both of you. Second, you have offered the manager a clean low-friction way to correct anything they did not mean to commit to — which makes them more likely to leave the agreement intact. Third, you have signaled that you treat this conversation as a real operational change, not as a vent, which makes the manager more likely to do the same.
If you do not get a response to the email within twenty-four hours, send one follow-up: “Just confirming my read on the above so I can act on it today.” The silence-then-prompt is itself a useful signal — if the manager is uncomfortable confirming in writing what they agreed to in person, the agreement was not as solid as it felt, and you need to know that before you have built your week around it.
What to do if the response goes sideways
Four common failure modes, with what each one means and what to do next.
The dismissal. “Everyone is stretched right now. Welcome to management.” Translation: the manager either does not believe the load is genuinely unsustainable, or they do believe it and do not have a way to fix it. Your move: pin them to the specific data. “I want to make sure I am not over-reading my own situation. Can we look at the hours and the project list together for ten minutes so we are calibrated?” If they still dismiss after seeing the numbers, you have learned something important about whether this is a manager who will protect you. Plan accordingly.
The weaponization. “I am surprised to hear this. Most people in your role manage just fine. Are you sure you are in the right job?” Translation: the manager is using your honesty against you to question your fit. This is a serious signal about the relationship and the culture. Your move: do not defend yourself in the moment, do not retract. End the conversation politely: “I think we should pause here and pick this up tomorrow when we both have had time to sit with it.” Then send the follow-up email anyway, documenting what you raised and what their response was. Start documenting privately what is happening. Consider whether HR, skip-level, or your network needs to be a parallel conversation. This is no longer about workload. It is about whether the role is survivable.
The sympathy without action. “I really hear you. That sounds so hard. Take whatever time you need.” Translation: the manager cares about you as a person but is not going to change anything operationally. Your move: redirect to the specific asks. “I appreciate that. I also want to make sure we land on the three operational changes I mentioned, so I can act on them tomorrow. Can we walk through them now?” If you cannot convert sympathy into operational change in the same conversation, send the follow-up email anyway with the asks explicit, and request a written response. If the email stays unanswered, the asks did not happen. Plan for the original load to continue.
The blame redirect. “Have you thought about how you are managing your time? Maybe we should talk about your prioritization.” Translation: the manager is reframing your structural problem as a personal performance issue, possibly because they do not know how to fix the structure. Your move: do not get pulled into defending your prioritization in the moment. “I am genuinely open to that conversation as a separate one. For today, I want to focus on the load numbers and the next two weeks. Can we keep those separate for now?” If the manager refuses to separate them, you have learned that the only way for this conversation to land is for you to accept the framing that the problem is your performance. That is information about whether to stay.
For any of the four failure modes, the pillar guide on managing up as a new manager covers the broader patterns for difficult conversations with a boss who is not making it easy.
The discipline most people skip: tracking the conditions
The conversation is one event. The conditions it was supposed to change persist over weeks. Most people have the conversation, feel temporary relief, and then watch the load creep back to the prior state within ten to fourteen days. Then they conclude the conversation did not work, which is not exactly right. The conversation worked; the follow-through did not exist.
The fix is to keep tracking the same numbers after the conversation as you tracked before it. Hours per week. Project count. The specific items you agreed to deprioritize. Two minutes a day to update the log. After the first month, you have data to answer three questions:
- Did the agreed changes actually happen?
- Did the conditions stabilize, or did they drift?
- Is this a manager who can protect your bandwidth, or is the protection only verbal?
The answers to those three questions determine your next move. If the changes happened and the conditions stabilized, you have a manager who can adjust the system, which is the most valuable kind. If the changes did not happen and the conditions drifted, you have a manager who is sympathetic but not operationally protective, which is the most common pattern, and the decisions about whether to stay shift accordingly.
For a sense of what the avoidance of this conversation has already cost, the Conversation Delay Cost calculator puts numbers on the four invisible bills the silence is running. Most managers underestimate the bill by a factor of five.
Before you have the conversation, three things to do
Take the Are You Burning Out? assessment if you have not already. Four minutes. Five dimensions (Emotional Drain, Cynicism, Overload, Identity Erosion, Physical Warning Signs). The dimension that scores hardest tells you which specific data to bring into the conversation. Different scores need different conversations.
Read the manager burnout signs guide and the manager burnout prevention guide if you are unsure whether what you are experiencing is burnout, a hard quarter, or something the conversation cannot solve. Different conditions need different responses. Some of what feels like burnout is recoverable with two weeks of conditions changing; some of what feels like burnout has been building for nine months and the conversation is one step among several.
Use your Employee Assistance Program if your employer offers one. EAP calls are free, confidential, and do not appear in any record your employer sees. The benefits portal or the back of your insurance card has the number. EAP counselors are not your therapist for the long term; they are a low-friction starting point that often includes three to eight free sessions with a professional, plus referrals if you need more. The conversation with your boss is one move. The conversation with a professional is a different move. You can run both in parallel.
Frequently asked questions
Is “burning out” a phrase I should actually use in the conversation?
It depends on your read of the manager. With a manager who treats burnout as a real, named operational condition, the word lands as honest naming. With a manager who treats burnout as a soft excuse or a personal weakness, the word activates dismissive responses before you have gotten to the data. If you are not sure, you can run the entire conversation with the word “load” or “capacity” or “sustainability” doing the work the word “burnout” would have done. The structural content is the same. The reception is sometimes better.
How specific should the data be? Should I bring a spreadsheet to the meeting?
Specific enough to ground the conversation; not so dense that the manager spends the meeting reading instead of talking. A one-page summary works: hours per week (last six weeks), project count, the two or three specific overlaps that are creating the crunch, your asks. If the manager wants more detail, you have it ready. If they do not, you have not made the conversation about the artifact.
What if my manager IS the source of the burnout?
Then this conversation cannot be the only conversation, and the pillar guide on managing up is the more relevant starting point. The script above still works for surfacing the conditions, but the structural fix probably involves skip-level, HR, or a change in role. Plan accordingly. Do not have the conversation expecting it to be the whole solution if your manager is the issue.
What if I am the manager who burned out, and my reports also need things from me right now?
You do both, in this order. First, you surface upward using the conversation above — your capacity to support your reports depends on whether your own load is sustainable, and your manager needs to know that. Second, you tell your reports what is and is not realistic from you for the next two weeks, specifically. “I am going to be slower on email responses than usual. The Friday 1-on-1s stay on the calendar. The strategic project I owe you is moving by a week.” This is not weakness; it is operational honesty, and your team needs it to plan. The shorter and more specific you are, the less anxiety it produces for them.
How do I bring up burnout if my company culture treats it as a stigma?
Drop the word “burnout” entirely. Use “workload sustainability,” “capacity mismatch,” “operational load,” or “the math on the next quarter.” The structural content of the conversation is the same. The frame is technical rather than personal. Some workplaces respond to technical framing where they would have dismissed personal framing. This is a workaround for culture, not a fix for culture, but it makes the conversation more likely to land in the meantime.
Should I have this conversation before or after I have started talking to other companies?
Whichever is true is what you say. If you have started looking and have not yet had this conversation, the conversation is most likely to produce real change because the contingency is concrete. If you have not started looking, the conversation is still worth having, because the answer determines whether you should. What you should not do is have the conversation pretending you have not started looking when you have; experienced managers can usually tell, and the trust cost is high.
What if the conversation works in the moment and then nothing actually changes?
Within ten days, send a calm written check-in. “Following up on the workload conversation we had on the 19th. The three items we agreed on were [X, Y, Z]. My read on this week is that one of them has happened, one has partially happened, and one has not. Can we sync for fifteen minutes on Friday to recalibrate?” If you get drift twice in a row after raising it twice in writing, you have your answer about whether the manager is operationally able to protect you. Plan for the role to continue as it was.
Am I allowed to take medical leave for burnout?
In some jurisdictions yes, in some no, depending on whether your local law recognizes burnout as a qualifying condition (the WHO classified burnout as an “occupational phenomenon” in ICD-11 but not as a medical diagnosis). The practical path in the US is to talk to your physician, who can write the relevant documentation under broader categories (anxiety, depression, adjustment disorder) that are covered by FMLA-eligible employers. This is not legal or medical advice. The point of this article is to help you have the conversation with your manager. If you are getting close to needing leave, the conversation with a physician and the EAP is the parallel track you should be running.
What to do next
Three concrete moves, in order. None of them is “buy something.”
- Take the Are You Burning Out? free assessment if you have not. Four minutes. The dimension that scores hardest tells you which specific data to bring into the conversation. Different scores need different first sentences.
- Pick a calendar slot in the next seven days for the conversation, and put it on the calendar before you talk yourself out of it. Use the language above to title it: “Workload sustainability check-in.” Make it a thirty-minute meeting, not a fifteen. Block the thirty minutes before the meeting on your own calendar to prep — write your numbers, your asks, your contingency on one page so you are not assembling them in real time.
- If you are unsure whether the conversation is the right next move, call your EAP first. Free, confidential, no record. They will help you decide whether the conversation, a different conversation, or a different path entirely is where to spend the next move. Starting there is not weakness; starting there is operational. The conversation with your boss lands better when you have already had the conversation with someone whose only job is to help you think clearly.
If your situation is urgent and the timeline is “this week, I cannot do another week of this,” the assessment and the EAP are not slow steps. They take less than thirty minutes between them and they give you better information for the conversation than another week of pushing through would. The decision to wait until you have a better baseline is the operational decision, not the avoidant one.