Back to Blog & Insights

Leadership

Run a Meeting That Ends With a Decision

A small product team compares two packaging samples, makes a call on the test, and leaves with an owner, deadline and written record.

By WWA Editorial Team 4 min read
Over-the-shoulder view of two women comparing unbranded packaging prototypes in daylight

The packaging samples are on the table, launch timing is approaching and the conversation keeps circling. One colleague prefers Sample A’s closure. Another thinks Sample B better fits the product’s shelf presence. A third wants more customer input before anyone commits. The team has surfaced useful concerns yet still has no decision about what happens next.

This is a common meeting failure for an owner or team lead: treating discussion as progress when the actual job is to make a specific call. The decision question can be narrower than choosing a proven winner: which of the two samples should the team test for the launch? The question reduces pressure and directs the group toward a concrete next move. A test can answer a question without requiring unanimous enthusiasm for either prototype.

Set the decision before the conversation starts

Before sending the invitation, name the outcome in a sentence: “Choose Sample A or Sample B for the initial packaging test, and confirm the owner and timing for that test.” McKinsey’s meeting guidance says leaders should determine whether a meeting is needed, clarify its purpose and identify who will make the decision. A meeting for updates or ideas needs different participants and a different ending from one intended to make a call.

For the packaging conversation, the team lead might be the decision maker. The product manager could recommend an option based on launch requirements. A packaging specialist could advise on closure details, while the operations lead could explain what each sample means for production. The colleague coordinating the test is an execution partner. People can hold more than one role, especially in a small business, but decision authority should stay visible.

Invite people because they can improve the decision, carry it out or need to understand it. If a sales lead has relevant customer feedback, request it before the meeting or bring that person in for the portion where it matters. If the team only needs someone’s update, send it in writing. The smaller decision group can then stay accountable to the question on the table.

Use the agenda to create a stopping point

A useful agenda does more than list topics. Harvard Business Review’s Roger Schwarz describes it as a set of expectations about what should happen before and during the meeting. Participants could receive photos or physical samples beforehand, the test objective, known production constraints and the criteria for choosing. Those criteria might include closure usability, fit with the product, availability for testing and what the team can learn.

Give each item time. Duke University’s career guidance offers a practical model: a one-page agenda that identifies whether an item needs action, estimates the time required and uses a parking lot for issues outside the current purpose. The packaging team might examine both samples, weigh the agreed criteria and reserve a final segment for the call. A future redesign question belongs in the parking lot when it falls outside the choice of which sample gets tested now.

As discussion closes, the decision maker should summarize the trade-offs and state what remains unknown. Then make the call in plain language: “We will test Sample A.” The team should understand that this is a test selection, why Sample A was chosen and what evidence could change the next decision.

End by stating the action, owner and timing: the operations lead will request the test run, the product manager will define the feedback to collect and the team will reconvene when those inputs are available. Duke’s guidance recommends closing with a review of decisions and the action plan. Record the decision question, chosen sample, rationale, owners and next review point in the shared project record.

A decision meeting earns its time when people leave knowing what was decided, what remains unknown and who moves the work forward.

Sources