Production 101 - #18 Running Meetings That Aren’t a Waste of Time

Why the most expensive meeting you run might be the one you hold every morning

Jun 07, 2026

Game Production Alchemist › Production 101 › How to Run Game Meetings That Don’t Waste Time

A ten-person standup that runs fifteen minutes costs two and a half hours of aggregate team time, every day.
Any information that can travel in writing should travel in writing. What remains is a much shorter meeting list.
No agenda means no meeting: a useful agenda is a list of questions needing answers, not topics to discuss.
Lean Coffee is a structured format for discussions where the agenda itself is uncertain, and it works.

Running meetings thumbnail with angry alchemist, crossed-out clock, agenda document, and production urgency graphics.

This is part of the Production 101 series.

A ten-person standup that runs fifteen minutes costs two and a half hours of aggregate team time. Every day. Run five days a week, that’s twelve and a half person-hours a week spent on a meeting whose entire purpose is to share information that, on a sufficiently mature team, travels faster in writing. Most producers inherit the standup cadence from whoever set up the project before them and never question it. That’s a reasonable description of how most meeting cultures form: through inheritance and inertia, with no one deciding.

I’ve done this. Early in my career I ran standups daily because that’s what you did. I ran them because the Scrum Guide said so, because the previous producer had run them, because stopping felt like admitting you didn’t care about communication. None of those are reasons. They’re habits dressed up as reasoning.

The cost calculation no one does

Standups are the most expensive meeting format in your weekly schedule, measured by aggregate cost. The formula is simple: headcount multiplied by duration multiplied by frequency. On a twenty-person team, a fifteen-minute daily standup is twenty-five person-hours a week. That’s more than half a person-week, every week, before the iteration planning, the milestone reviews, the one-on-ones, and the assorted other gatherings have been counted.

The uncomfortable question that formula raises is: what is that time buying you? On a team that is new to each other, building complicated dependencies, or working through something genuinely uncertain, a daily standup is probably worth the cost. Blockers surface fast. People know what others are doing. The meeting pays for itself. On a team that has worked together for two years, that documents properly and communicates well asynchronously, that same standup is often a recital of things everyone already knows, punctuated by the occasional “no blockers for me.”

Team maturity should determine standup frequency, not process habit. The team that needs daily synchronisation is the team that doesn’t yet have the discipline or the tooling to communicate without it. As that discipline develops, the frequency should come down. Three times a week. Twice. Once. The standup that stays daily indefinitely isn’t a sign of good communication. It’s a sign that nobody reviewed whether it was still needed.

The standup that stays daily indefinitely isn’t a sign of good communication. It’s a sign that nobody reviewed whether it was still needed.

The producers I’ve seen who never audit this tend to have the same explanation when you ask them: “the team likes the standup.” Sometimes that’s true. More often, the team has simply adapted to the standup the way you adapt to any recurring overhead. It’s just part of the day. If you removed it, you’d find out whether they actually wanted it or just got used to it. Run that experiment.

Async first

The principle is simple: any information that can travel in writing, should. The meetings that survive this filter are considerably fewer than the ones you currently have.

Status updates belong in writing. Progress reporting belongs in writing. Non-urgent questions belong in writing. Decisions with clear owners and well-understood options belong in writing. If you’ve read Production 101 #9 on status reports, you have the format for the written version. A well-maintained status report eliminates a significant portion of your recurring meeting load, because the meetings those reports replace were mostly people asking each other what was happening.

I’ve worked at studios where the weekly status report went out on Friday afternoon, and by the time Monday’s first conversation started, the project’s state was already documented and shared. People came in with context rather than questions. The synchronous time that followed was for work that actually needed live presence, not for getting everyone up to speed.

What actually requires real-time presence? Decisions that need live debate, where the outcome depends on people building on each other’s thinking in real time. Situations that need emotional attunement, where the written word is inadequate to the stakes of what’s being discussed. Problems that would take three long message threads to resolve and ten minutes in person. That’s not nothing. Those meetings matter enormously. But it’s a short list compared to the default.

The async-first producer doesn’t eliminate meetings. They eliminate the meetings that exist because nobody asked whether they needed to exist.

The agenda as the gate

I’ve operated a simple policy for years: no agenda, no meeting. Not as a preference. As a rule.

This does two things. First, it forces the person calling the meeting to be clear about what the meeting is for before anyone agrees to attend. Second, it makes it possible for attendees to prepare, which changes the quality of the conversation in the room.

A useful agenda is a list of questions that need answers. Not a list of topics to discuss. The distinction matters more than it sounds. “Art direction” is a topic. “Do we maintain the current visual reference or shift toward the concept work Yuki produced last week?” is a question. A topic can run indefinitely without resolution. A question has an answer, which means the meeting ends when you have it.

A useful agenda is a list of questions that need answers. Not a list of topics to discuss. Topics can run indefinitely without resolution.

Who owns the agenda? The person calling the meeting. When does it go out? At least twenty-four hours before the meeting, not five minutes before. The agenda that arrives the morning of tells attendees they’re expected to perform thinking they haven’t had time to do. The agenda that arrives a day before gives people the chance to come in with a position, which is what you need when you want a decision, not a discussion.

The producer’s job here extends to meetings they don’t run. If a meeting lands in your calendar with no agenda, you ask for one. Not aggressively, not as an accusation. You ask because you need to prepare. “What are the questions we’re trying to answer?” is a reasonable thing to ask of anyone who wants an hour of your team’s time.

