Game production often sits in the uncomfortable space between creativity, deadlines, technical limitations, and business realities. That balance becomes even more complicated on large live-service and free-to-play projects.
Connor Graham has worked across both massive AAA pipelines and smaller mobile-focused teams, giving him extensive experience in game production – from milestone planning and bug triage to production alignment and roadmap management.
In this interview, Connor talks about production realities, supporting artists within large teams, balancing monetization with player experience, and why slowing down can sometimes be the healthiest production decision a team can make.
Main topics:
Game production
Product management
F2P game design
Art and production alignment
Burnout prevention
Live-service development
Mobile production
AAA production pipelines
Balancing Art, Production, and Capacity
One of the recurring themes throughout Connor’s answers is that art teams are often heavily constrained compared to other disciplines, especially on larger productions.
From his perspective, production planning frequently underestimates both the complexity of art work and the limited capacity of artists inside modern development pipelines.
Q: From your experience, what usually becomes the biggest challenge when trying to keep art, design, and production teams aligned?
A: Structurally speaking, in America we value art but undervalue artists. We’ve reduced not only the number of art jobs available, but also the number of pathways into those jobs, especially through traditional education.
Even early on, arts programs are often heavily limited in terms of class size, which naturally shrinks the pool of artists entering the industry.
And even highly skilled artists often struggle to justify pursuing art professionally because many adjacent careers simply offer better financial stability.
When I think about production, design, and art alignment, art is often overlooked during planning. In most teams I’ve worked on, we’ve had tons of designers and producers, but comparatively limited art resources.
Art itself is also incredibly complex. Concept art, tech art, game art, UI/UX – these are all different specialties requiring distinct skills and a highly coordinated game dev workflow.
Personally, I think capacity planning could improve significantly. We’d benefit a lot from better resource estimation and planning systems so artists receive work that actually aligns with realistic capacity instead of constantly being overloaded.
One thing that’s also unique to licensed projects is that we have to stay creative while working with familiar characters like Iron Man or Princess Leia. There are only so many recognizable poses and visual approaches that exist, so teams constantly need to find new ways to present iconic characters.
Creative Ambition vs Production Reality
Product and production roles often become the bridge between what teams want to create and what is realistically achievable within deadlines, staffing, and monetization constraints.
Connor describes this balancing act as one of the most challenging emotional aspects of production leadership.
Q: Product and production roles often sit between creative ambition and practical limitations. What part of that balance do people underestimate the most?
A: As a free-to-play game, one of the hardest parts is balancing business health with maintaining a genuinely good player experience.
Without a healthy business, the team doesn’t survive. But at the same time, players – whether they spend money or not – still deserve a good experience.
So the challenge becomes figuring out how to use systems in ways that improve the experience for free-to-play players while also supporting the business side.
Personally, I believe better games ultimately make more money, but convincing higher-level stakeholders of that can sometimes be difficult.
The second major challenge is validating roadmaps against reality. Sometimes ideas need to be delayed, split into future updates, or removed entirely because they simply don’t fit within the current production scope.
That can be emotionally difficult because developers care deeply about what they build. Games become people’s babies.
Production and product teams often become the people forced to say, “We can’t do this right now.” That doesn’t mean never – it just means not yet.
AAA vs Mobile Production
Connor has experience working both in massive AAA production environments and much smaller teams dedicated to mobile game development.
That contrast significantly changed the way he thinks about planning, iteration speed, and organizational flexibility.
Q: Has your approach to planning and prioritization changed after working on larger productions?
A: Absolutely.
At WB Games, our development team was massive. We had around 100 developers, plus another 30 to 50 people internally supporting the project full time.
Because of that, production roles became very specialized. Some producers focused almost entirely on bug triage or QA, while others focused on milestones or roadmap planning.
On my current team, things are much smaller, so I might handle bug triage and milestone planning on the same day.
One major thing I’ve learned is understanding when to push for change and how hard to push.
On smaller mobile teams, roadmap shifts can happen very quickly because communication is more direct and development cycles are more iterative.
At larger companies, especially in traditional AAA environments, changing pipelines or priorities requires a huge amount of preparation, data, and stakeholder alignment.
Neither approach is necessarily wrong – they’re just very different production cultures.
Avoiding Burnout and Crunch
Despite years of industry discussions around burnout, crunch culture still remains common throughout game development.
Connor believes healthier production often starts with something surprisingly simple: giving teams space to breathe.
Q: When development starts getting stressful near major milestones, what usually helps teams stay organized and avoid production chaos?
A: Crunch is still very common across the games industry.
I haven’t had full authority over large-scale production pipelines outside of indie projects, but my general philosophy is simple: take a step back, relax, and give people space to breathe.
Even in smaller ways, I try to reinforce that mindset constantly. I’ll tell developers “no rush” or “take your time” even when something is technically urgent.
If milestones slip, I’d rather take ownership of the delay than create unnecessary stress.
Breaks and downtime genuinely help people think more clearly and produce better work. When teams become overloaded, mistakes increase, bugs increase, and ultimately the player experience suffers too.
So when things start becoming chaotic, I try to gently push teams toward slowing down, regrouping, and resetting – even if only briefly.
The Human Element of Game Production
Connor Graham’s perspective highlights one of the more difficult realities of modern game development: production is often less about controlling creativity and more about protecting teams from unsustainable pressure while still moving projects forward.
What stands out throughout the conversation is how much game development depends on compromise, communication, and realistic planning – especially in live-service and free-to-play environments where business goals, player expectations, and creative ambition constantly compete with one another.
The interview also reinforces a broader industry issue: art and creative disciplines are frequently under-supported despite being central to how players emotionally connect with games.
For developers working in production, product management, or team leadership, the biggest takeaway may be that healthy pipelines are not just about schedules and milestones – they are also about protecting the people building the game itself.
Explore more behind-the-scenes stories in our exclusive interview series. We have many more conversations with industry visionaries coming soon, so be sure to visit us again.
Get in touch
Got a project in mind? We usually reply within a day.