How to structure a weekly team meeting agenda that people want to attend

Executive overview

Most meetings feel like a waste because the agenda is wrong, not because meetings are inherently bad. A well-designed agenda turns a weekly team meeting into an alignment and culture-building tool.

The agenda below runs 55–60 minutes and is built around human connection first, metrics second, and decisions third.

The agenda is the meeting — get that right and everything else follows.

Attendance and logistics

• Check off who's present for reference when posting notes later
• Assign a rotating note taker (excludes the facilitator) to capture key decisions and action items only — not a full transcript
• Note taker duty is light: a few minutes of work, not a secretarial role

Icebreaker and check-in

• One person brings a question each week — "what would you do if not this?" beats generic warm-ups
• Remote and hybrid teams: budget 10–15 minutes here deliberately
• These minutes reveal who's in the right headspace, who's stressed, who needs support
• Skippable for some teams, but high ROI for distributed ones

Celebrations and fail fest

• Celebrations: personal or professional wins shared openly — moving house, launching something, any milestone
• Fail fest: rebranded from "lessons learned" — normalises risk-taking by celebrating mistakes
• Examples shared: wrong email segment, wrong discount code, missed calendar invite
• Goal is to institutionalise a culture of continuous improvement without blame

Metrics review

• List every key north-star metric for the department (typically 5–10 numbers)
• Team members react with an emoji: good / bad / so-so — fast to fill in
• Each reaction includes a short note: why is it high? why is it low?
• Facilitator models curiosity: "email subscribers are up — is it because of the YouTube mention?"
• Converts passive tracking into active analysis; prevents autopilot data entry
• Takes about 10 minutes; generates more questions from the team over time

Capacity check-in

• Three questions per person, answered in emojis or words:
  1. How are you feeling overall?
  2. How full is your plate? (50%, 100%, 200%)
  3. Is anything standing in your way?
• Task counts and time estimates alone don't reveal true capacity — asking does
• Blockers surfaced here feed directly into the "to discuss" section

Calendar and announcements

• Calendar: upcoming holidays and PTO listed for visibility — not discussed unless relevant that week
• Just saying: brief one-way announcements only (e.g. new job listing) — "any questions? bring them to discuss"
• No status reports; async messaging handles those

To discuss

• The bulk of meeting time: approximately 30 minutes
• Typically 2–3 items per week — only issues that can't be resolved asynchronously
• Items are prioritised by emoji marker (today vs. can wait)
• Decisions and key notes are captured inline; meeting ends with a clean slate

Closing

• Decisions and actions: a dumping ground for tasks that emerged — items are turned into tasks in the work management tool directly
• End on a high note: a dad joke or inspirational quote, keeping the close light and memorable