Interview: Game Producer on Crunch Culture

Alicia Romero, thirty-eight, is a senior producer at a mid-size studio in Montreal. She has managed teams through alpha, beta, certification, and the patch weeks players remember more than credits. She also worked eighty-hour weeks on a shipped title that underperformed commercially anyway—a combination that radicalized her against crunch as default culture.

This interview explores production realities players never see: milestone contracts, publisher pressure, and why “passion” language often masks planning failures. Alicia speaks for herself, not her employer.

Alicia asked us to note she speaks as a producer trying to change systems—not as an executive excusing them. She has missed birthdays and apologized with pizza. She is not proud of every milestone she shipped.

Before the interview she sent us a list of questions she hoped applicants would ask studios—crunch history, attrition after ship, whether producers can cut scope without executive approval. We include them here because she believes interview power should flow both directions.

How Crunch Gets Scheduled Without Anyone Saying Crunch

Publishers set immovable dates: holiday windows, conference reveals, fiscal year targets. Studios sign milestone agreements with penalties for slips. Producers inherit dates decided before scope was locked. Alicia describes receiving a gold master deadline with six months of features still on the whiteboard—then watching leadership nod because canceling the date felt impossible.

Crunch begins as “a temporary push” and becomes culture when temporary pushes happen every milestone for three years. Teams stop believing rest promises. Alicia stopped making rest promises she could not enforce contractually.

Crunch culture survives because milestone bonuses reward leads who hit dates regardless of overtime invoices workers never file. Alicia pushes for overtime tracking in producer dashboards even when finance ignores it—paper trail matters for future negotiations.

“Gold master date locked before scope locked. Crunch scheduled without saying crunch.”

The Human Cost She Cannot Spreadsheet Away

On her worst project, three senior engineers quit within six weeks of launch. One designer hospitalized for stress-related illness. Alicia herself developed migraines she still manages. The game shipped with Metacritic mid-seventies and layoffs two months later—a pattern she calls the crunch hangover industry normalized.

She keeps a private list of names—not for guilt performance, but to remember crunch is not abstract. When executives say “everyone knew what they signed up for,” Alicia hears people who needed visas, who had children, who loved making games and got exploited for that love.

One engineer’s hospitalization still haunts her standups. She asks how people slept—not as performance theater, but because sleep debt predicts bugs two sprints later.

“Three engineers quit. One designer hospitalized. Metacritic mid-seventies anyway.”

Production Tools That Actually Reduce Crunch

Alicia advocates ruthless scope locking eight months before ship—not feature creep dressed as polish. Vertical slices early. Automated build pipelines. Dedicated bug triage roles so engineers are not context-switching between features and firefighting. She tracks overtime weekly and escalates when averages exceed ten hours unplanned—not at ship, continuously.

Unpopular truth: some crunch comes from individual contributors hiding blockers until too late. Psychological safety to report slips early matters. So does producer willingness to cut features publicly instead of absorbing slips privately until overtime is the only lever left.

Scope cuts require producer courage Alicia learned late. Early career she absorbed slips to look competent. Now she cuts loudly in writing so design and engineering are not blamed individually for collective overcommitment.

“Track overtime weekly—not only in the final ship month.”

Saying No to Publishers—and Keeping Your Studio

Alicia lost one publisher deal when she refused a milestone schedule she deemed unbuildable without crunch. The studio found another partner six months later. She cannot promise that outcome universally—power imbalances are real—but she argues producers who never push back become complicit in schedules they know are lies.

She documents risk in writing: emails summarizing scope versus timeline, alternative cuts proposed, publisher acknowledgments. CYA is not cowardice when teams’ health is on the line. Legal and HR backed her once when a publisher claimed surprise at delays she had flagged monthly.

Publisher power imbalances are real. Alicia cannot promise every producer who pushes back keeps jobs. She can say silence guarantees crunch for someone junior on the team.

“I lost a publisher deal refusing an unbuildable schedule. We survived.”

What Players and Applicants Should Know

Players demanding faster patches on live service games feed crunch cycles Alicia cannot eliminate alone—she asks for empathy without absolving leadership. Applicants should ask studios about last three ship crunches in interviews. If answers are vague or framed as heroism, believe the vagueness.

Unionization progress in Montreal and elsewhere gives her cautious hope. Producers can ally with organizing workers instead of treating labor advocates as enemies of “the project.”

Union progress in Montreal changed conversations. Management now asks about overtime before milestone sign-offs sometimes—small win, repeated.

Live service patches after launch create perpetual crunch Alicia fights to cap with dedicated live teams—not feature team overtime forever. Separation of live ops from development is organizational design, not kindness.

Crunch questionnaires in job interviews should ask for numbers, Alicia says—not vibes. Average overtime hours last three milestones, attrition rate post-ship, whether producers had authority to cut scope. Vague answers are answers.

“Ask about last three crunches in interviews. Hero stories are red flags.”

Can Games Ship Without Crunch?

Alicia shipped a title last year with average overtime under five hours weekly across the final two months—unprecedented in her career. Scope was cut twice publicly. A feature players wanted delayed to post-launch DLC deliberately. Morale surveys improved. Sales met projections anyway.

She is not naive about competitive pressure. She is tired of pretending crunch is inevitable when it is often a planning and courage failure concentrated on the lowest-paid workers.

Her best ship used post-launch DLC to defer features players wanted instead of crunching them pre-gold. Team retention beat previous project by double digits.

Alicia trains junior producers to document scope cuts in producer bibles—not slack threads that disappear. Institutional memory prevents repeating the same overcommitment every sequel cycle because the last producer burned out and left.

Studios that treat producers as schedulers instead of risk managers get crunch they deserve, Alicia argues bluntly. Producers who only Gantt-chart without pushing back on scope are complicit—her past self included.

“We cut scope twice and still hit sales. Crunch is often courage failure.”

Crunch culture persists because it externalizes cost onto workers while executives keep milestone bonuses. Producers sit in the middle—Alicia argues they can move the middle toward accountability or toward complicity. Her interview is one data point from someone still inside, still trying to ship games without consuming people.

Players will never see Alicia’s name in credits the way they see directors. Producers shape conditions under which games get made. That power can absorb crunch downward or push back upward. She argues for pushing back.

Alicia keeps a printed scope-cut email from her best ship on her wall—a reminder that shipping healthy once makes the next negotiation with publishers easier. Evidence beats philosophy when executives demand dates nobody can build.

She invites applicants to email her privately with studio names if they want unofficial crunch reputation context—a whisper network producers maintain because Glassdoor reviews rarely capture milestone dynamics accurately.

Post-ship recovery weeks are now policy, not plea—Alicia counts that among wins worth repeating in industry panels.

Leave a Reply

Your email address will not be published. Required fields are marked *