Enforcing agenda discipline consistently trains the people around you over time. They stop scheduling vague meetings because they’ve learned you’ll ask what the questions are. That’s not a small thing. It changes the meeting culture of the whole team, one agenda request at a time.

Lean Coffee

Not every meeting has a clear agenda before it starts. Sometimes the question is “what do we need to talk about?” and you have a room full of people with different answers. The default response to this situation is an open discussion that runs long and ends inconclusively. There’s a better format.

Lean Coffee was created by Jim Benson and Jeremy Lightsmith in Seattle in 2009. It’s a structured format for discussions where the agenda itself is uncertain, and it’s one of the more practically useful things I’ve adopted across a long production career.

Here’s how it works. At the start of the session, each participant writes their discussion topics on individual cards or sticky notes, one topic per card. Once everyone has written theirs, you spend a few minutes dot-voting: each person gets a small number of votes (typically three) and places them on the topics they most want to discuss. The cards are ranked by votes and become the agenda.

You then work through the ranked topics in timeboxed segments, typically five to eight minutes each. At the end of each timebox, you take a quick vote: thumbs up to continue discussing this topic, thumbs sideways to wrap it up quickly, thumbs down to move on to the next one. Majority decides. The discussion continues until the time runs out or the topic list is exhausted.

What you get is a conversation shaped by the team’s actual priorities rather than whoever called the meeting. The loudest person in the room doesn’t determine the agenda. The person most senior in the hierarchy doesn’t determine it. The collective does, anonymously, by voting. That’s a meaningful difference.

I’ve used it most regularly in weekly team meetings. The prior week’s board acts as a shared record, so people arrive with topics already in mind. What the format changes is whose topics get discussed: the voting step means the person with the most to say doesn’t control what the group spends its time on. The collective need surfaces, rather than the need of whoever has the loudest voice in the room.

When should you reach for it? Any time you’re looking at a long and open-ended discussion that has historically run over time and ended without clear decisions. Any time you’re facilitating a group whose priorities you’re not certain about. Early-project alignment. Team health check-ins. Priority debates where multiple stakeholders have different views. The format doesn’t resolve disagreements, but it makes sure the important ones get airtime.

Facilitation as a distinct skill

There’s a version of running a meeting where the producer is a participant, like everyone else in the room, contributing opinions and building positions alongside the rest of the team. That’s sometimes the right mode. For most production meetings, it’s not.

The producer as facilitator is a different job. You’re the host. You hold the agenda’s questions and bring the group back to them when the conversation drifts. You manage time. You notice when a discussion has reached a decision but nobody has said the decision out loud, and you say it. You close the meeting with explicit decisions and named owners, not a general sense that something was discussed.

The specific skill that takes practice is managing the person who wants to workshop everything out loud. Every team has at least one: someone for whom thinking is a social activity, who processes by talking, and who will run a twenty-minute tangent if you let them. You’re not trying to shut them down. You’re redirecting. “That’s worth exploring. Let’s put it in the parking lot and come back to it if we have time.” The parking lot is real: write it down visibly, and either return to it at the end or make sure it gets a home elsewhere. The redirection only works if people trust you’ll follow through.

The producer as facilitator closes the meeting with explicit decisions and named owners, not a general sense that something was discussed.

The meeting that ended and the meeting that concluded are different things. A meeting ends when the time runs out or everyone leaves the room. A meeting concludes when every agenda question has an answer, every decision has an owner, and the next action is clear. Most meetings end. Fewer conclude. The producer’s job is to make sure they conclude.

The audit

If you’ve never done a full audit of your recurring meeting schedule, the exercise is uncomfortable and worth doing.

Go through every recurring meeting on your calendar. For each one, ask two questions. What decision does this produce? Who couldn’t get that information another way? The meetings that survive both questions are probably earning their place. The ones that don’t are candidates for conversion or elimination.

The meetings that typically survive: milestone reviews, where multiple stakeholders need to collectively assess whether delivery targets are still on track. Decisions requiring input from people who don’t have a shared written channel. Any situation requiring the kind of attunement you can only achieve in real-time conversation.

The meetings that typically don’t survive: status updates that could be a written report, which Production 101 #9 covers in detail. Recurring syncs where the conversation loops without producing decisions. Check-ins that exist because someone is anxious about visibility and prefers a meeting to a document. That last one is worth being honest about. If a meeting exists to manage someone’s anxiety rather than to produce information, the meeting is the wrong solution to that problem.

When a meeting fails the audit, converting it is usually straightforward. Status syncs become status reports. Recurring information-sharing meetings become a standing document that people comment on asynchronously. Meetings that existed for visibility become a dashboard or a brief weekly write-up. Some meetings simply stop, and nobody misses them, which tells you something about why they existed.

The producers I know who have done this exercise report the same finding: they typically recover two to four hours of team time per person per week. Not from eliminating meetings that felt important, but from eliminating meetings that nobody would have defended if asked to defend them directly. The audit asks the question. The meeting cadence never does.

None of this is a case for eliminating synchronous communication. Some things need a room. The judgment required is knowing which things those are, and having the production discipline to reserve the room for them. A well-facilitated milestone review is worth every minute it costs. A status standup on a team that already writes things down is a cost with no return.