Make group meetings produce decisions and next actions

Choose the decisions worth meeting for

Collect issues that require discussion rather than a simple status update. For each agenda item, state the question to resolve and the information needed. 'Choose the two comparison cases using the agreed criteria' gives the meeting a purpose. 'Discuss project' can consume the time without producing a decision.

Share the agenda and relevant material through the group's agreed channel in advance where possible. Ask members to add missing issues. Keep the amount of preparatory material proportionate; a meeting cannot depend on everyone reading a large new document that arrives moments before it begins.

Assign simple meeting roles

Choose someone to keep the discussion on the agenda and someone to record decisions. Rotate these jobs if practical so coordination does not always fall to one person. Agree how members will contribute, including remote participants. Check that the time and platform work with the group's availability and access arrangements.

Start by reviewing actions from the previous meeting. Ask whether each output is ready, blocked or changed. Keep the discussion factual. If an action is incomplete, identify what is needed and how the schedule is affected rather than using the review to assign blame.

Record decisions in plain language

For each resolved item, write what was agreed and the reason when it will matter later. Include the version or source the decision applies to. 'Use dataset B because it covers both selected years' is more useful than 'dataset discussed'. Keep alternative ideas only when the group may need to revisit them.

Mark unresolved questions separately and give them a next step. A question is not resolved merely because the discussion moved on. Decide who will obtain the missing information, whom they will ask and when the answer is needed. This prevents an uncertainty from silently becoming an assumption in the draft.

Make actions complete enough to follow

Give each action an owner, an output and a date. If another task depends on it, state that connection. For example, a chart review may need to finish before someone records narration. Avoid assigning an action to 'everyone' unless the expected individual response is clear.

At the end, read back the main decisions and actions. Let members correct misunderstandings immediately. Confirm the next meeting only if another discussion is needed, and note what should be ready by then. A short asynchronous update may be sufficient between more substantial meetings.

Use the record between meetings

Publish the note promptly in the shared project location and link it from the communication channel. Update the task plan to reflect decisions; do not leave two contradictory records. If someone was absent, give them a clear way to ask about the decisions and contribute to unresolved items.

Before the next meeting, use the record to identify genuine changes rather than repeating the same debate. Keep the notes concise enough that the group will consult them. At submission, retain any meeting record the course requires, while removing unnecessary personal information from material that will be shared beyond the group.

Your next steps

• Build the agenda around decisions.
• Record agreements separately from unresolved questions.
• Give every action an owner, output and date.
• Update the shared plan after the meeting.

Keep planning

• Arrange online group-study meetings people can participate in
• Make reading notes that help you build an argument
• Translate an assignment brief into writing decisions
• Turn tutor feedback into a plan for the next assignment