Developer First, Craft Second

Art Direction Lessons from Former Riot and PlayStation Art Director John Wu

Art direction in games is not only about style, taste, or making every asset look impressive.

Art has to support gameplay, fit technical limits, work inside production, and help the rest of the team build a better game. A visually strong idea can still be the wrong decision if it creates confusion, adds unnecessary complexity, or does not serve the player experience.

John Wu describes his guiding principle as “developer first, craft second.”

His career spans concept art, art direction, external development, outsourcing, team leadership, and large-scale game production. He has worked across Riot Games, PlayStation, Insomniac Games, Sony Bend, Behaviour Interactive, and Super Evil Megacorp, contributing to projects and teams with very different needs and structures.

In this interview, we explore how art directors connect craft with game development, help large teams maintain a shared quality bar, work with external art partners, and prepare younger artists for major game projects.

Main Topics

• Game Art Production
• Art Direction
• Art Team Leadership
• Player Experience
• External Art Teams
• Game Art Outsourcing
• Art Production Workflow
• Game Development

Interview

Q: You describe your guiding principle as “developer first, craft second.” What does that mean in practice?

production needs, technical limits, artistic decisions.

At its core, “developer first, craft second” means understanding what we’re building, who we’re building it for, and why it deserves to exist. That understanding gives every developer, regardless of discipline, the confidence to make decisions when the path isn’t always clear. Solving that problem together is what defines a developer.

The goal isn’t to create beautiful art for its own sake. It’s to contribute to a player experience that people genuinely enjoy. Art is one part of that equation alongside design, audio, engineering, production, and every other discipline. The best games aren’t the result of isolated craftsmanship. They’re the result of a team aligning behind a shared vision and making thousands of good decisions together.

Craft is also one of the most expensive investments a team makes. High-quality assets require significant time, talent, and iteration, which is why I believe in validating the experience before polishing it. If a rough blockout or proxy proves the core gameplay is engaging, then the team can invest in final quality with much greater confidence. If the experience isn’t working, no amount of polish will fix the underlying problem.

In practice, that means establishing a clear product vision, then moving through ideation, prototyping, playtesting, and refinement. With each milestone, the unknowns become known and the team gradually replaces uncertainty with confidence.

Ultimately, being “developer first” is about reducing uncertainty before increasing investment. Craft will always matter, but its greatest value comes when it’s serving a well-defined product, a shared vision, and an experience worth building.

Q: You began as an illustrator, storyboard artist, and concept artist before moving into art direction and leadership. What changed in the way you judged good art?

I still appreciate great art on its own merit because art is inherently subjective. But game art is different. It exists with intention. Every artistic decision should answer a simple question: Why does this belong in this game?

Early in my career, I judged good art almost entirely by execution. I started in traditional animation as a layout posing artist, focused on creating the strongest image I could from the direction I was given. As my career progressed, my perspective widened. I realized that great art wasn’t simply about execution. It was about supporting a larger vision.

A turning point came when I joined Insomniac Games. The studio was still relatively small, which gave me the opportunity to work closely with artists, designers, and engineers. I learned enough about each discipline to understand their challenges and appreciate how one decision could ripple throughout production.

I stopped thinking of an art director as the person with the craft or art style. Instead, I saw the role as helping the team discover the best ideas and visuals together and aligning them toward a shared vision ‘objectively’. Great artists need room to explore and contribute, but they also need clear guardrails. Without them, even strong teams can spend months debating personal taste instead of improving the product.

I’ve also been on the other side. As an artist, I remember endlessly iterating on details that ultimately came down to subjective direction. Those experiences made me want to become an art director who grounded creative decisions in the needs of the product rather than personal taste.

Q: How can an art director tell when a beautiful idea is helping the game and when it is only making production harder?

The first question I ask isn’t, “Is this idea beautiful?” It’s, “Does this idea strengthen the player fantasy?”

Ideas are easy to generate. The harder challenge is identifying which ones are worth the investment. The best ideas do more than look impressive. They reinforce the world, support gameplay, and make the player feel more immersed.

For example, enemies appearing out of nowhere may technically work, but players recognize when something feels artificial. In a military game, they might rappel from helicopters. In a zombie game, they might crawl out from underground. In a science fiction game, they might arrive in drop pods. Those ideas add production cost, but they’re justified because they strengthen the experience.

The art director’s job is understanding which ideas create meaningful value and which simply add complexity. As artists, we can always find another detail to refine or another feature to add. The challenge is knowing when we’re improving the player’s experience versus satisfying our own creative preferences.

That’s where creative direction and playtesting become important. The team needs to understand the target audience, genre, visual identity, and experience we’re trying to create. Playtesting then provides another perspective. If players are distracted by the art, that’s useful feedback. If they’re immersed and talking about the gameplay and experience, that’s often a sign the art is doing its job.

Ultimately, every creative decision is a tradeoff. A good art director isn’t the person who pushes the most ambitious ideas. They’re the person who understands which ideas are worth pursuing.

Q: You have worked closely with artists, designers, engineers, producers, and external teams. What usually causes these groups to misunderstand each other?

The biggest cause of misunderstandings is usually a lack of clarity and shared context around the original ask.

A high-level feature idea can create a huge ripple effect downstream. For example, a VFX artist might be asked to create an effect without understanding the player experience, gameplay intention, or narrative context. They may go back to the designer for clarification, but that conversation can become isolated. Now the artist has information that the rest of the development team may not have. The approach that has worked with me is to establish alignment at the source before communicating and soliciting conversations downstream.

For any significant feature or play experience, it’s always best for the team to articulate a simple elevator pitch from the player’s perspective: What do we want the player to experience? What is the player fantasy? What behavior are we expecting? What gameplay, narrative, and visual elements support that experience?

