The gap between saying and doing
“Can someone chase that supplier?” is not a task. It has no owner and no deadline, and in a group of five it reads as handled by everyone and is handled by nobody. This is the single most common way small teams drop work, and it has nothing to do with effort.
The fix is unglamorous: three fields.
The three fields
- One name. Not a team, not a role. A person. Shared ownership is unowned.
- One date and time. “Today” is not a deadline when the shift ends at six.
- One status. Not started, in progress, done. Three is enough. More is a taxonomy nobody maintains.
That is the whole system. Everything else a project tool offers is optional for a store team of under ten.
Why a separate board usually fails
Not because boards are bad. Because they are a second place. The conversation happens in chat, and then somebody has to remember to go and mirror it onto the board, and that person is busy. Within three weeks the board is a fiction and the team has quietly reverted to chat, now with the added cost of an abandoned tool.
Any system that requires re-typing what was just said will be abandoned by the second busy week.
Keep the task where the conversation is
If a task can be created directly from the message that prompted it, the re-typing step disappears and so does the drift. The context comes with it: whoever picks it up can see what was actually said, not a summarised version of it.
This is the model Store Huddle uses. A message becomes a task in two clicks, the task carries an assignee, a due date and time, a status and a priority, and the card stays in the room where the conversation happened. The task guide has the specifics.
A habit worth building
At the end of each day, one person scans the day's rooms and asks a single question of anything unresolved: does this have a name and a date? If not, give it one or explicitly decide it does not need doing.
Five minutes. It is the highest-leverage five minutes in a store team's day, and it works regardless of which tool you use.