It’s November. Daylight Savings Time just stole an hour of sunlight from our lives, reminding us daily that darkness falls at 4:47 PM for no good reason. Your team is running on fumes, caffeine, and spite. And somehow, everyone decided that projects absolutely must launch before the holiday break because apparently, January doesn’t exist.
As a project manager who has personally experienced every stage of burnout (including the one where you consider becoming a goat farmer), I’m here to tell you: We need to talk about what’s really happening to your team right now.
The Perfect Storm: Why November is Project Management Hell
Let’s set the scene. Daylight Savings Time ended, which means everyone on your team is:
- Biologically confused about what time it is
- Leaving work when it’s already dark (hello, seasonal depression)
- Somehow both gaining and losing sleep simultaneously
- Questioning why we still do this time-change nonsense in 2025
Add to that:
- Q4 deadlines that were “definitely doable” in July
- Year-end reviews looming like dark clouds
- Holiday planning that’s stressing everyone out
- The realization that 2025 is almost over and half your goals aren’t done
- Election aftermath (because November 2024 was A LOT and people are still processing)
- The general existential dread that comes with November
And you, dear project manager, are supposed to keep everything on track while your team members are barely keeping themselves together.
No pressure.
Reading the Signs: When Your Team is Actually Burning Out
Here’s the thing they don’t teach you in PMP certification: Your Gantt chart doesn’t include a row for “team completely falls apart.” But you need to recognize the signs before your star developer decides that living in a van and selling homemade soap sounds more appealing than one more sprint planning meeting.
Early warning signs:
- Increased typos in Slack (the engineer who never makes mistakes just wrote “I’ll get that done tomorwo”)
- Longer response times to messages
- Cameras off in every single meeting
- That usually chipper team member who now responds to everything with “fine” or “whatever works”
- People working at weird hours (3 AM commits are not a flex, Sarah)
- Increased sick days
- Jokes about burning it all down (ha ha, but seriously, check on them)
Critical warning signs:
- Openly crying in meetings
- Total silence where there used to be debate
- Missing deadlines from people who never miss deadlines
- Rage-filled messages followed by “sorry, didn’t mean that”
- Someone asking if their role could be “less customer-facing” when they’re a backend developer
- The phrase “I don’t even care anymore” uttered without irony
If you’re seeing critical signs, we’ve moved past prevention into crisis management. Time to pull the emergency brake on some things, and yes, that’s going to be uncomfortable.
The Uncomfortable Truth: You Can’t Project-Manage Your Way Out of Burnout
I know. I KNOW. You want to solve this with better processes, clearer communication, and maybe a really good Trello board. Trust me, I’ve tried. I once color-coded a burnout prevention plan. It was beautiful. It was useless.
Here’s what actually causes team burnout:
- Too much work for too few people (no amount of agile methodology fixes this)
- Unrealistic deadlines that everyone knew were unrealistic from day one
- Constant context-switching between seventeen different priorities
- Leaders who say “work-life balance” but expect responses at 9 PM
- Zero psychological safety to say “this isn’t sustainable”
- The belief that everyone is replaceable (spoiler: they’re not, and good luck hiring in Q4)
And here’s the hard part: As a project manager, you probably can’t fix the root causes. You can’t magically create more people or more time. You can’t make executives suddenly understand technical complexity. You can’t change the fact that American corporate culture treats burnout like a badge of honor.
But you can change how you manage your projects and your team. And that actually matters more than you think.
The Triage: What Actually Needs to Happen Before Year-End
Sit down with your project plans. Now be brutally honest. What genuinely, actually, truly must launch before January? Not what people want. Not what would be nice. Not what someone promised before understanding the scope.
What will cause actual business harm if it doesn’t happen?
That list is probably much shorter than your current project roster. Maybe it’s the client deliverable with contractual penalties. Maybe it’s the compliance requirement with regulatory deadlines. Maybe it’s the revenue-critical feature that sales is literally waiting on to close deals.
Everything else? It can wait. Yes, even that thing the VP promised. Yes, even the initiative that’s “already been delayed twice.” Yes, even the project you personally really want to finish.
Call a meeting with your stakeholders. This will be unpleasant. They will push back. They will insist their project is the critical one. They will suggest the team “just work a little harder.”
Here’s your script:
“We have X capacity. We have Y projects. These projects are at risk of failure or significant quality issues because the team is beyond capacity. I need to prioritize Z projects for completion this year. Everything else will be scheduled for Q1. I’m happy to discuss which projects those should be, but I’m not open to discussing whether we need to reduce the workload. We do.”
Stand firm. Your job is to deliver successful projects, not to kill your team trying to deliver impossible commitments.
The Reset: Giving Your Team Permission to Be Human
Here’s a radical idea: What if you acknowledged that your team members are actual humans experiencing November in all its darkness and deadline-filled glory?
Things to actually say in your next team meeting:
“Hey everyone. November is rough. Daylight Savings Time is rough. Year-end pressure is rough. If you’re struggling, you’re not alone and you’re not failing. Let’s talk about what we can adjust.”
“I need you to tell me if you’re overloaded. I can’t fix it if I don’t know about it, and I promise there won’t be consequences for being honest about capacity.”
“We’re moving three projects to Q1. I know some of you were working on those. This isn’t about your performance. This is about setting realistic expectations.”
“If you need to take time off, take it. I’d rather you take a day now than burn out completely in two weeks.”
Things to stop saying:
“I know everyone’s busy, but…” (The “but” negates everything before it)
“We just need to push through these next few weeks.” (It’s never just a few weeks)
“This is our busy season.” (Every season is busy season now)
“At least we have jobs.” (Not a helpful perspective when someone is drowning)
“Work smarter, not harder.” (Cool, thanks, everyone is cured now)
The Practical Stuff: Actual Tactics That Help
Okay, enough philosophy. Let’s talk concrete actions.
Reduce meetings immediately. Look at your calendar. Cancel at least 30% of recurring meetings. Make the rest shorter. Nobody needs an hour to accomplish what could happen in 30 minutes. Your team needs time to actually work, and surprising news: meetings aren’t work.
Implement “No Meeting Fridays” or at least “No Meeting Afternoons.” Give people blocks of time where they can focus without interruption. Protect this time ferociously.
Stop requiring cameras on. If someone wants to attend a meeting in their pajamas with their camera off because they’re barely holding it together, that’s fine. You need their brain, not their face.
Create slack in your timeline. And I don’t mean the messaging app. I mean actual buffer time. If a task will take three days, schedule four. When (not if) something goes wrong, you have room to absorb it.
Rotate who takes on the urgent requests. Don’t let the same reliable people become the dumping ground for every fire drill. Distribute the pain equitably.
Celebrate small wins. Your team needs evidence that progress is happening. When something ships, acknowledge it. When someone solves a hard problem, call it out. When you hit a milestone, take 30 minutes to appreciate it before moving to the next thing.
Model the behavior you want to see. If you’re sending emails at midnight, your team thinks they should too. If you never take PTO, neither will they. If you eat lunch at your desk, they will too. Your behavior sets the standard.
The Daylight Savings Time Factor: It’s Not Just About Sleep
Can we talk about how much the time change messes with people? Everyone focuses on “losing” or “gaining” an hour of sleep, but the real impact is psychological.
It gets dark at 5 PM. Your team members leave work in darkness. They arrive in darkness in the morning. They’re spending their entire workday disconnected from natural light, which humans are absolutely not designed to do.
This affects:
- Mood (hello, November depression spike)
- Energy levels (why is everyone so tired?)
- Motivation (hard to feel motivated when it feels like nighttime all day)
- Focus (circadian rhythms are confused)
- General sense of wellbeing (not great, to be honest)
What you can do:
Acknowledge it exists. Don’t pretend this isn’t affecting people.
Encourage people to go outside during lunch, even for 10 minutes. Natural light helps.
Be flexible about work hours if possible. Some people are morning people, some are night owls. Daylight Savings Time intensifies this.
Don’t schedule important decision-making meetings right after the time change. People’s brains need a week to adjust.
Consider whether that 8 AM meeting could be a 10 AM meeting, at least through November.
The Conversation You’re Avoiding: Talking to Leadership
You know what needs to happen. You need to tell your leadership that the current pace isn’t sustainable. You need to push back on unrealistic expectations. You need to advocate for your team.
This is terrifying. I get it. You’re worried about being seen as “not a team player” or “unable to handle pressure” or “not leadership material.”
But here’s the thing: Good leaders protect their teams. Great leaders advocate for sustainable practices even when it’s uncomfortable.
Schedule time with your manager or project sponsor. Bring data:
- Current workload per team member
- Number of projects vs. available capacity
- Risk assessment for current projects
- Velocity trends showing declining productivity
- Turnover risk (if you have it)
Use phrases like:
- “I want to ensure we deliver quality outcomes, which requires…”
- “I’m concerned about the long-term sustainability of…”
- “To meet these commitments without compromising quality, we need…”
- “I’m seeing signs of team burnout that could lead to…”
Propose solutions:
- Specific projects to defer
- Additional resources needed
- Timeline extensions
- Scope reductions
And if leadership responds with “everyone’s busy” or “just figure it out”? Document everything. CYA is not just a acronym, it’s a survival strategy. When projects fail or team members quit, you need evidence that you raised concerns.
The Self-Care Lecture You Don’t Want But Need
You can’t pour from an empty cup, and all those other clichés that are annoyingly true.
You’re managing your team’s burnout while probably experiencing your own. You’re absorbing stress from above and below. You’re the buffer between unrealistic expectations and human limitations. You’re doing emotional labor that nobody acknowledges while also doing your actual job.
This isn’t sustainable for you either.
You need to:
Take your PTO. Not “maybe during the holidays.” Actually take time off. Turn on your out-of-office. Don’t check email.
Set boundaries. Stop responding to Slack at 10 PM. Stop working weekends. Stop being available 24/7.
Find a peer group. Other project managers who understand that feeling of being trapped between leadership’s expectations and team capacity. Vent to them. Share strategies. Remind each other you’re not crazy for thinking this is hard.
Talk to a therapist. Not even kidding. Project management during crunch time is legitimately stressful enough to warrant professional support.
Exercise, sleep, eat food that isn’t from a vending machine. Your body is not a machine. It needs maintenance.
Acknowledge that you’re doing a hard job during a hard time of year, and that’s okay.
The Reality Check: Some Projects Will Fail
Let me say the quiet part out loud: Even with perfect project management, some projects won’t succeed. Some deadlines won’t be met. Some stakeholders will be disappointed.
And that’s okay.
Better to deliver fewer projects well than many projects poorly. Better to have a burned out team that recovers than a team that quits entirely. Better to reset expectations now than deal with complete project failure later.
Your job isn’t to make the impossible possible. Your job is to manage projects successfully within the constraints of reality. Reality includes: finite human capacity, time that cannot be magically created, and November being November.
The Path Forward: December and Beyond
You’re going to make it through November. Here’s how:
Week 1 (early November): Triage projects. Have hard conversations with stakeholders. Reset team expectations. Cancel unnecessary meetings.
Week 2-3 (mid-November): Execute on the reduced, realistic project plan. Check in with team members individually. Adjust as needed.
Week 4 (Thanksgiving week): Minimal work expectations. Seriously. Let people be with their families or just decompress. Don’t schedule launches during Thanksgiving week unless you hate yourself.
December: Finish critical projects. Let everything else go. Start planning for Q1 with realistic resource allocation.
January: Retrospective on what went wrong and how to prevent it next year. (Spoiler: next year will also be chaotic, but maybe slightly less so with better planning.)
The Final Word: You’re Not Failing
If you’re reading this and feeling like you’re barely keeping it together, join the club. November project management is survival mode. Daylight Savings Time is a conspiracy against human wellbeing. Year-end deadlines are mostly arbitrary. And burnout is a system failure, not a personal failure.
You’re doing your best in a system that’s working against you. That’s not failure. That’s resilience.
Take care of your team. Take care of yourself. Deliver what you can. Let go of what you can’t. And remember that in January, when everyone is rested and the days are getting longer again, you’ll look back on November and think “wow, we survived that.”
Because you will.
Now go cancel a meeting. Your team will thank you.
