I’ve spent a fair amount of time on the other side of the GM screen, running tabletop games for friends and building more world than anyone asked for. Nothing as grand as a multi-year campaign, just enough sessions to get the reps. Somewhere in there I noticed I was getting better at my day job from an unexpected direction. Running a game well and running a team well aren’t similar skills. They’re the same skill, wearing different dice.
A few of the places it showed up.
Session zero is the kickoff you keep skipping#
Before a game starts, you run session zero: no adventure, just the table agreeing on what you’re actually here to play. Tone, the lines nobody wants crossed, what each person wants out of it. The player who came for tactical combat and the one who came to roleplay tavern conversations need to find that out now, not several sessions in when one of them is quietly bored and can’t say why.
Every team kickoff that went badly for me skipped this. We aligned on the deliverable and the deadline and assumed the rest. Then it turned out two people wanted completely different things from the project, one to ship fast, one to learn everything, and we found out in a tense review weeks later. Session zero asks the boring question up front: what does a good version of this look like to you? The answers are never as aligned as the kickoff slides pretend, and the half hour spent surfacing that is the cheapest half hour in the project.
The spotlight is a fixed resource#
A session is only so many hours, and the attention in the room is finite. If one player is a natural performer, they’ll eat the spotlight without any malice at all. The quieter player drifts, checks their phone, and before long stops preparing, because the table taught them their choices don’t get airtime.
The fix is the same one a good standup needs: the spotlight is a resource the person running the table hands out on purpose. You give the showy player a great moment, then you turn, deliberately, to the quiet one and ask what they do. Not “anyone else have thoughts,” which the quiet one always declines, the same way the junior engineer declines the open “any questions?” You ask them directly, about the thing they specifically know. Talent on a team isn’t evenly loud. Let airtime track volume and you lose your quietest people first, and you won’t notice until they’ve already checked out.
Players will derail the plot, and that’s the good part#
You prep an elaborate set piece. The players latch onto some throwaway character you invented on the spot and chase that instead, and the set piece sits there untouched. The new GM panics and herds them back. The experienced one drops the prep and follows, because the players just told you what they’re invested in, and their investment is the only fuel the game actually runs on.
I herded my teams back onto the plan for years. When someone got excited about a different approach, I treated it as a deviation to manage instead of the best signal in the room. Engaged people pulling hard toward something is the rarest resource you get. Spend less effort defending the plan and more pointing the energy that actually showed up. The prep keeps. It’ll be a great session whenever they wander back to it.
The rules exist so you can improvise safely#
A game system is a pile of rules, and the secret every good GM learns is that the rules are there to make improvisation safe, not to prevent it. Because there’s an agreed way to resolve a sword swing, I can invent a chandelier to swing from and we both already know how to handle it. The structure is what frees the table to do the unplanned thing.
Team process is supposed to work the same way and often doesn’t, because we forget what it’s for. The deploy checklist and the design-doc template aren’t about compliance. They’re there so that when the unexpected happens, and it will, nobody’s improvising the basics under pressure. Good process is the agreed ruleset that lets the team handle the surprise without arguing over fundamentals first. When the process becomes the point instead of the enabler, you’ve got a GM reading rulebooks aloud while the table falls asleep.
The actual lesson#
None of this landed from a management book, at least not in language I absorbed. It landed at a table, where the feedback is immediate and the stakes are zero. A bored player is a Tuesday. A bored engineer is a resignation a quarter from now. The GM’s chair turned out to be a flight simulator for the part of leadership that has nothing to do with being right and everything to do with whether the people around you are still leaning in.
