How to run weekly team meetings that are worth attending

The short version

1. Decide the meeting's purpose.
2. Fix the time, length and attendees.
3. Use the same agenda every week.
4. Collect updates in writing before the meeting.
5. Spend the meeting on blockers and decisions.
6. Turn every action into an owned task.
7. Share a short written summary.
8. Review the meeting itself every few months.

Step 1: Decide the purpose

A weekly meeting should exist for something people cannot do well in writing: resolving blockers, making decisions together, aligning priorities for the week or keeping a team connected. If the meeting is only a round of status updates, those updates can be written instead.

Write the purpose in one sentence and put it in the calendar invitation.

Step 2: Fix time, length and attendees

• Same time each week, so people plan around it.
• Short, around 30 minutes for most teams, 45 at most.
• Only the people who need to be there. Others can read the summary.
• Avoid the edges of the week if possible; mid-week gives time to act on outcomes.
• For distributed teams, choose a time inside everyone's working hours, or rotate it.

Step 3: Use a fixed agenda

A predictable agenda means people arrive prepared. A simple one that works for most teams:

Keep the agenda in a shared document so anyone can add a decision item before the meeting.

Step 4: Collect updates in writing first

Ask each person to post a short update before the meeting: what they finished, what they are working on and what is blocking them. People can read these beforehand, so the meeting skips the round-robin and starts with the problems.

If your team uses a shared board or task list, many updates are already visible there. The pre-read then only needs to cover what the board does not show.

Step 5: Spend the time on blockers and decisions

The most valuable minutes are spent on items that need several people:

• Blockers: name the blocker, agree who will act and by when.
• Decisions: state the options, discuss, decide and note who decided.
• Priorities: if there is more work than capacity, agree what moves.

Park anything that needs deeper discussion for a separate, smaller conversation. Note the parked topic and who will arrange it, so it does not quietly disappear.

Step 6: Turn actions into owned tasks

An action that exists only in someone's notes will be forgotten. Before the meeting ends, turn each action into a task with one owner and, if needed, a due date, in the same place the team tracks its work. Next week, start by checking those tasks.

Step 7: Share a written summary

Within an hour, share a short summary: decisions made, actions and owners, and anything notable. Keep it in the team's shared space so people who missed the meeting, and future readers, can find it.

Step 8: Review the meeting itself

Every few months, ask the team: is this meeting useful? Should it be shorter, less frequent or differently structured? Meetings drift, and a quick review keeps them valuable.

Common mistakes

• Status round-robins that could have been written.
• No agenda, so the loudest topic wins.
• Decisions without owners, so nothing changes.
• No summary, so absent colleagues fall behind.
• Actions in private notes instead of the shared task list.

How to do it in Emitii

Emitii keeps the meeting, its agenda, its updates and its follow-up tasks in the same space:

1. Recurring event. Create the meeting in the space Schedule with invitees and a repeat rule (such as a custom "Repeat on" a chosen weekday). Invitees RSVP per occurrence, and you can book an office meeting room if you meet in person. The event appears in everyone's My calendar.
2. Agenda. Keep a running agenda doc in Docs & Files, or comment on the event itself with items to discuss.
3. Written updates. Ask people to post their update in Pulse as a thread, or as comments on a weekly post in Posts. The Board already shows owners, due dates and blocked cards; filter by Blocked to start the blockers section.
4. Catch-up help. In the Emit tab, ask "What is blocked or overdue?" or "Summarise what is in progress" to prepare the agenda.
5. Actions. Add each action as a to-do in Tasks or a card on the Board, with one assignee and a due date. A recurring to-do can remind the organiser to send the summary.
6. Summary. Publish the summary as a Post, pin it if it matters, and use "Notify everyone" so the whole space sees it.

Voice and video calls are coming soon to Emitii. Until then, remote attendees join through your usual call tool.

See the shared calendar in Emitii and Posts for team updates, how startups run weekly rhythms, the sample setup in the startup template, and how Emitii compares in Emitii vs Monday.com.