How to Discuss Burnout with Your Manager in English
Learn the English phrases for raising burnout with your manager professionally: naming the problem, being specific about causes, and proposing solutions.
Raising burnout with a manager in a non-native language adds a layer of difficulty on top of an already uncomfortable conversation — it’s easy to either understate the problem out of politeness or feel unable to articulate it precisely. This guide covers English phrasing that’s honest without being alarming, and specific enough that your manager can actually help.
Key Vocabulary
Naming the problem — stating directly that you’re experiencing burnout or unsustainable workload, rather than hinting at it through vague complaints, which managers can miss entirely. “I want to name this directly: I’ve been feeling burned out for the last few weeks, and I don’t think it’s going to resolve on its own.”
Specific contributing factor — a concrete cause of the burnout (on-call frequency, scope creep, understaffing) rather than a general statement like “I’m just tired,” which is harder to act on. “A specific contributing factor is the on-call rotation — I’ve been on-call three weeks out of the last six, which is more than double what the rotation is supposed to be.”
Impact statement — a description of how the burnout is affecting your work or wellbeing, making the cost concrete rather than abstract. “The impact is that I’m making more mistakes in code review than I used to, and I’m dreading Monday mornings in a way I didn’t a few months ago.”
Proposed adjustment — a concrete suggestion for what would help, offered by the employee rather than left entirely to the manager to guess. “One adjustment that would help is rebalancing the on-call rotation to include the two engineers who joined last quarter.”
Check-in cadence — an agreed-upon follow-up schedule to revisit whether the situation has improved, preventing the conversation from being a one-time event that gets forgotten. “Can we set a check-in cadence — maybe revisit this in three weeks — so we can see if the adjustment actually helped?”
Common Phrases
- “I want to raise something directly: I’ve been feeling burned out.”
- “A specific factor contributing to this is…”
- “The impact I’m noticing is…”
- “One thing that would help is…”
- “Could we check in again in a few weeks to see if this has improved?”
Example Sentences
Opening the conversation clearly: “I wanted to use some of this one-on-one to talk about how I’ve been feeling at work. I’ve been burned out for the past month or so, and I think it’s worth naming now rather than letting it build up further.”
Being specific about causes and impact: “The biggest factor has been the overlap between the migration project and the on-call rotation — I’ve effectively been working two jobs’ worth of context-switching, and it’s affecting my sleep and my focus during the day.”
Proposing a concrete adjustment: “What would help most right now is either extending the migration deadline by two weeks or pulling someone else in to share the on-call load. I don’t think I can sustain the current pace through the end of the project as it stands.”
Professional Tips
- Name the problem directly rather than hoping your manager infers it from indirect signals — burnout described vaguely (“I’m just a bit tired lately”) is easy for a busy manager to miss.
- Cite a specific contributing factor, ideally with a number (weeks on-call, hours of overtime, number of concurrent projects) — specificity makes the problem something a manager can actually act on.
- Include an impact statement connecting the burnout to concrete outcomes (quality, mood, sustainability) — it helps a manager understand urgency without you needing to overstate how you feel.
- Always propose an adjustment, even a partial one — coming with a suggestion, not just a complaint, shifts the conversation toward problem-solving and shows you’ve thought it through.
Practice Exercise
- Write a two-sentence opening statement naming burnout directly to a manager.
- Write one sentence citing a specific contributing factor with a concrete detail.
- Write a sentence proposing one concrete adjustment that would help.
Navigating Nuance: Specific Phrasing for Non-Native Speakers
Let’s be honest – discussing something as personal as burnout can feel incredibly vulnerable. It’s not just about stating you’re overwhelmed; it’s about framing that overwhelm in a way your manager understands and, crucially, will respond to constructively. For non-native English speakers, this requires careful attention to vocabulary and the subtle nuances of professional communication. Often, direct translations from your native language can fall flat or even be misinterpreted. The key is to move beyond simply saying “I am burnout” and instead focus on describing the experience and its impact.
Consider a scenario: you’ve been spending extra hours reviewing code – perhaps prompted by a comment in a pull request like, “This section needs significant refactoring; consider a more modular approach.” You’re feeling immense pressure to deliver quickly, juggling deadlines, and constantly battling imposter syndrome. A simple statement of “I am burnout” wouldn’t convey the depth of your struggle. Instead, try phrasing it as, “I appreciate your feedback on this section. I’ve been finding it challenging to manage the workload and maintain code quality with the current pace. Specifically, the increased review requests have added a significant amount of cognitive load, making it difficult to focus effectively and leading to some self-doubt about my ability to deliver consistently.” This demonstrates you’re acknowledging the feedback, explaining why you’re struggling, and highlighting the specific pressures contributing to your state.
Another common situation is communicating during Slack conversations. Let’s say a teammate sends a message: “Hey team, pushing out this PR – let me know if you have any questions!” Responding with just “No thanks” feels dismissive and doesn’t address the underlying issue. A more professional response might be, “Thanks for sharing! I’m currently prioritizing a few critical bugs and haven’t had time to thoroughly review yet. Could we schedule a quick 15-minute slot tomorrow morning to discuss it when my bandwidth is less constrained? I want to ensure I can provide valuable feedback.” Notice the polite request for a specific timeframe, acknowledging your limitations without directly stating “I’m overwhelmed.” Using phrases like “bandwidth constraints” – a common professional term – avoids a potentially awkward personal admission.
Finally, when documenting work in a pull request description, avoid vague statements. Instead of “This PR is complex,” try: “This PR incorporates several new features and refactors existing code to improve performance. Due to the increased complexity, I’ve focused heavily on unit testing and have spent additional time optimizing for efficiency. While I’m committed to delivering a high-quality product, I’ve noticed an increase in my workload recently, which has impacted my ability to maintain focus and deliver at my usual pace.” This demonstrates ownership of the work while subtly signaling you need support or adjustments. Remember, your goal isn’t to complain; it’s to collaboratively find a solution that benefits both you and the project.