You set up a board, add the stages, invite the team, and expect work to flow. A week later the questions begin. Does a task that fails review go back to Doing, or stay in Review with a comment? Who moves cards to Done? Can anyone add tasks, or only the lead?
The board cannot answer these. It shows where work is, but the agreements about how work moves live elsewhere: in people’s heads, in habits and in a few written rules. Teams that skip this step end up with a board that looks tidy and tells you little.
The board is a tool, not a process
A kanban board is a visual part of a bigger system. Much of that system is not visible on the screen: expectations, priorities, who decides what. If those are unclear, the board reflects the confusion. Two people can use the same stages and mean different things by them.
Rules worth writing down
Keep the list short. A handful of rules covers most situations. Consider writing down answers to these:
Stage definitions
For each stage, say what it means and what must be true to enter it. “In Review” might mean the author considers it finished and has attached any needed notes. “Done” might mean published and checked, not just written.
Who moves what
Decide who may move cards into each stage. Often the person doing the work moves it forward, while a reviewer moves it to Done.
What happens on failure
Agree on what happens when something fails review. One common choice: move it back one stage and add a comment explaining why, so the history stays readable.
Limits
Decide how many cards each busy stage may hold. KanbanWP lets you set a WIP limit per stage so the board enforces it.
Priorities
Say how priority is signaled and who can change it. Cards have a priority field, and labels can mark categories such as bug or client request.
Conversations
Decide where discussion happens. If comments belong on the card, say so; otherwise decisions scatter across chat and email. See task comments.
What to keep off the board
Equally important is what you leave out. Not everything deserves a card.
- Trivial tasks. Five-minute chores clutter the board. Use a personal list.
- Vague wishes. “Improve the website” is not a task. Break it down or leave it in a notes document until it is actionable.
- Sensitive details. Passwords, personal data and private client discussions do not belong in task descriptions. If a card is for your team only, mark it internal so clients do not see it.
- Long documents. Link or attach them rather than pasting them into a description.
How to introduce rules without a long meeting
- Run the board for a week with the stages you expect to use.
- Collect the questions that come up. Write each one down.
- Meet for thirty minutes and answer them. Resist the urge to cover every edge case. Aim for rules that handle most situations.
- Put the rules where everyone can find them, such as a short shared document that you link from a task on the board.
- Review after a month. Delete rules nobody follows and add one for any recurring confusion.
A short example
A four-person content team might settle on: five stages, a limit of three cards in Drafting, authors move cards to In Review, the editor moves them to Scheduled, and failed reviews go back to Drafting with a comment. That is five sentences, and it removes most of the arguments.
If you work with clients or contractors, do the same exercise with them, since their expectations are the ones most likely to differ from yours. Once the rules exist, the board becomes what it should be: an accurate picture of work, shared by everyone. To set one up, start with your first board.