M360 Compass

M360 Compass · Management insights

After-action review for a small business setback

· 6 min

Two colleagues review a parcel and a sheet of paper at a dispatch counter.

An after-action review helps a small business learn from a setback by comparing the plan with what actually happened. Once the immediate work is under control, bring the people who handled it together and agree on one change to try on the next few cases.

Say a Friday order misses its pickup. The customer gets a new delivery time and everyone turns to Monday’s work. The shop remembers seeing the revised order early. Dispatch remembers hearing about it just before the truck arrived. Both accounts can be accurate. A short review gives the team a chance to put those accounts on the same timeline and see where it could have made a different decision.

How do you prepare a 30-minute after-action review?

Set the boundaries before sending the invitation. In a delivery review, start when the company confirmed the timing and stop when the truck left. Invite the people who made the promise, prepared the order and handled dispatch. If someone cannot attend, ask for their account in advance and show the group which parts they have yet to confirm.

Bring a few records the group can read together. A job ticket, the carrier’s pickup time and the customer update are a good start. This agenda gives the team time to reconstruct the event and still leave with a next step.

Suggested agenda for a short after-action review
TimeDiscussionOutput
5 minOriginal planExpected result
10 minWhat happenedShared timeline
10 minGaps and successesOne possible explanation
5 minNext trialOwner and review date

The World Health Organization uses structured discussion to examine how a response unfolded and what could improve. Indigenous Services Canada’s after-action report template makes room for a timeline, successes and challenges. Those resources were written for public health or emergency response teams. A small business can adapt the discussion and keep the record to a page. World Health Organization · Indigenous Services Canada

How do you build a timeline the team trusts?

Give everyone a minute to write down an observation and an uncertainty before anyone speaks. If you made one of the decisions under discussion, hear the other accounts before offering yours. Put verified times and actions on the timeline. Where accounts differ, record the difference and identify a record that might resolve it. An email timestamp can tell you when a message went out. It takes a separate check to learn when the person who needed it could read and act on it.

Fictional example. A 22-person sign shop has a 3:30 p.m. carrier pickup. At 1:10 p.m., customer service records the customer’s approval of a late change on the job ticket. At 2:20 p.m., the shop resumes work on the order. At 3:20 p.m., dispatch learns that the parcel will miss pickup. Customer service reaches the customer and arranges next-day delivery.

During the review, the team finds that the word “confirmed” on the ticket meant the customer had signed off to one group and the order was ready to ship to another. Ask each person what they could see when they opened the ticket and what they understood from it. Those accounts help establish whether the wording affected the decisions people made that afternoon.

Which practice should you keep, and what should you check?

Look for the decision that helped the team recover as well as the point where the plan went off course. In the sign shop, the customer call gave the buyer a clear next step once the delay was known. The team keeps that practice. It then looks at why dispatch found out so late. The status wording may have mattered. A long queue at the shop or a change to the pickup schedule could also explain part of the delay.

Pull a couple of similar tickets, including one where a late change still made the truck. Compare the information that reached dispatch and when it arrived. Maybe someone made a quick call in the successful case. If ownership of the delivery decision was unclear, use a RACI matrix to clarify who makes it. If the shop already had more work than it could finish, use the workload management guide to look at demand and capacity.

What would show that the next change helps?

In the fictional shop, try one rule on the next five orders that change on pickup day. At 2 p.m., the person preparing each order says whether it will be ready for the carrier. If readiness is still unclear, dispatch and customer service agree when they will make the next decision. Record how many of the five orders had a usable status at 2 p.m. and jot down any interruptions the check creates.

Meet again after the fifth order. Read through one case where the new signal helped somebody act sooner and one where it fell short, if there was one. If the check adds work without helping anybody make a decision, change the timing or the person who gives the update. A handful of cases helps you choose what to try next. A longer observation period can tell you more about missed pickups. The Institute for Healthcare Improvement describes how teams can test changes on a small scale, study the results and adjust the change before widening the test. Institute for Healthcare Improvement

How can M360 Compass help you follow through?

Use M360 Momentum to record the issue and the decision to run a trial. Assign the action to the person who will lead it and add a due date for the review. At the next team check-in, bring the order examples and decide whether to keep, adjust or stop the trial.

Before you close the next job that went sideways, write down the expected result and the earliest point when someone might have been able to act differently. Bring both details to the review. To see how your team could track the resulting action, request a M360 Compass demo.

Frequently asked questions

When should we hold the review?

Schedule it once service is stable and the people who handled the work are available. Capture records early, even if it takes a few days to get everyone together.

Can we review an event that went well?

Yes. Pick a practice the team wants to repeat. Describe what people did and the conditions that allowed it to work so the group can judge where else to try it.

What if people disagree about the cause?

Write down the competing explanations. Pick a record to check or an observation to make on the next job so the group can compare the explanations against evidence.

How many changes should we test?

Start with one change whose effect the team can observe. Agree on the cases it applies to, who will run the test and what evidence will inform the decision to keep it.