How to Make a Meeting Worth the Time

A project team has reached a fork: the launch date may need to move, but the people in the room have different information and no shared plan for choosing. They could meet to decide, work through the options together, or simply exchange updates. The right choice depends on what must happen by the end—not on habit, calendar availability, or the fact that the topic feels important.

A useful meeting has a defined job, the people needed to do that job, and an output that someone can carry forward. Three formats cover many workplace needs: a decision meeting, a working session, and an update meeting. Each can be worthwhile, but each becomes wasteful when it is used for the wrong task.

Use a decision meeting when a choice is ready

A decision meeting is for choosing among options, resolving a disagreement, or approving a proposal. It suits situations where the decision depends on input from several people, or where the people who must act need a shared understanding of the choice. It is a poor fit when the group has not seen the relevant information or when no one present has authority to decide.

Before inviting anyone, write the decision as a question with a limited scope. “How should we handle the launch?” is broad. “Should the launch date move, and what must change if it does?” gives participants something they can prepare to answer. If the decision depends on legal, technical, or customer-service constraints, invite the person who can explain those constraints—not an entire department by default.

Share a short briefing in advance: the options, the criteria for choosing, relevant facts, and any recommendation. During the meeting, distinguish facts from preferences. Ask the decision owner to state the choice and its reasoning before the conversation moves on. The record should name the decision, the person responsible for the next action, and any condition that could prompt a review.

This format is best when a group can make a real choice in the time available. If a key participant cannot attend, decide whether that person’s input is essential. The meeting may still be useful for gathering views, but it should not be presented as a decision session if the actual decision must wait.

Choose a working session when the group must make something

A working session is for creating or improving an artifact: a draft, a plan, a process map, a list of requirements, or a shared set of options. It suits work that benefits from people thinking together in real time. It does not suit a task that one person could complete more quickly alone and then circulate for comment.

Define the object of the session and its intended state at the end. “Discuss onboarding” gives no boundary. “Draft the first-week checklist for a new support colleague” identifies a tangible output. Choose participants for their contribution to that object. A team lead may know the sequence of work; a new colleague may notice where instructions are unclear. People without a relevant role can often review the finished draft instead of attending the whole session.

Bring the materials into the room before discussion begins. For a process map, this might mean a shared document or a whiteboard with the current steps already listed. For a draft, open the draft itself rather than talking around it. Assign someone to capture edits and someone to keep the group focused on the stated output.

Working sessions need room for exploration, but they still benefit from a boundary. If a new issue appears, record it in a parking list and decide whether it belongs in the current task. Close by naming what the group produced, what remains unresolved, and who will revise or review the artifact. The output might be a rough draft rather than a finished product; make that status explicit.

Use an update meeting only when live exchange matters

An update meeting is for sharing information and clarifying what it means for the people present. It can suit a team facing interdependent work, changing priorities, or questions that are easier to answer together than in a message. It is usually a poor choice when participants only need to read routine status reports.

For routine updates, a written note in a shared document or project channel often lets people read at a convenient time and refer back later. If the discussion needs to happen live, give the meeting a specific purpose beyond taking turns reporting. For example, ask the team to identify dependencies that could block the next piece of work, then assign owners to follow up.

Keep the invited group to people who need the information or can act on it. Send background material beforehand, and use the meeting for questions, coordination, and decisions that arise from the update. Record new commitments and unresolved points rather than trying to reproduce every spoken sentence.

This format is most useful when the group needs a shared picture of what is changing. If the only outcome is that everyone has heard the same information, ask whether an accessible written update could do that job with less interruption.

Choose by matching the output to the work

Start with a sentence that completes the phrase, “By the end, we will have…” If the answer is a choice, use a decision meeting. If it is a draft or a plan, use a working session. If it is shared understanding or coordination, consider an update meeting. If the sentence is hard to finish, the purpose may be too vague—or the task may not need a meeting.

Then check whether the people needed for that output can attend. A useful invitation names the purpose, expected preparation, and the decision or artifact in view. It also tells invitees whether they are there to decide, contribute, advise, or listen. That distinction helps people prepare and prevents a room full of observers from being mistaken for a group with authority.

Finally, choose a record that fits the outcome. A decision needs a clear statement and an owner. A working session needs the artifact and its status. An update needs the commitments, questions, or dependencies that emerged. A shared document, meeting notes, or a project board can hold this record; the tool matters less than making the result easy for the responsible people to find and act on.

Hypothetical worked example: deciding whether to move a launch

Imagine a small team preparing to release a customer help page. The draft is complete, but a product change may make one section inaccurate. The team has a product lead who can confirm the change, a support lead who understands the likely customer questions, and a project coordinator who owns the release schedule. The team needs to choose whether to publish as planned or delay for revision.

The coordinator sends a brief containing the two options, the affected section, the information needed from the product lead, and the launch constraint: the page should not publish with incorrect instructions. The invite goes to those three people because each holds information or authority relevant to the choice. The meeting is framed as a decision session, not a general launch update.

During the conversation, the product lead clarifies whether the change is final, the support lead describes which instructions would be misleading, and the coordinator checks what each option means for the release plan. If the product change is still uncertain, the group can choose a temporary action, such as holding the affected section for confirmation, if that is acceptable to the decision owner. The notes record the choice, its condition, and who will update the page. The tradeoff is clear: a narrower meeting may leave other launch topics for a separate update, but it gives the necessary people a focused route to a decision.

Close with a record that lets work continue

Before ending, state the outcome in plain language and ask the relevant owner to confirm it. Capture actions with a named person and a clear deliverable; “follow up” is less useful than “send the revised instructions to the product lead for review.” If no decision was reached, record what is missing, who will obtain it, and when the group should reconsider the question.

Afterward, put the record where participants already coordinate work and share it with anyone who needs to act but did not attend. A meeting earns its place when its chosen format fits the task and its result survives beyond the conversation. When the next invitation is drafted, the first useful question is not who is free, but what must be different when everyone leaves.