Running and joining meetings

Why it matters

Meetings are where many technical decisions get made, and where many hours get lost. A well-run 25-minute meeting can unblock a whole team for a week. A badly run one ends with everyone unsure what was decided and who is doing what next.

You do not have to be a manager to make meetings better. Anyone can send a clear agendaA list of meeting topics sent in advance, each with an owner, a time box and the outcome you want., take good notes, or ask "Who owns that, and by when?" Those habits make you look organized and reliable early in your career.

The core idea: purpose, agenda, actions

Every meeting needs three things:

1. A purpose you can state in one sentence. "Decide which database to use for the inventory app." If you cannot state the purpose, you may not need a meeting at all. An email or a shared document might do.
2. An agenda sent in advance, so people can prepare.
3. Action items at the end: who will do what, by when.

Before the meeting

• Check whether a meeting is needed. Status updates often work better in writing. Meetings are best for decisions, problem solving and discussions that need back-and-forth.
• Invite only the people who are needed. Others can read the notes.
• Keep it short. Many meetings fit in 25 or 50 minutes, which leaves people time to get to the next one.
• Send the agenda at least a day ahead if you can, with any document people should read first.

A good agenda lists topics, an owner for each, a time boxA fixed amount of time given to one agenda topic. and the outcome you want:

Inventory app: database choice
Wed 10:00-10:25, Room 2 / video link
Purpose: decide between PostgreSQL and MongoDB for the inventory app.
Pre-read: comparison doc (link), 5 minutes.

1. (5 min)  Requirements recap: Aisha
2. (10 min) Pros and cons of each option: Ben, Chloe
3. (5 min)  Decision and reasons: everyone
4. (5 min)  Action items and next steps: Aisha

Note-taker: Dev

During the meeting

• Start on time and restate the purpose in one sentence.
• Keep to the time boxes. A facilitatorThe person, often the organiser, who keeps the meeting to its purpose and time and moves the group on. (often the organizer) gently moves the group on: "We're at time on this one. Can we decide, or should we take it offline?"
• Use a "parking lotA separate list for useful off-topic points, so they are not lost and do not derail the agenda.". Write off-topic but useful points in a separate list so they are not lost and do not derail the agenda.
• Give everyone a chance to speak. Ask quieter people directly: "Chloe, anything to add from the testing side?"
• Capture decisions and actions as they happen, not from memory afterwards.

Taking notes that work

Notes are not a transcript. They record what someone who missed the meeting needs to know. A simple template:

Meeting: Inventory app database choice (2026-10-14)
Attendees: Aisha, Ben, Chloe, Dev (notes)

Decisions
- Use PostgreSQL. Reasons: data is relational (items, suppliers,
  orders); the team already knows SQL; managed hosting is available.

Action items
- [ ] Ben: set up the PostgreSQL dev database. Due Fri 10-17.
- [ ] Chloe: draft the table design for items and suppliers. Due Tue 10-21.
- [ ] Aisha: tell the client the decision. Due Wed 10-15.

Parking lot
- Reporting tool choice (to discuss next week).

A good action itemA follow-up task with one named owner, a specific task and a due date. has three parts: one owner (a person, not "the team"), a specific task and a due date. "Look into hosting" is not an action item. "Ben: compare two hosting options and post a summary in the channel by Friday" is.

After the meeting

• Send the notes the same day, to attendees and anyone else affected.
• Put action items where work is tracked, such as the team's task board or ticket system, so they do not live only in an email.
• Follow up on actions at the start of the next meeting: "Ben, how did the database setup go?"

Joining meetings well

When you are an attendee rather than the organizer:

• Read the agenda and pre-reads, and come with your questions.
• Join on time, with your microphone muted on video calls when you are not talking.
• Keep your comments short and on topic.
• If you take on an action, repeat it back: "So I'll send the test results by Thursday."
• If you are not needed, it is fine to ask politely whether you can skip and read the notes instead.

Common mistakes

• No agenda, so the loudest topic takes all the time.
• No decision recorded, so the same discussion happens again next week.
• Actions without owners or dates.
• Too many people, so nobody feels responsible.
• Notes sent days later, after everyone has forgotten.

Quick recap

• State the purpose; send an agenda with owners and time boxes.
• During the meeting, keep time, park side topics and include everyone.
• Record decisions and action items (owner, task, date) as they happen.
• Send notes the same day and follow up on actions.

Try it

Open the Do tab. You will prepare an agenda for a short meeting and capture its action items.