Shorten a site meeting around its purpose and needed participants
A site meeting regularly fills ninety minutes. Most participants wait while two trades discuss a detail they have not prepared. The chair wants a shorter meeting, but moving that discussion elsewhere could hide an interface that other trades need to understand.
Set a meeting length from its purpose, available inputs and necessary participation. Thirty minutes may fit one agenda and be inadequate for another. Separate wider coordination from a narrower working discussion only after checking who needs its information and decision. Judge the complete effort, including the added conversations, rather than declaring a saving because the main meeting ends earlier.
Make a shorter agenda credible
- Identify the result each item needs. Ask the item owner for its question, supporting references and actual decision role. Distinguish an information update, a coordinated commitment and a technical matter requiring separate review. Do not reserve a small number of minutes for an unprepared decision and then pressure the room to invent an answer to protect the finishing time.
- Check who needs to participate. Keep people whose work, responsibility or information affects the outcome. Move a genuinely narrower working item to suitable participants with a receiving date and return route. Before doing so, establish how affected interfaces will be consulted and reported. Two people arguing does not prove that only two people need the answer, or that their agreement is authorized design approval.
- Set and use realistic item periods. Send the agenda and needed preparation with usable lead time. Confirm essential attendance and how an unavailable decision-maker's item will be handled. During the meeting, state the remaining question and route an overrun to an agreed next step. Avoid excluding a necessary participant merely to start on time or rushing a consequential commitment into the final minute.
- Close with received actions and review total effort. Read back owners, dates, conditions and the answer's receiving route. Keep pending decisions visible in the record. Afterwards, compare useful results, participant time, preparation and additional discussions. A shorter main meeting is helpful when its work is actually supported; a queue of unowned follow-ups can simply move the same delay outside the room.
Common mistakes
- Giving an unprepared technical question a forced decision deadline.
- Assuming only the two arguing people need the answer.
- Shortening the meeting by excluding a necessary decision role.
- Omitting extra discussions from the effort comparison.
Checklist
A credible shorter meeting has
- Ready questions, references and actual decision roles.
- Necessary participants and agreed narrower discussions.
- Realistic item periods and an overrun route.
- Received actions with pending conditions preserved.
- A review of complete effort and useful results.
Check your understanding
The main meeting is shorter, but three extra discussions are needed afterwards. Has attendance effort fallen?
