What a studio is actually made of

I’ve led teams through productions that shipped, and the thing I think about most isn’t the games. It’s the culture around them. What held people together, what wore them down, and how much of that was set long before anyone on the team arrived.

Culture is the stuff nobody puts in a sprint ticket. It’s whether people feel safe raising a problem. It’s whether good work gets noticed or just absorbed into the schedule. It’s whether “we should fix this” leads to a conversation or a shrug. You can’t ship it, but you ship through it. Every day.

Recognition as infrastructure

The teams I’ve seen burn out fastest weren’t the ones with the hardest crunch. They were the ones where effort disappeared. Where someone solved a real problem and the next morning it was just the new baseline, unremarked. I’ve watched this happen at studios of very different sizes, and the pattern is always the same.

Recognition sounds soft when you say it in a planning meeting, but it functions like infrastructure. When people know their work is seen, they take risks, flag issues early, and stay longer. When they don’t, they do exactly what’s asked and nothing more. A team running on compliance instead of investment looks fine on a dashboard and feels dead in the room.

I made a point of calling out good work in my teams, by name, in front of other people. Not because I read it in a leadership book, but because I remembered what it felt like when nobody did it for me. It cost nothing and it changed the energy of the room. The fact that it felt rare told me something about the places I was working in.

The temperature you inherit

A lead inherits the culture of the studio whether they agree with it or not. You can build a microclimate inside your team, protect the people under you from some of the dysfunction, set your own standards. But the larger temperature leaks in. If the studio rewards firefighting over prevention, your team will eventually learn to wait for fires. If cross-department collaboration is discouraged, your team will stop offering help even when they see the need.

The hardest version of this I’ve lived through was watching good habits I’d built inside a team get eroded by the wider org. People would start reaching across to help another department and then pull back after being told it wasn’t their concern. The reflex I wanted them to have, the one where you see a problem and move toward it, got trained out of them by the system around us. I’ve since seen the same dynamic play out at other places, and it always starts the same way: one “stay in your lane” conversation at a time.

What I carry forward

I came out of these experiences knowing what I value in a studio, because I’ve worked in places where most of it was missing. A shared direction people believe in. Recognition that flows to the people who did the work. The freedom to cross a department line when the project needs it. A definition of leadership that means more than “manage your vertical and don’t cause problems.”

These aren’t luxuries. They’re the difference between a team that ships because it wants to and a team that ships because it has to. I’ve been on both kinds. The work looked the same from the outside. From the inside, they were completely different places.