M360 Compass · Management insights
Meeting decision follow-up for small business teams

Meeting decision follow-up starts before the people who made the decision leave the room. In the last two minutes of a meeting, read back what the team agreed to do. Then ask who will take the next step and what the team will be able to see when the work is complete. A colleague hearing “try the new packaging” may picture a workshop trial while someone else starts planning a customer shipment.
A small team can use a shared log with one line for each commitment. Give an absent colleague enough context to pick up the work or ask the right person a question. Use the log for decisions that change what people do and for actions the team needs to revisit.
Five fields for meeting decision follow-up
- Decision. Record the choice and its scope. “Use the new insert on one pilot batch” gives the team a boundary it can work with.
- Action. Start with a verb and specify what the action produces. Preparing ten packages for a trial and authorizing them for shipment are separate steps.
- Owner. Name the person who will coordinate the work and raise problems that need help. Other people can contribute. When the same responsibilities cause confusion across several meetings, use M360 RoleAlign to start a discussion about who owns the work.
- Due date. Agree on a day. Include a time if someone needs the result to start another task. Ask the owner to confirm the timing and identify anything they need from others.
- Evidence of completion. Agree on what will close the action. A trial photo, measurement sheet or confirmation in a shared file may be enough. Name the reviewer when someone has to check that evidence before the team can proceed.
Canada’s Translation Bureau advises meeting recorders to capture decisions, actions and the people responsible in concise, factual minutes. The five fields here apply that guidance to the day-to-day work of a small team. Language Portal of Canada, Preparing the minutes
Read the commitment back before people leave
Take decisions one at a time. The meeting lead reads out the entry. The owner describes the deliverable in their own words and flags any condition that could change the timing. If two people describe different results, clarify the expectation while both are present. A decision to review measurements on Friday and a decision to implement a change on Friday call for different preparations.
If the team needs more information to decide, record the open question. Assign someone to collect the missing information and choose when the decision will return to the agenda. If a supplier’s answer is uncertain, agree on when the owner will get in touch again or when the team will consider a fallback. That step gives everyone a date they can plan around.
Afterwards, send the log link to the people whose work changes. If an affected colleague missed the meeting, add one sentence about what applies to their next shift or project. Keep the supporting detail in the usual project location and link it when the reader needs that context.
A pilot batch at a fictional workshop
Fictional example. At a machine shop, the production team notices marks on some parts after they are moved around the workshop. On Monday, the team decides to try a new insert on ten packages. Sofia owns the trial. She will prepare the packages and record the condition of each part before and after the move by 2 p.m. Thursday. Her record will show which packages contained a part with a new mark. Felix from quality will read it before Friday’s meeting.
On Tuesday, Sofia learns the usual transport bin will be unavailable until noon on Thursday. She records the dependency and flags that Felix may have too little time to review the results. At Wednesday’s check-in, the production lead reserves an equivalent bin for Thursday morning. She records that change alongside the action. The package count and observation method stay the same for this trial.
Sofia adds the completed sheet on Thursday. It shows one package with a marked part. Felix checks the record and the team closes the trial action. On Friday, the team makes a new decision to examine the contact point that may have caused the mark before using the insert on more packages. That decision gets its own action and owner. A colleague can look back at the original entry to understand the evidence behind it.
Review obstacles before reading out statuses
At the next meeting, use the first few minutes for blocked work and approaching deadlines. For each blockage, find out what the owner is waiting for, who else needs the result and who can make the next decision. Record the answer and when the team will revisit it. An action can still be within its deadline while already putting a colleague’s next step at risk.
Share evidence for completed actions ahead of time when people can check it quickly. Use the meeting to resolve exceptions or choose what happens next. When the same delay recurs, locate the point where it starts and change one part of the process in the next cycle. TeamSTEPPS, developed for healthcare teams, uses a debrief to review what happened and carry a lesson into the next plan. A workshop can borrow that sequence for its operational review. AHRQ, TeamSTEPPS debrief guidance
When an obstacle concerns someone’s workload or the support they need, make room for a one-on-one meeting. Keep the shared entry focused on the work dependency and when the team can expect an update.
Try the approach over two meetings
Choose two decisions at the next meeting that genuinely require follow-up. Write the entries while everyone is present. Then ask someone who missed the discussion to read them. Can that person tell what was decided, who is organizing the work and when they will know the result is ready? At the second meeting, look at which field prompted the most questions. Start by improving that field in the next set of entries.
M360 Momentum offers shared agendas, records of issues and decisions, and action tracking with owners and deadlines. Use those features to keep the decision and follow-up together. Agree within the team on the evidence you will review for each action. M360 Momentum
To see how a discussion, decision and action fit together in the platform, bring one entry from your log to a M360 Compass demo.
Frequently asked questions about decision follow-up
How do we record a deferred decision?
Write down the open question, the information needed to answer it, who will get that information and when the discussion will resume. Mark the decision as deferred so everyone can see which choice is still open.
Who closes an action?
The owner supplies the evidence the team agreed to use. When a colleague needs to check it before using the result, name that reviewer at the start. Both people can then work from the same understanding of completion.
What should an owner record when work is blocked?
Record the missing input, the effect on the deadline and the next step. Bring any decision the team needs to make to the next review. Raise it sooner if another commitment will be affected before the meeting.
Do we need full meeting minutes?
Use your organization’s minutes format when the meeting calls for it. A decision log can carry the resulting commitments into day-to-day work. Link back to the minutes so people can find the context when a decision needs to be revisited.
