Running a meeting that isn't wasted

Separate the meeting from the build session

The most common mistake is holding both at once: half the team is trying to decide something while the other half is trying to drill a hole. Neither gets done, and the people at the robot correctly resent being pulled away.

Make the meeting a short, distinct block (fifteen minutes at the start of a session is plenty for most weeks) and then let people work. A ninety-minute meeting on a build night is a build night you did not have.

The standing agenda

Use the same four items every week. Repetition is the point: everybody knows what they will be asked, so they arrive with an answer.

1. What was due since last time, and did it happen? Yes or no, not an explanation.
2. What is blocked, and on whom? This is the item that actually earns the meeting.
3. What is due before the next meeting, and who owns each thing?
4. Dates: what is coming up, and has anything moved?

End with names and dates or do not end

A meeting that produces "we should look into the intake mounting" has produced nothing. A meeting that produces "Priya has the intake mount drawing by Thursday" has produced work.

Every outcome needs an owner and a date, written down where the team can see them rather than in the notes of whoever ran the meeting. If you use a task board, the meeting is just the moment things get assigned on it, which also means next week's first agenda item answers itself.

Decisions get decided, in the room

Debates run long because nobody agreed in advance who decides. Say it at the start of the season: technical calls belong to the subsystem owner, cross-team calls to the lead, safety and money to the mentor.

Timebox the discussion, then have the owner decide. Then write down what was decided and the reason. That reason is worth real points in the engineering portfolio, and it is the thing nobody can reconstruct in February.

The items worth repeating every single week

• Days until your next event. Say the number out loud; it changes how people prioritise.
• Anything blocked on a part that has not been ordered.
• Whether the documentation for this week's work exists yet.
• Who has not had anything assigned to them. That is your retention problem in advance.

Notes, briefly

Write four lines: decisions made, work assigned with owners and dates, anything blocked, next meeting. Put them where absent members can read them, which is what stops the meeting being re-run in the corridor.

Anything longer than four lines does not get read, including by the person who wrote it.