Stephen Brenish
Halfway through sprint review, your lead artist goes quiet. The creative director just called their environment work “a good start” and asked for “more energy.” No specifics. No examples. Just vibes-based criticism delivered in front of the team. The artist nods, says nothing, and spends the next two weeks technically doing their job while emotionally checking out. You’ve just watched morale die in real time, and the worst part is the creative director genuinely thought they were being helpful.
This is the most common production failure no one talks about. Studios obsess over crunch management, milestone planning, and pipeline efficiency. Feedback culture? Mostly an afterthought. But bad feedback loops kill games just as surely as bad budgets. They drive your best people out the door, create a culture of self-censorship where no one takes creative risks, and turn your review sessions into something the team dreads rather than uses.
Here’s how to fix it.
Why Creative Feedback Goes Wrong (And It’s Usually Structural, Not Personal)
Most feedback problems aren’t about bad intentions. The creative director above wasn’t malicious. They were busy, inarticulate in that moment, and operating without a defined feedback framework. That’s a production problem, not a personality problem.
The three structural failures I see most often:
Feedback without criteria. Your team doesn’t know what “good” looks like before they start work, so any criticism lands as arbitrary judgment. You can’t hit a target no one drew.
Public critique without psychological safety. Group review sessions are useful for some things. They’re a terrible place to deliver substantive negative feedback for the first time. People perform defensiveness in public. They actually hear you in private.
One-way transmission. Feedback given with no mechanism for response or clarification isn’t feedback, it’s a verdict. The difference matters enormously to the person receiving it.
Fix the structure and you fix most of the morale damage.
Setting Creative Standards Before the Work Starts
The single highest-leverage move a producer can make for feedback culture costs nothing and takes about two hours per project phase: write a creative brief that defines the target before anyone opens a tool.
A useful creative brief for a game asset or system isn’t a wall of prose. It answers four questions:
- What is this thing trying to accomplish for the player?
- What does success look and feel like? (Reference examples help here, even rough ones.)
- What are the hard constraints? (Engine limits, art style guides, scope boundaries.)
- What is explicitly out of scope?
When the brief exists, feedback has a reference point. Instead of “this doesn’t feel right,” a reviewer can say “the player-facing goal was tension, and this reads as peaceful, here’s why.” That’s a conversation the artist can work with. It also protects them from scope creep masquerading as feedback.
Notion or Confluence work well for housing briefs where the whole team can access and comment on them. Milanote is worth looking at for visual briefs that need mood references alongside text.
A Step-by-Step Framework for Delivering Feedback That Actually Works
This isn’t complicated. What makes it hard is consistency, specifically doing it this way when you’re under deadline pressure and tempted to just fire off a Slack message.
Step 1: Name what you’re evaluating against. Before giving any critique, state the brief criteria you’re referencing. “Against what we defined for this level’s pacing goals…” This signals that your feedback is principled, not personal.
Step 2: Describe what you’re observing. Stick to observable specifics. “The lighting in the middle section makes it hard to read the path” beats “the atmosphere is off.” One is actionable. The other is a feeling.
Step 3: Connect the observation to the impact. Why does it matter? “When the path is hard to read, playtesters miss the objective marker, and we saw that in three separate sessions last week.” Data and player experience are your strongest allies here.
Step 4: Ask before prescribing. “What were you going for here?” is genuinely useful, not a soft evasion. Sometimes the artist had a reason you didn’t know about. Sometimes hearing themselves explain it, they identify the gap themselves. Either way, you’ve respected their expertise.
Step 5: Define the next concrete action. Every feedback session should end with a specific, agreed task. Not “rework the lighting,” but “adjust the midpoint lighting so the path marker is visible within two seconds of entering the section, and flag me when it’s in for a quick look.”
The Public vs. Private Feedback Rule
| Feedback Type | Best Format |
|---|---|
| High-level creative direction | Async, written, before live session |
| Substantive critique on specific work | 1:1, before group review |
| Positive callouts, shared learnings | Group session, great use of the format |
| Directional pivots or scope changes | 1:1 first, then communicated to group |
| Quick iterative notes | Async tool comments (Shotgrid, Frame.io, etc.) |
I’ll be blunt: most group critique sessions in game dev are run badly. They default to senior people talking and junior people nodding. That’s not useful for quality and it’s actively harmful to psychological safety.
A workable model:
| Feedback Type | Best Format |
|---|---|
| High-level creative direction | Async, written, before live session |
| Substantive critique on specific work | 1:1, before group review |
| Positive callouts, shared learnings | Group session, great use of the format |
| Directional pivots or scope changes | 1:1 first, then communicated to group |
| Quick iterative notes | Async tool comments (Shotgrid, Frame.io, etc.) |
The group session becomes a lot more functional when it isn’t doing the job it was never designed to do. It’s for alignment, celebration, and shared context. Not for delivering news that blindsides someone in front of their peers.
Building Feedback Resilience Into Your Team Culture
Morale isn’t just about how feedback is delivered. It’s about whether the team believes the feedback is worth engaging with at all. If revisions feel arbitrary, if direction changes constantly, if nobody ever explains why a decision was made, people stop investing in getting things right. They start working to avoid criticism rather than achieve something.
A few things that make a real difference over time:
Close the loop visibly. When a team member’s suggestion changes the game, name it. “This fix came from Marcus’s playtest note two weeks ago.” People remember when their input mattered.
Make direction changes legible. When you pivot, explain the real reason. Not “we’re taking a different approach,” but “player testing showed that version confused first-time players at a 70% rate, so we’re pulling back toward a clearer tutorial pattern.” Respect the team enough to give them the actual information.
Read Liz Wiseman’s Multipliers and Kim Scott’s Radical Candor. Neither is specifically about games, but both are among the most practically useful books I’ve given to studio leads dealing with feedback culture issues. The Art of Game Design by Jesse Schell also has a sharp chapter on the feedback dynamics specific to creative teams in games.
For producers who want a more structured approach to team health, TeamRetro integrates with agile workflows and gives you a regular, structured way to surface feedback issues before they compound.
Feedback culture is a production problem. That means it’s yours to own, whether or not you’re the one giving the feedback. The best thing you can do right now is look at your next review session and ask one question: does everyone in that room know what they’re being evaluated against? If the answer is no, start there. Everything else follows.
Photo: Ben Khatry via Pexels
