.png)
Run personal, team, department and org work on boards where every card carries the SOP, process map, checklist run or KPI it is actually about.
Pick who it is for, and name the columns the work actually moves through.
Owner, due date, priority, tags — and the SOP or KPI it is about, linked rather than described.
Assignment emails straight away, and a status change waits for the dragging to settle.
This is the whole difference. Every task tool holds a title and a due date; only the one that already owns your SOPs, maps, runs and KPIs can put them inside the card.
Link any Wikidoc artefact: document, process map, checklist run or module
Link the KPI the work serves, so “why are we doing this” has an answer
Upload PDF, XLSX, CSV and DOCX too, MIME-checked, up to ten per card
Most work is not company business. A personal board has an audience of exactly one, its creator, with no admin override, no assignees and no email.
Team and department boards resolve membership live against the org map
The kind is fixed at creation: a different audience is a different board
Every face that can see the board is on it, with the full list one click away
A description, dates, people, a priority, tags and a conversation. Plus a history that records what happened, rather than what the card looks like now.
Priority and due date, with an overdue state and a daily reminder
Watchers, threaded comments and @mentions that notify the right people
Subtasks inside the card, and an append-only trail of who moved it when
Paste a card into a message, a notice or a review and it opens on that card. It is the same URL the assignment email uses.
Copy link from the card itself or from its overflow menu
The link is not an access grant: outsiders get a request-access page
It survives the login redirect, so an emailed link still lands on the card
Dragging a card is the cheapest gesture in the product and the most expensive to email about. Sent naively, a feature like this ends its first week muted.
Assignment sends now, because being handed work is news
Status changes settle first, and you are never emailed about your own action
Mute one noisy board instead of unsubscribing from every board you have
Somebody on five boards needs an inbox, not five tabs. My tasks gathers everything assigned to you or watched by you, sorted by what is actually due.
On the Home dashboard too, beside the checklist runs and training due this week
Filter and search by assignee, tag, priority, due date or text
Export a board to CSV, and archive rather than delete when it is done
Opening a second site is forty tasks with an order to them, and each one carries the SOP it follows, so the second opening runs the way the first one did.
A checklist item that fails at open becomes a card with an owner and a deadline, still pointing at the run it came out of so nobody has to re-explain it.
Each new client is a board walked left to right, with the intake SOP on the first card and the engagement letter attached to the last one.
Servicing, calibration and stock reorders sit on a department board with real due dates, and each card names the KPI it protects.
Emily
Small Business Owner
Five: personal, shared, team, department and org. The kind is fixed when the board is created and cannot be converted, so if the work needs a different audience it is a different board.
Yes, and it is the one rule above all the others. A personal board has an audience of exactly one, its creator, with no admin override, no invitations, no assignees and no email.
No. Assignment emails immediately, because being handed work is news. A status change waits for the dragging to settle and is filtered for meaning, so a triage session is one message rather than thirty.
Every board and every card has a permalink, with a copy button on both. It is a link, not a grant: someone outside the board gets a page offering to request access, never a preview.
A description, dates, an author and assignees, a status, a priority, tags, watchers, threaded comments, subtasks, attachments and an append-only activity trail plus the Wikidoc artefacts and KPI it links to.
Yes. Every move has a keyboard and a menu path alongside the drag, and those same paths are what the mobile board uses. Drag-only would be an accessibility failure.
