Meetings · make presence count
Save live time for live work
A call is not automatically collaboration. Bring people together when they need the immediacy of exchange, and give everything else a clear written path.
Decide what the gathering is for
Before sending an invitation, finish this sentence: “By the end, we will have…” A useful answer might be a decision, a shared understanding of a complex problem, a relationship-building conversation, or a plan for an uncertain piece of work. “Discuss project” is a subject, not an outcome. If the outcome is simply to share information, consider a written update people can read when they are ready.
Make the invitation explain the purpose, who needs to participate, what preparation matters, and how a decision will be captured. Invite people who can contribute or need to act on the result; do not fill every seat by habit. If a person is optional, say what they can review afterward. A smaller group can often think more clearly, while the record keeps others informed.
Design for different working conditions
Remote meetings ask people to manage audio, video, captions, chat, documents, and conversation turn-taking at once. Share materials in advance and make them accessible without requiring a particular device. Say whether cameras are optional. Use captions where available, and leave room for people to contribute in writing. A facilitator can watch the queue while another participant leads the discussion.
Time zones deserve the same care as room bookings. Check who is repeatedly asked to join outside reasonable working hours. Rotate difficult slots when the meeting truly requires everyone, and provide an async route for people who cannot attend. Avoid scheduling a call at the edge of one colleague’s day just because it is the middle of another’s.
Keep the conversation navigable
Open by naming the purpose and the decision-maker, if a decision is needed. Give a short moment for people to review the question, then invite input in an orderly way. If the conversation wanders, connect the tangent to the outcome or place it in a follow-up list. Not every tension needs instant resolution; sometimes a smaller group or a written proposal is the more thoughtful next step.
Close with a short recap: what was decided, what remains open, who owns each action, and when the next check happens. The recap should live beside the relevant work, not only in somebody’s private notes. This matters especially for colleagues who missed the call or work different hours. Ask one person to own the record and make that role explicit before the meeting begins.
A good meeting leaves behind less ambiguity than it found.
Use a simple meeting test
- Is real-time interaction important to the outcome?
- Can the purpose be written in one clear sentence?
- Are all invitees needed for the decision or conversation?
- Can participants prepare without searching through several channels?
- Will actions and decisions be recorded for absent teammates?
Review recurring meetings every few weeks. Ask whether the work still needs a live slot, whether the frequency is right, and whether everyone affected can participate fairly. Canceling a standing call is not a failure; it can be evidence that the team has found a better way to coordinate.