Let the meeting end with a decision someone owns

What we found in the news

The NHS Institute’s 2010 improvement handbook (opens in a new tab) includes a plain instruction:

“Review your action plan regularly”

— Action planning, page 27

That older guidance gives us a starting point for thinking about recurring operational meetings. We are considering the work a discussion leaves behind, rather than claiming that a particular meeting format has been tested across care organizations.

Why this matters to us

A meeting can end with broad agreement and leave the next step surprisingly unclear.

Imagine a hypothetical program team discussing how to welcome people arriving after an activity has started. Everyone agrees the arrangement could be easier. The same issue returns at the following meeting because nobody was sure whether reception or the activity lead would take it forward.

At genus, we are interested in the connection between useful conversation and dependable action. The colleagues in this example may have understood the problem very well. The missing piece was an agreement about what would happen next.

Decide what the meeting is there to do

Before inviting everyone, identify the decision or question that needs their time. Some updates can be read beforehand. Some situations need discussion because people hold different parts of the picture.

Ask who can make the decision, who will carry it out, and whose experience is needed to make it sensible. Including every possible person can make a meeting expensive without making the decision better.

For the late-arrival example, reception and the activity team both matter. So does the participant’s experience of joining. The team could seek that perspective through an appropriate conversation rather than assuming staff can describe it fully.

If an essential decision-maker cannot attend, be clear whether the group is preparing a recommendation or making an agreement. Those are different uses of the time.

Describe the action in terms of the work

An instruction to improve communication leaves much to interpret. A more usable action identifies what someone will do, what they need, and when the group should hear back.

In our hypothetical service, a colleague might agree to propose a welcome arrangement with reception, check it with participants who want to contribute, and bring the options to the next planning discussion.

Check that the owner accepts the task and has the authority and time to do it. Naming someone in meeting notes does not settle those questions.

If two teams need to agree, identify who will bring them together. If a budget decision is required, record that dependency. Work can stall when an action sounds complete but the next approval is hidden inside it.

Keep records proportionate. A useful note preserves the decision and responsibility without copying unnecessary personal information into a wider circulation.

Begin the next discussion with what happened

Return to the agreed action. Was it carried out? What did the colleague learn? Does the proposed next step still fit?

An action may reasonably change after someone speaks with participants or examines the practical arrangements. Ask for that explanation rather than treating every change of direction as failure.

If the same task repeatedly remains unfinished, investigate the conditions around it. Perhaps it has no protected time. Perhaps the person assigned to it cannot make the required decision. Rewriting the due date may simply hide the issue for another week.

Also ask whether the meeting itself remains useful. A group may need to meet more often during a change and less often once the arrangement works. The calendar should reflect the work rather than determine it indefinitely.

What this means for the people you serve

People may experience the consequences of an unresolved action long after the meeting ends. A clear welcome, a corrected timetable, or an answered question can matter more than knowing that a committee discussed it. Invite people to check whether the resulting arrangement works for them.

The genus connection

Configured genus community tasks and calendars can help people organize agreed work today. Authorized staff can also use the Partner Portal to review relevant operational context.

These tools depend on the enabled modules and local process. Recording a task does not establish that the person has accepted it or has authority to act. The meeting still needs to make those agreements clear, then use the available record to return to them.

One question for your next team meeting

Which action from our last meeting can we describe with a clear owner and a next step that person has accepted?