I’ve been running the same tabletop campaign for a little over two years. Same four players, every other Sunday, a world I’ve built more lore for than anyone has asked to hear. Somewhere in year two I realized I was getting better at my day job from the wrong direction. The things that make a campaign work and the things that make a team work are not similar. They’re the same thing, wearing different dice.
This isn’t a metaphor I went looking for. It ambushed me mid-session when I caught myself doing the exact move on a quiet player that I’d failed to do in a retro the previous Thursday. So, a few of them.
Session zero is the kickoff you keep skipping#
Before a campaign starts, you run session zero: no adventure, just the table agreeing on what game we’re actually playing. Tone, lines we won’t cross, what everyone wants out of it. The player who wants tactical combat and the one who wants to roleplay tavern conversations need to find that out in session zero, not in month four when one of them is bored and doesn’t know why.
Every team kickoff that went badly for me skipped this. We aligned on the deliverable and the deadline and assumed the rest. Then two engineers turned out to want completely different things from the project, one wanted to ship fast and learn nothing, the other wanted to learn everything and ship slow, and we discovered it in a tense PR three sprints in. 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 tabletop session is maybe three hours, and there are four players. If one of them is a natural performer who loves the attention, they will, without any malice, eat the whole spotlight. The quiet player checks their phone. By session six the quiet player has stopped preparing, because the game 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 allocates on purpose. You give the loud bard a great moment, then you turn, deliberately, to the quiet ranger and ask what they do. Not “anyone else have thoughts,” which the quiet one will always decline, the same way the junior engineer declines the open “any questions?” You ask them directly, by name, about the thing they specifically know. The talent on a team is not evenly loud. If you let airtime correlate with volume, you lose your quietest people first and you don’t notice until they’ve already checked out.
Players will hijack the plot, and that’s the good part#
You spend a week prepping the haunted lighthouse. The players hear a rumor about a smuggler in the port and sprint off in the opposite direction, and your lighthouse sits there unvisited. The new GM panics and railroads them back. The experienced one throws the lighthouse prep in a drawer and runs the smuggler, because the players just told you what they’re invested in, and their investment is the only fuel the game actually runs on.
I railroaded my teams for years. I’d come in with the plan, and when someone got excited about a different approach, I’d treat their excitement as a deviation to manage instead of the most valuable signal in the room. Engaged people pulling toward a thing is the rarest resource you get. Spend less effort defending the plan and more figuring out how to point the energy that actually showed up. The lighthouse keeps. It’ll be a great session whenever they wander back.
The rules are there so you can improvise safely#
A tabletop system is a pile of rules, and the secret every good GM knows is that the rules exist to make improvisation safe, not to constrain it. Because there’s an agreed way to resolve a sword swing, I can invent a chandelier to swing from and we both know how to adjudicate it. The structure is what frees the table to do the unplanned thing.
Process on a team is supposed to work the same way and usually doesn’t, because we forget what it’s for. The point of the deploy checklist and the design-doc template isn’t compliance. It’s that when the unexpected happens, and it will, nobody’s improvising the basics under pressure. Good process is the agreed rules that let the team handle the chandelier moment without arguing about how damage works. When process becomes the point instead of the enabler, you’ve got a GM reading rulebooks aloud while the players fall asleep. I track the table’s turn order in a scratch Jupyter notebook for exactly this reason: the structure handles the bookkeeping so I can spend my attention on the people.
The actual lesson#
None of this is in a management book in language I’d have absorbed. It took rolling dice with the same four people for two years for it to land, because at the table the feedback is immediate and the stakes are zero. A bored player at a game is a Tuesday. A bored engineer is a resignation in a quarter. The campaign was 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.
