Why a small team needs this more, not less
Routine feels like something larger organisations need. The opposite is closer to true. A big team has redundancy: if someone misses a stock problem, three other people might catch it. A team of three has no redundancy at all. Everything depends on the right person noticing the right thing at the right time.
The point of a routine is to stop relying on noticing. It converts vigilance, which is unreliable and exhausting, into a checklist, which is neither.
What follows is three fixed points. Total time is about twenty minutes a day. It assumes nobody is a full-time manager, because in a three-person store nobody is.
Morning: ten minutes, before anything else
Done by whoever opens. The goal is to know what happened overnight and what today requires, before the day starts making demands.
- Overnight orders. Not each one individually. Look for the exceptions: unusually large, flagged as risky, international if that is unusual for you, anything containing a product you know is tight on stock.
- Anything flagged. High-risk orders need a decision, and the decision is much cheaper before fulfilment than after. If something needs holding, hold it now.
- Stock below threshold. Which products crossed the line overnight. The question is not "are we low" but "does anything need ordering today", which is a different and more actionable question.
- Yesterday's open items. Anything assigned and not finished. This is where a task list with owners earns its keep, because otherwise this step relies on memory.
- Post the summary. Three or four lines where the team will see it. What needs attention, what is short, what is different about today.
That last step is the one people skip and it is the one that makes the rest work. A check nobody communicates only informs the person who did it, and in a three-person team the other two are the point.
Midday: five minutes, roughly after the lunch rush
Deliberately short. This is a checkpoint, not a meeting.
- Is anything from this morning still unhandled? If a flagged order is still sitting there at one o'clock, it is going to be sitting there at five unless someone says something now.
- Has anything changed? A product moving faster than expected. A supplier email. A customer issue escalating.
- Is anyone blocked? The most valuable question in the routine and the one people least like asking. In a small team being blocked feels like admitting you are stuck, so it goes unmentioned until the end of the day when it is too late to unblock.
Ask it explicitly and by name. "Anything stuck?" addressed to the group gets a reflexive no. Addressed to a person, it gets an answer.
End of day: five minutes, before the last person leaves
The handover, and the most valuable five minutes of the three if your team works shifts or split hours.
- What is unfinished and who owns it tomorrow? Unfinished work with no owner is dropped work with a delay.
- What is waiting on someone else? Supplier replies, customer responses, a courier investigation. These are invisible unless recorded, because nothing prompts you about something you are waiting for.
- What does tomorrow's opener need to know? Written down, not remembered. Memory does not survive a night, and it particularly does not survive a night when a different person opens.
We wrote a fuller treatment of this in the shift handover note, including a format that takes about ninety seconds.
Making it survive contact with a busy week
Routines die in predictable ways. Guarding against each one is most of the work.
- Attach it to something that already happens. Not a time, which slides, but an event: opening, after the lunch rush, before locking up. Times get missed and then the routine feels broken. Events are self-triggering.
- One owner per check, by name. "Someone checks stock" means nobody checks stock. This is the same diffusion problem that breaks group chats, applied to routines.
- Write the output somewhere shared. If the morning check happens in someone's head, the other two people gain nothing and the routine has no value beyond that individual.
- Let it shrink under pressure, but not stop. On a terrible day, two lines beats nothing. A routine that is all-or-nothing becomes nothing during the weeks it matters most.
- Review it monthly. Cut checks that never surface anything. A routine full of steps that never find problems trains people to perform it without attention, and then it stops finding the problems it would have found.
What this routine will not fix
Being honest about scope. This is a detection system. It catches problems earlier and makes handovers reliable.
It does not create capacity. If your three people are doing the work of five, the routine will surface more problems than you can act on, which is genuinely useful information but is not the same as solving them. Sometimes the correct output of a good routine is the realisation that you need a fourth person.
It also does not replace deciding who owns what. The routine assumes someone owns stock, someone owns customer issues, someone owns fulfilment. If those are ambiguous, the routine surfaces the ambiguity daily without resolving it.
Where the alerts fit
Two of the five morning checks can be automated in most setups: flagged orders and stock below threshold. Store Huddle surfaces both in Store pulse, which turns two acts of vigilance into two things that appear on their own.
That is worth doing, but it does not remove the routine. An alert nobody has a habit of reading is just a notification. The routine is what makes the alert land, and the alert is what makes the routine reliable. Our post on getting the threshold right covers the setup, which matters more than people expect: set it wrong and you get either silence or noise.
Common questions
Is twenty minutes a day realistic for a small team?
Yes, provided it is split into three short blocks attached to things that already happen. A single twenty-minute meeting is much harder to sustain than three short checks.
What if we all work different hours?
Then the end-of-day handover becomes the most important of the three, and it has to be written rather than spoken. Split hours are precisely the case this routine exists for.
Should the same person do the morning check every day?
Ideally whoever opens, so it attaches to the event rather than to a person. What matters is that it is unambiguous each morning who is doing it.
How do we stop it becoming a box-ticking exercise?
Review monthly and cut any check that has not surfaced a real problem. Checks that never find anything teach people to perform the routine without attention.
Do we still need this if we have automated alerts?
Yes. Alerts tell you something happened; the routine is the habit of looking and deciding. Without the habit, alerts accumulate unread.