People have a limited daily budget of good decisions. My job is to keep that budget off the boilerplate and spend it where a human is genuinely needed. Every principle here serves that.
If a team needs willpower to do the right thing every time, I built the wrong system. Discipline runs out, and decision fatigue spends the same budget the hard problems need. So I fix the environment once instead of asking people to be disciplined forever.
My designers wrote their own Lua to drive game logic, and some of it got heavy. Big loops, no review. I didn't ask for cleaner code. I changed the path: keep writing Lua, but a commit needs a programmer's sign-off. The bad loops dropped, and in the trade, performance stopped being the designers' problem and moved to the engineers. A good constraint gives something back for what it takes.
Are you blocked? Are you delayed? Are you confused about the requirements? Those cover the only reasons someone can't move on their work.
All three no, and I stay out of the way. They have what they need, and stepping in would just be noise. Any one yes, and that's my cue: reprioritize something, set up the meeting, or clear the requirement, so they can get back to it. The questions check the system around the person, not the person.
The useful moment in a meeting is the hard one, the blocker nobody's saying. So I bring it up. It's us against the problem, never person against person.
Process problems get aired to the group. People problems never do, that's a 1:1, in private. I stand in as the intermediary, keep my own feelings out of it, and let both sides air their context until the misunderstanding comes apart. Nine times in ten it's a misunderstanding, not a real disagreement.
Three things drive good work: autonomy, mastery, and purpose. The org supplies the purpose. The person earns the mastery, chasing the work that pulls them.
Autonomy is the one I control, and it's a dial, not a switch. Grant none and I'm a micromanager. Grant all and the team drifts. I aim for autonomy within scope: enough room that people feel invested and can move, inside a boundary that keeps everyone pointed the same way.
For an IC, that's how their work affects the team. For a lead, how the team affects the studio. For a director, how the studio advances the company.
That wider view grows someone into the next level before they're in it. And it surfaces options that would otherwise stay hidden. The person closest to the craft, once they can see the goal from above, holds the idea only their discipline would think of. A cheaper path, a better effect, a different shape of the same outcome.
I want everyone on my team to grow into a senior who runs autonomously. Every raise, promotion, and bonus I can advocate for, I do.
And I'm honest about the selfish half. A team of autonomous seniors is one I barely have to maintain, and every hour I'm not holding the system together is an hour I put into making it better. The generous goal and the selfish one run the same direction.
Carry responsibility, grow people, confront the uncomfortable topics, and waste nobody's time. The same belief runs my games and the way I lead.