How to Run Agency Meetings That Lead to Clear Decisions

Decide what the meeting must accomplish.

Separate routine progress reviews, working sessions and strategic decisions. Combining them can leave specialists waiting through irrelevant discussion while important decisions receive too little attention.

A progress review should identify changes, dependencies and client actions. A working session should produce or resolve something specific. A strategic review should assess whether the plan still fits the business and what needs to change.

Relationship problems also deserve direct attention. Do not expect a rushed question at the end of a reporting call to resolve a recurring concern about ownership or communication.

Ask for a useful pre-read.

Request the material needed for the decision, delivered with enough time for participants to review it. State the question the meeting needs to answer.

For a budget decision, the pre-read should explain the proposed change, evidence, alternatives and consequences for other work. For a creative review, it should include the relevant brief and the stage of approval.

Avoid requiring a new presentation when the necessary information already exists in a clear shared document. Preparation should help participants make a decision rather than create another production task.

Invite people according to the agenda.

Include the decision-maker and the specialists whose knowledge is necessary. Give other affected people a clear summary afterward.

Atlassian's DACI guidance separates decision contributors from those who need to be informed. Applying that distinction can make attendance more purposeful.

If the approver cannot attend, decide whether the meeting can still produce useful work. Do not repeatedly hold a supposed decision meeting with nobody authorized to decide.

Discuss the evidence and the consequences.

Ask the agency to explain what changed, why it thinks that happened and what it recommends. Separate confirmed observations from hypotheses.

Give the agency relevant business updates before evaluating its recommendation. A sales-capacity problem or a change in inventory may alter the appropriate next step.

When discussion becomes a detailed problem for a small group, assign a separate working session. Preserve the main meeting for the decisions its participants were asked to make.

Record decisions in language people can act on.

A decision record should state what was agreed, who owns the next action and when it is due. Include the reason for material choices and any conditions attached to approval.

Distinguish a suggestion from an authorization. If the group discussed increasing spend but the authorized client owner has not approved it, record the decision as pending.

Ask the people responsible to confirm the actions before the meeting ends. Send the record to affected teams, especially when a choice changes their schedule or scope.

Use this agenda and decision log.

Adapt the prompts to the meeting's purpose.

• We are meeting to decide or resolve [specific matter].
• Participants should review [material] before [meeting time].
• [Decision-maker] can approve [matters] within [limits].
• The facts that changed are [observations], and the remaining uncertainties are [questions].
• The options are [options], with [costs, dependencies and consequences].
• We agreed to [decision] because [reason], subject to [conditions].
• [Owner] will complete [action] by [date].
• We will inform [affected people] and revisit the decision if [condition] changes.

After several meetings, examine whether decisions are being made and actions completed. If the same unresolved issue appears repeatedly, investigate authority, information or capacity rather than simply increasing meeting frequency.

Use the multi-agency guide when several suppliers attend, and the reporting guide when the evidence in the pre-read needs improvement.