Most teams pick their first work tool because someone used it at a previous job. A board goes up, the columns get named To do, Doing and Done, and it works well for the project at hand. Then someone adds a column called "Waiting for approval", and the board slowly becomes the place where purchase requests, time off and new laptops also live.
That is usually when the trouble starts. Not because boards are bad, but because a board and a workflow solve different problems. A board shows work so a team can pull it forward. A workflow moves a request along a fixed path, to the right people, with the right information, and keeps a record.
Key takeaways
- A kanban board makes work visible so a team can manage its flow. A workflow defines who does what, in what order, with what information.
- Boards fit varied, collaborative work like content, design and projects. Workflows fit repeatable requests with approvals, deadlines and an audit trail.
- The warning sign is a "Waiting for approval" column: on a board, anyone who can edit can move the card, and the move is not a recorded decision.
- Most teams need both, for different kinds of work.
This guide compares kanban vs workflow for internal processes: what each one is, where each one wins, and a quick test to decide which one a given piece of work needs.
What is a kanban board?
The word comes from the Toyota Production System, where a kanban was a card that said which parts were needed, where and when, so each process produced only what the next one used. Office and software teams later borrowed the idea and turned it into a board.
A kanban board has three parts:
- Columns for the stages of work, such as Backlog, To do, In progress, Review and Done
- Cards for each piece of work, with an assignee, a due date, comments and attachments
- WIP limits (work in progress): a cap on how many cards can sit in a column, so the team finishes work before starting more
The central idea is pull. People take the next card when they have capacity, instead of work being pushed onto them. And because everything is visible, bottlenecks are obvious: if Review holds twelve cards, everyone can see where work is stuck.
Trello, Jira, Asana and monday.com all offer boards of this kind. Trello is built around boards, lists and cards. Jira's kanban boards let you set a minimum and maximum number of items per column. Asana and monday.com let you view the same work as a board or in other layouts, such as a list or a calendar.
What is a workflow?
A workflow, in the sense used here, is a defined path a request follows from start to finish. Each step has:
- An owner: a person, a role, or someone relative to the request, like the requester's manager
- Information: the fields that must be filled before the step is done
- An action: complete, approve, reject or send back
- A deadline: with a reminder or escalation when it passes
- A record: who did it, when, and what they decided
The same steps happen in the same order every time. Nobody decides where the request goes next by dragging it; the rules decide. If a board is about pull, a workflow is about routing: when one step is done, the next owner is told it is their turn. Our approval workflow guide covers the approval side in depth.
Kanban vs workflow: side by side
| Kanban board | Structured workflow | |
|---|---|---|
| Question it answers | What is everyone working on, and where is it stuck? | Whose turn is it, and what do they need to decide? |
| Unit of work | A card, mostly free text | A request with a form defined in advance |
| How work moves | Someone drags the card to the next column | The owner completes the step and the rules route it |
| Stages | Columns the team can change at any time | Steps defined once and applied every time |
| Who can act | Usually anyone who can edit the board | Only the owner of the current step |
| Approvals | A column or label, by convention | A step with approve, reject and send back |
| Deadlines | A due date on the card | A deadline per step, with reminders and escalation |
| Record | Comments and card history, if the tool keeps it | A timeline of every action and decision |
| Who starts work | The team, from its backlog | Anyone, often people outside the team |
| Best for | Projects, creative work, varied tasks | Repeatable requests, approvals, compliance |
The line is not absolute. Board tools have added automation rules, custom fields and approval features over the years: Trello has built-in automation, and Asana has an approval task type with approve, request changes and reject. The real difference is what the tool is built around. A board is built around visibility and flexibility. A workflow is built around rules and a record.
Which work fits a board, and which fits a workflow
Some examples, to make it concrete:
| Work | Better fit | Why |
|---|---|---|
| Marketing content calendar | Board | Every piece is different, and the team pulls work as capacity frees up |
| Software development backlog | Board | Flow and WIP limits matter more than fixed routing |
| Hiring pipeline (candidates) | Board | Candidates move through stages at their own pace |
| Job offer approval | Workflow | Salary needs a yes from specific people, on record |
| Purchase request | Workflow | Approvers depend on the amount, and finance needs the trail |
| Expense reimbursement | Workflow | Same fields every time, approval, then payment |
| Vacation request | Workflow | Requested by anyone, approved by their manager |
| System access request | Workflow | Approval by the system owner, and proof for access reviews |
| Final approval of a published ad | Workflow step | The content is made on a board, the sign-off is recorded |
The pattern: work the team does for itself, where every item is a little different, fits a board. Requests from other people that repeat and need a yes fit a workflow. The purchase approval workflow is the classic example of the second kind.
A quick test
Ask five questions about the work:
- Does it happen the same way every time?
- Does someone outside the team start it?
- Does someone specific have to approve it?
- Will anyone ever ask "who approved this, and when?"
- Does the same information need to be collected every time?
Mostly yes: build a workflow. Mostly no: a board is probably the better tool.
What goes wrong when approvals live on a board
Approvals on a board work while the team is small. These are the problems that show up as it grows.
The card is moved by the wrong person
On most boards, anyone who can edit the board can drag a card. If "Approved" is a column, then approval means whoever dragged the card there: the requester, a colleague tidying up, or a slip of the mouse. Example: a $4,800 software renewal lands in Approved, purchasing pays it, and the department head who should have decided never saw it.
There is no clean record of the decision
Some tools log card moves, but a move is not a decision. It does not capture the amount at the time, the reason for a rejection, or whether that person was allowed to approve that amount. Six months later, someone is scrolling through comments to find out.
The important fields live in comments
Amount, cost center, supplier and dates end up in the description or in comments, written differently every time. You cannot total, filter or route by amount when the amount is a sentence. Many board tools support custom fields, but nothing usually stops a card from moving with them empty.
Nobody is told it is their turn
A card in a column waits for someone to notice it. Approvers who do not live in the board, like the CFO or a department head, rarely open it. Reminders and escalation have to be set up by hand, if the tool allows it at all.
The rules live in people's heads
"Anything over $5,000 needs the CFO" is a convention on a board, not a rule. Nothing enforces it. If your approvals depend on amounts, the rules belong in an approval matrix that the workflow applies automatically.
Most teams use both
The honest answer to kanban vs workflow is that you should not pick one for everything. Marketing plans content on a board, and the ad spend approval goes through a workflow. Engineering runs its work in Jira, and production access requests go through a workflow. The board is for the team's own work. The workflow is for requests that cross teams, need a yes, or need a record.
Signs something is in the wrong place:
- On a board, but it should be a workflow: there is a "Waiting for approval" column, people ask "did anyone approve this?", required information is chased in comments, and the same card is copied as a template every time.
- In a workflow, but it should be a board: steps are skipped or reordered most of the time, every request is different, and people spend more time filling forms than doing the work.
Frequently asked questions
Is kanban a workflow?
Kanban visualizes a workflow: the columns are the stages work goes through. But a board does not usually enforce it, since anyone who can edit the board can move a card to any column. A structured workflow defines the steps, who owns each one and what has to be filled in before the request moves on.
Can you handle approvals in Trello, Jira or Asana?
Yes, to a point. Teams use a dedicated column, automation rules or add-ons, and Asana has an approval task type. That works for light, informal sign-offs. For approvals that depend on the amount, need a record for audits, or involve people who never open the board, a dedicated workflow is usually easier to keep correct.
What is a WIP limit?
A WIP (work in progress) limit caps how many cards can sit in a column at the same time. When a column is full, the team finishes or unblocks existing work before pulling more. In some tools the limit is a visual warning rather than a hard block; in Jira, for example, the column header changes color when the limit is exceeded.
Running it in Easyflow
Easyflow has no boards, on purpose. A process is a linear list of steps: the first step is a form filled by whoever starts the request, and every step after it has an owner and a deadline, with reminders and escalation when it runs late. Approvers decide from the email (a confirmation page opens first), can send a request back for changes, and approval limits pick the approvers by amount. Every request keeps a full timeline of who did what and when, and Insights shows volumes, lead times and late steps per process.
The gallery has Purchase request, Expense reimbursement, Vacation request, Access request and Content approval ready to adapt. Keep your board for projects, and send the requests through a workflow.
Before building any workflow, write the process down first: our guide on how to document a business process includes a template you can copy.