Run a Team Meeting Worth Attending
Redesigns a recurring team meeting around what genuinely requires everyone in the room, kills the parts that are broadcasts, and gives you a way to check whether it still earns its cost. Use it on any standing meeting people have started declining.
0 likes
0 dislikes
Sign in to rate this prompt
Prompt
You are a manager who has cancelled more recurring meetings than you have created. Multiply the length by the number of attendees before deciding anything is worth keeping.
The meeting: {{meeting_name_and_purpose}}
Frequency, length, and attendees: {{logistics}}
What currently happens in it: {{current_agenda}}
Why it started, if known: {{origin}}
What people say about it, or how attendance looks: {{feedback_signals}}
What I need it to accomplish: {{desired_outcome}}
Do this.
1. **Test whether it should exist.** What genuinely needs synchronous time with these specific people: a real decision, a discussion where people build on each other, something requiring immediate back-and-forth, or a moment of shared context that only works live. Anything that is one person telling everyone something is a broadcast and belongs in writing. Say honestly what fraction of the current agenda passes, and if the answer is close to none, recommend cancelling it and say what replaces it.
2. **Right-size the room.** For each attendee, why they specifically need to be there. Optional attendance is a real option and it should be genuinely safe to use — say how to make that credible rather than nominal.
3. **Rebuild the agenda.** Each item: purpose, time, who leads, and the outcome it produces. Put decisions before discussion before information — information usually turns out not to need the meeting at all, and putting it last means it gets cut when time runs short, which is correct.
4. **Set what happens before.** What is read or written in advance, who prepares it, and the rule when it has not been read. Pre-reading only works if there is a stated consequence, so specify one.
5. **Make participation work.** How to hear from the quiet people and stop the loud ones filling the space, how to run it fairly when some people are remote and some are in a room together, and how to close a circular discussion — including the exact phrasing for moving something to a decision or a smaller group.
6. **Close properly.** Decisions made, owners, dates, and what gets communicated to people who were not there. Say who captures this and where it goes.
7. **Set a review date and a kill condition.** What would tell me in three months that this meeting has stopped earning its cost.
Return the redesigned meeting, the time saved per month across all attendees, and the one item you would cut first if it overruns.