Know what kind of meeting it is

Not every meeting does the same job. A daily huddle shares the plan and flags blockers. A weekly review looks at numbers and progress. A problem-solving meeting brings the right people together to fix one issue. A planning meeting looks ahead.

Decide which one you are calling, and say so in the invitation. If a meeting is only to pass on information that could be sent in a message, cancel it. Meetings are for discussion and decisions.

Set a purpose and a short agenda

Send the agenda a day before, with the purpose in one line: 'To decide how we handle festival-season deliveries.' List the topics with an owner and a time for each, and mark which require a decision. Invite only those who need to be there.

A fixed structure helps for recurring meetings. For a weekly review, you might use the same order every time: last week's actions, key numbers, problems, decisions needed, new actions. People learn the rhythm and come prepared.

  • One-line purpose
  • Topics with owner and time limit
  • Decisions needed marked clearly
  • Any data or paper to read beforehand

Run it on time, with roles

Start at the stated time, even if someone is missing; waiting teaches people to be late. Give the meeting a chair who keeps to the agenda and a note-taker who records decisions and actions. These can rotate among the team.

When a topic expands beyond its time, ask the room: do we need to decide this now, or should two people take it offline and report back? Park unrelated issues in a visible list rather than letting them hijack the meeting.

Make decisions visible

For each item, end with a clear statement: 'We have decided to move dispatch cut-off to 3 pm, starting Monday.' If there is disagreement, state how the decision will be made: by the owner after hearing views, by vote, or by consensus. Unclear decision rules lead to endless re-discussion.

Encourage quieter members to speak. Ask each person for their view before the most senior person gives theirs, since juniors tend to follow the boss. You will hear more honest input.

Record actions and follow them up

Capture every action in a simple table with three columns: what, who and by when. Send it to everyone within a day. Keep to one owner per action; shared responsibility often means none.

Begin the next meeting by reviewing these actions. Done, not done, or blocked. If actions are never reviewed, people conclude the meeting does not matter. This single habit changes the culture more than any agenda template.

A good meeting has a purpose, a short agenda, a chair, visible decisions and a record of actions that is reviewed next time. Try it on one recurring meeting for a month: shorten it, add the action table and start each session with a review. Ask the team afterwards what changed. If it works, apply the same format elsewhere, and cancel the meetings that nobody would miss. Fewer, shorter and better meetings give everyone hours back, and they show the team that their time matters.