I’ll typically bring narrative and design together first. Once they’re aligned, I’ll work with concept artists to loosely visualize the experience holistically, then circle that back to design and narrative for validation. This lets us catch misunderstandings before they become expensive later on.

Once the direction is validated, I want the context captured in a master Jira epic or story that becomes the source of truth. The cross-functional team should be able to openly discuss the objective, share ideas, raise concerns, and help shape how we achieve it, with the important decisions and conversation notes captured in that same ticket. This keeps the context visible and consolidated rather than fragmented across meetings, messages, and individual people.

Ultimately, everyone should understand not just what they’re making, but why. The direction may come from the top, but the thinking and problem-solving should also come from the bottom up.

Q: What should a growing game team put in place before its art production becomes difficult to control?

I’d start with something that sounds a little cheesy: a culture of team spirit and shared ownership. Everyone should feel they have a role in improving the art organization as a whole. If the team is constantly refining how it works, the needle can continue moving forward as the organization grows.

From there, I’d focus on a few foundations.

First, create clarity and make onboarding a priority. A clear art org chart helps everyone understand who’s who, what they do, and where to go for different needs. I like creating a simple onboarding cheat sheet covering the art team, key partners across disciplines, and the high-level project vision and history.

Second, establish a team charter, working agreements, and a culture of knowledge sharing. The charter defines the team’s purpose, direction, and boundaries, while working agreements establish how the team collaborates day to day. Documentation then turns that knowledge into something scalable. I think of it as, “What would I teach another version of myself if I didn’t have to repeat myself every time?”

Finally, establish production discipline. Artists need visibility into how their work connects to disciplines, milestones, and the project as a whole. Being able to scope, forecast, and plan work, in partnership with a strong production team, can remove a lot of ambiguity and fire drills.

Ultimately, the goal isn’t to create more process. It’s to create enough shared context, clarity, and accountability that the team can scale without constantly reinventing how it works.

Q: When an art team becomes very large, how do you keep the quality bar consistent without adding endless review layers?

The key is to scale the art direction rather than centralize it as in single or few points of failure. By the time a team becomes large, there should already be a clear global art style and discipline-specific style guides that define the visual bar and provide concrete WGLL benchmarks.

The art director shouldn’t be reviewing everything. Art direction can be delegated to discipline leads who have worked closely with the AD and understand the vision and expectations. The AD stays connected through recurring touchpoints with the leads, while the leads manage the quality of their respective disciplines.

It’s also important that everyone understands what phase of development we’re in and what kind of feedback is appropriate for that phase. During prototyping, for example, the question might simply be, “Does this work?” We don’t necessarily need feedback on polish, materials, or whether it’s fun yet. If we’re in blockout and someone is reviewing final material quality, we’re creating noise rather than value.

Each discipline should have clear workflows, checkpoints, and WGLL examples showing how work moves from a creative brief through final production.

Ultimately, consistency comes from shared context, clear standards, and distributed ownership. The goal isn’t to add more reviewers. It’s to make sure the right people are making the right decisions at the right time.

Q: What separates an external art team you trust from one you would never hire again?

For me, it comes down to integrity, transparency, and communication.

We’ve all heard about the bait-and-switch. If we choose an external team or specific artists because of their quality and experience, then discover later that the work has been handed off to someone else without our knowledge, that can damage the relationship very quickly. Things happen and people become unavailable, but I’d much rather have a partner tell me upfront so we can figure out how to adjust than discover it after the quality has dropped.

Communication is equally important, and it’s a two-way street. I expect our partners to be responsive, and we need to be responsive to them as well. More importantly, I want them to tell me bad news early. If they’re going to miss a milestone, discover a technical limitation, misunderstand the brief, or realize the scope is larger than expected, I want to know as soon as possible. Problems are much easier to solve when there’s still time to react.

I also value external teams that understand the why, not just the what. A good partner shouldn’t simply execute a brief. They should understand the project’s vision, the player experience, the constraints, and what we’re trying to accomplish. And if they see a better way to approach something, I want them to bring that expertise forward rather than simply say yes to everything.

The external teams I value most feel like extensions of our own team rather than a transactional service. The point of contact is almost as important as the artists doing the work. When communication is strong and both sides have shared context, we can openly discuss timelines, bottlenecks, and problems and work together to resolve them.

Ultimately, a vendor delivers what you ask for. A partner understands why you’re asking for it, tells you when something isn’t working, brings their expertise to the table, and earns your trust over time. Quality matters, of course, but trust is what makes the relationship sustainable.

Q: What would you advise a young artist who wants to work on major game projects but is only beginning their career?

I’d say pick a lane and bear hug it. Think of it like an RPG skill tree. You need to build depth somewhere before you can meaningfully expand from there.

I started my game dev career as a texture artist at Insomniac Games, unwrapping UVs and texturing day in and day out. That repetition helped me build a strong foundation in one vertical. From there, I kept adding skills, both hard and soft, and gradually expanded what I could bring to a team.

Make mistakes. I certainly have, and I still do. The important thing is to learn from them, pivot when necessary, and own them. Your career isn’t going to be a straight line.

And relationships matter. I tell my kids to meet people and build connections because you never know what someone can teach you or where your paths might cross again. You don’t need to be close with everyone, but trust that everyone has something to offer. It’s a relatively small world, and the relationships you build along the way can last much longer than any one project or studio.

So, if I could give a young artist one piece of advice, it would be: get really good at your craft, then expand from there. Become T-shaped: develop deep expertise in one area while building complementary skills that allow you to collaborate, solve problems, and bring additional value to the team, project, or the company as a whole.

The goal isn’t to know everything. It’s to become really valuable at something, then keep growing.