Any message becomes a task with an owner, a due time, a priority and a status. View the whole board as Kanban columns, or as a list when you just want to work down it.
Work is identified in conversation. If capturing it means opening another application, re-typing the context and assigning it, that step happens when things are calm and gets skipped when they are busy.
Busy is exactly when it matters. So the useful measure of a task system is not what it can do, it is how many actions stand between noticing work and it having an owner. More than one or two and the system will be accurate during quiet weeks and wrong during the weeks that count.
Creating a task from a message keeps the context attached, so whoever picks it up tomorrow has the order in front of them rather than a description of it.
Every extra field is a reason not to create the task, and a task not created is work not tracked. Three carry almost all the value.
One name. Not a team, not a room. Anything assigned to a group is assigned to nobody, which is the same diffusion that makes "can someone check this?" go unanswered in a group of six.
One time. Not a priority label, an actual due time. Priorities are comparative and everything drifts to high; a time makes lateness visible, which is the entire mechanism.
A visible status. To do, In progress, Blocked, Done. If nobody can see the difference between finished and forgotten, you have a list rather than a system.
Kanban answers "what is the state of the day?" in one glance. Every task sits in its status column, so the shape of the work is visible without asking anyone.
List answers "what do I do next?" Same tasks, ordered by due time, worked down from the top.
Most teams use both, and which one is open is usually a good indicator of whether the person is planning or executing.
Most boards run To do, In progress and Done. That set hides the most expensive state a task can be in.
A blocked task looks identical to an in-progress one from outside. Nobody knows it is stuck, so nobody unblocks it, and it surfaces days later when somebody asks. Giving it a column makes stuck work visible at a glance, which is the point of having a board at all.
Some work cannot be described in a title. A damaged item, a mislabelled product, a picking error: showing it is faster and less ambiguous than writing it.
Tasks carry a description and images, so the person picking it up sees what the person who raised it saw.
The abstract case for task tracking is easy to nod along to and hard to picture. Here is the concrete version.
9:41. A low-stock alert lands in #daily-ops: a hoodie down to eight units, selling steadily. Somebody turns it into a task in two clicks. It arrives in To do with a name and a due time of two o'clock, and the product is already attached, so whoever picks it up is not hunting for it.
9:47. A customer asks to swap a size before dispatch. The order is shared into the room and becomes a second task, assigned to fulfilment, due before the courier collection.
10:15. The restock task moves to Blocked: the transfer needs a count from the pop-up shop. That single status change is the difference between a problem somebody knows about and a problem discovered at four o'clock.
2:00. Both tasks are in Done. The record of what happened, why, and who did it sits in the room where it was decided, which is where the next person will look.
Task systems fail in small teams for one reason: creating the task costs more than doing the job. Nobody opens a project tool to record a five-minute errand, so the board drifts from reality, and once it is untrustworthy people stop reading it.
One rule prevents the drift. If it will be done by someone other than you, or later than now, it becomes a task. Everything else you just do.
The common mistake is recording only the big things. Big things get remembered anyway. What gets dropped is the small item somebody agreed to in passing, which felt too minor to write down and was forgotten within the hour.
For the first fortnight, have one person convert what other people said they would do. Mildly presumptuous, and it establishes the norm faster than asking everyone to change their own behaviour, because people see the value before they have to do the work.
A board nobody prunes becomes a graveyard, and a graveyard is worse than no board because it looks like a system while being an archive.
Once a day, look at what is overdue and sort it into three. Still matters, so it gets a new time. No longer matters, so it gets closed. Or it has been carried three times, which means it is either not important or blocked by something nobody has named. That third pile is the useful one and it needs a decision rather than another date.
Closing dead items matters more than it sounds. A list containing things nobody intends to do is a list people stop trusting, and an untrusted list stops being read at all.
Being straight about the boundary. Store work is mostly interrupt work: unplanned, single-step, needed today. That is what this is built for.
Planned work is different. A replatform, a seasonal buying cycle, a multi-week build with dependencies and sequencing genuinely benefits from a tool that can show sequence, and no chat-based task list will do that well.
If you have both, the boundary that survives contact with a busy week is simple enough to apply without thinking: if it will not be finished this week, it goes on the board; otherwise it lives in the conversation. Anyone can answer that in a second, which is the only property that matters when people are busy.
Both views show the same tasks, so this is about what you are trying to see rather than a preference.
Kanban answers "where is everything?". Columns make a pile-up obvious: six items sitting in Blocked is visible in a glance in a way that no list makes visible. It is the view for a stand-up or for a quick look between other things.
List answers "what is next?". It sorts, so due time and priority line up and the top of the screen is the thing to do now. It is the view for actually working through the day.
Most people settle into list for their own work and Kanban when they want the shape of the whole board, and switching costs nothing because it is the same data underneath.
Yes, in two clicks, and the task keeps the context from the message including any attached order or product. You can also start a task fresh with the New task button.
Yes. Tasks appear as cards in To do, In progress, Blocked and Done columns, and the same tasks can be viewed as a list ordered by due time.
Both. Every task takes an assignee, a due date and time, a priority and a status, and can be filtered by any of them.
For genuine multi-week projects with dependencies, possibly. For same-day store work, a separate project tool usually adds a context switch without adding much, which is why the tasks live in the conversation here.
Yes. Filters cover assigned-to-me, created-by-me, status, priority and room, so the board can be narrowed to just what you own.
Free for teams up to five, and about two minutes to connect your store.