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.
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.