Stephen Brenish
Your lead programmer hasn’t taken a real day off in eleven weeks. She’s still hitting deadlines, her code still ships clean, and when you ask how she’s doing, she says “fine.” Three weeks later she hands in her notice. You never saw it coming, but you absolutely should have.
Burnout doesn’t announce itself. It accumulates quietly behind “fine” and “almost done” and one more late night that becomes forty. The games industry loses experienced people every year not because the work is too hard, but because the systems around the work are broken. The good news: most of those systems are fixable, and fixing them is squarely in a producer’s job description.
Why Game Dev Burnout Is Different
Every industry has burnout. Games have a specific flavor of it that makes conventional HR advice almost useless.
Developers in games are often deeply mission-driven. They care about the product in a way that makes it hard to disengage. That passion is exploitable, and studios, sometimes unconsciously, exploit it. “Crunch culture” is the obvious villain, but the subtler problem is a chronic low-grade overload: 50-hour weeks that aren’t officially crunch, scope that never quite gets cut, feedback cycles that reset work already done. That slow grind does more cumulative damage than a single death-march sprint.
There’s also the seniority trap. Your most experienced people are the ones most likely to say yes to extra load, least likely to flag that they’re drowning, and most catastrophic to lose. They’ve already been burned before. They’ve got a quiet countdown running.
Build Sustainable Capacity Before You Need It
The standard advice is “monitor your team’s wellbeing.” That’s not actionable. Here’s what is.
Track actual hours, not estimated hours. Scheduling 45-hour sprint loads into nominal 40-hour weeks and calling it “a bit of stretch” adds up fast: five extra hours a week is more than 100 hours of unacknowledged overtime per person over six months. Use a tool such as Harvest, or the time tracking built into Jira, to get real data. You can’t manage what you’re not measuring.
Set a hard team velocity baseline during a low-pressure period and defend it. When scope pressure arrives, that baseline is your negotiating position with leadership. “We ship 80 story points per sprint at sustainable pace. Adding this feature costs 20 points. What comes out?” That’s a producer’s job. Having the number makes it a business conversation instead of a feelings conversation.
Build buffer into your schedule intentionally. Not 10% contingency on a single task. Buffer weeks: one week per milestone where nothing new is scheduled. Teams use those weeks to catch up, refactor, rest, or handle the thing that always appears from nowhere. Studios that skip buffer weeks usually regret it by alpha.
Spot the Warning Signs Early
By the time someone’s performance visibly drops, burnout is already advanced. Watch for earlier signals.
The first sign is usually a change in communication pattern, not work quality. Someone who was chatty in standups goes quiet. Someone who pushed back on decisions stops pushing back. Disengagement shows up in meetings before it shows up in tickets.
Second is an increase in WIP without closure. A developer who normally finishes 5-6 tasks a sprint starts touching 12 but closing 3. They’re context-switching frantically, probably because they’re avoiding something, or trying to absorb too many priorities at once.
Third is vacation avoidance. Someone who keeps postponing approved PTO is telling you something. Either they don’t trust the team to function without them, or they’re afraid to stop because stopping would mean feeling how tired they actually are.
Run a simple biweekly check-in, one-on-one, 15 minutes, no agenda except “what’s hard right now and is your workload sustainable?” Ask the second question explicitly. People will answer a direct question more honestly than a vague wellness check.
The Scope Conversation Nobody Wants to Have
Burnout is usually a scope problem wearing a culture costume.
Teams don’t burn out because they work hard. They burn out because they work hard on an amount of work that was never achievable in the time available. The cure isn’t a meditation app. It’s cutting scope, and that conversation needs to happen between producers and leadership before the team feels the weight.
Here’s a practical framework for scope triage when pressure builds:
| Priority | Criteria | Action |
|---|---|---|
| Must ship | Core loop broken without it | Protect at all costs |
| Should ship | Meaningfully improves experience | Negotiate timeline |
| Nice to have | Polish, edge cases, features for 5% of players | Cut or post-launch patch |
| Legacy scope | “We’ve always planned to include it” | Kill it with fire |
The hardest category is the last one. Features survive in scopes because they’ve been on the list for two years, not because they serve the game. A producer’s job is to make that argument without sentiment.
Create Recovery Time That Actually Gets Used
Mandatory rest sounds paternalistic until you’ve watched a team ignore a “no meetings Friday” policy while still answering Slack at midnight.
Recovery time only works if leadership visibly participates. If the studio head is sending emails at 11 PM on “recharge Friday,” the policy is theater. Model the behavior you’re mandating.
Specific tactics that actually move the needle:
Post-milestone recovery time, scheduled in advance. Not “take some time after launch.” An actual calendar block, two to five days, no deliverables, communicated to the team before the milestone crunch starts. This gives people something to work toward and prevents the guilt spiral of “everyone else is still working.”
No-meeting core hours, not just days. Block 10am-12pm and 2pm-4pm as deep work time across the team. Meetings happen outside those windows. Flow state is genuinely restorative. Constant interruption is genuinely depleting.
Encourage real PTO by covering responsibilities explicitly. The reason people don’t disconnect on vacation is that nothing covers their work while they’re gone. Assign a backup. Document the handoff. Make it safe to actually leave.
Tools That Help Producers Stay Ahead of It
Burnout prevention is an operational problem, and operations have tooling.
Jira or Linear for sprint tracking with actual workload visibility. Linear is faster and less cluttered for smaller teams.
Harvest or Toggl Track for honest time data. Both integrate with project management tools.
Notion or Confluence for documentation that reduces the bus-factor anxiety driving a lot of overtime. When knowledge lives in one person’s head, that person can never fully disconnect.
For professional development on this specifically: Jason Schreier’s Blood, Sweat, and Pixels is required reading for understanding how scope and crunch interact at the production level. Less a how-to than a brutal case study collection. For the evidence behind sustainable pace, Evan Robinson’s essay “Why Crunch Mode Doesn’t Work: Six Lessons,” published by the IGDA in 2005, is still the clearest summary.
The best producers I’ve worked with treat team sustainability the same way they treat the critical path: something to be actively managed, with clear owners and visible metrics, not left to chance or goodwill. The games that ship well aren’t made by teams who grind hardest. They’re made by teams that were still functional, still motivated, and still actually there in the final three months when it mattered most.
Photo: RDNE Stock project via Pexels
