Capcom, Jira, and the Question of Who Gets to

A US-based former Capcom employee says Western studios lean too hard on project management software like Jira, and the industry has been arguing about it ever since.

The claim comes from an interview conducted by journalist Lewis Gordon for a feature at The Ringer on Capcom's current "golden age." The ex-employee, speaking anonymously, described a production culture at Capcom that privileges creative ownership over ticket-tracking overhead, and contrasted it with Western publishers that, in their view, drown teams in productivity suites. The exchange has been picked up and summarized by God is a Geek, Kotaku, and NewsBeep, and the framing that stuck is blunt: competitors are wasting their time on Jira while Capcom makes games.

What the Ex-Employee Actually Said

Read the summaries closely and the argument is narrower than the headlines. The critique is aimed at the culture around the tool, according to Newsy Today, not at planning software itself. Nobody credible is claiming that a studio can ship a 300-person open-world game on vibes and a shared notebook. The accusation is that measurement has become a substitute for judgment: when every task must be broken into tickets, sized, groomed, and reported upward through layers of production management, the people doing the creative work spend their days servicing the system rather than the player.

That is a real failure mode, and it is not unique to games. Anyone who has watched a status meeting expand to fill a calendar recognizes the shape.

The Japan Frame Does a Lot of Work

Capcom's recent run speaks for itself: the Resident Evil remakes, Monster Hunter's continued dominance, a revived Onimusha. Gordon's feature frames this as the product of a healthier equilibrium, and the anonymous former employee's Jira complaint is one data point inside that larger argument. The pick-up coverage, including God is a Geek, leaned on the Onimusha angle and the East-versus-West framing, because that framing travels well.

It also flattens things. Larian shipped Baldur's Gate 3 out of Belgium with a large, heavily coordinated team and years of early access. Obsidian, Santa Monica Studio, and Insomniac all run rigorous production pipelines, and all have shipped acclaimed work recently. Meanwhile, Japanese studios have had their own process disasters; Sega's outsourcing missteps of the early 2010s and the troubled development cycles of several mid-tier Japanese productions are part of the record. The variable that predicts a healthy studio is not longitude. It is whether the people with creative authority actually have it, and whether management treats coordination as a service to the work rather than the work itself.

One more caveat the headline version omits: the source is a single anonymous former employee. Anonymous sourcing is sometimes the only way to get candid accounts of internal culture, and Gordon's feature reportedly drew on multiple current and former staff. Still, one person's experience of one company at one moment is an anecdote, and the internet is treating it like a diagnosis.

Why Workers Hear a Threat

The debate has landed on raw nerves for reasons that predate any single interview. Western games employment has been through a string of high-profile layoffs and studio closures across 2023, 2024, and into this year, a wave documented extensively by outlets covering the industry's contraction. Against that backdrop, any efficiency narrative reads as a preamble to cuts. Workers who survived the last reorganization can be forgiven for hearing "less process, more output" as "fewer of you, faster."

There is also a genuine tension the pro-Capcom argument glosses over. Coordination is expensive because modern games are expensive. A studio shipping a nine-figure title cannot let every designer follow their instincts unrestrained; the budgets that make Capcom's polish possible also demand predictability. Process is how large organizations try to buy predictability. The question is where the curve bends, and that answer is different for a 40-person indie than for a 400-person sequel factory.

This Fight is Older than Jira

The pattern rhymes with history I spend a lot of time around. In the late 1970s, Atari's management famously kept its programmers anonymous and uncredited, treating talent as interchangeable labor on an assembly line. The result was Activision, founded in 1979 by David Crane, Larry Kaplan, Alan Miller, and Bob Whitehead, four programmers who wanted their names on cartridges. The Atari collapse of 1983 followed in part because management systems built for predictable output could not see, let alone retain, the actual authors of the product.

Skip forward to the 2000s. Mid-size Western studios adopted film-style pipelines and massive outsourcing waves, breaking art production into standardized, spec-driven chunks shipped across time zones. The cost: teams lost coherence, quality control suffered at the seams, and a generation of designers complained that the game had been assembled from parts nobody had played together. The lesson studios eventually absorbed was that the pipeline must serve a single creative vision, not replace it. Jira is the 2020s expression of the same pressure. The tool changes; the tension between legibility and authorship does not.

As someone who spends most of my time on game preservation, I will add a quieter observation. The games most at risk of being lost are rarely the ones made by chaotically auteur-driven teams; they are the ones made by process-heavy organizations whose documentation lived in proprietary systems and died with the server. A production culture that mistakes its tracking system for the work also tends to mistake the database for the archive. When the studio closes, the tickets evaporate and nobody can reconstruct how the game was actually made.

What Would Settle It

The strong version of the Capcom argument is simple: give small creative leaders real ownership, keep coordination lean, and judge decisions by the player experience rather than velocity metrics. The strong counterargument is equally simple: that culture is easier to describe than to scale, and the studios that have it often got it through decades of stable employment, family-like staffing practices, and a domestic market that tolerates slower cadence, none of which survives a cost-cutting regime.

Both things can be true. Capcom can be a genuine success story and a poor template, because the ingredients (patient capital, retained talent, clear internal creative authority) are the hard part, and none of them are available for purchase with a license of anything.

The honest test will come when a Western studio publicly tries the Capcom model, names the creative leads, cuts its own reporting layers, and publishes the results, including the failures. Until then, the Jira debate is a proxy fight over a question the industry keeps refusing to answer directly: when a game ships, whose work is it, and does the system that produced it treat those people as authors or as line items?