How to run jobs and tasks on a kanban board
A kanban board shows every job and who has it, without anyone asking "what's the latest?" in the group chat. Here is how to set one up for a small business and keep it honest.

A kanban board is a board with one column per stage of your work, such as To do, In progress, Review and Done, and one card per job. To run one, match the columns to how work really moves, give every card an owner and a due date, limit the cards in each stage, and review the board weekly.
Ask three people in a small business where a job stands and you may get three different answers. The status lives in a WhatsApp group, a supervisor's notebook and someone's memory, so finding out means interrupting someone. Customers wait for replies, finished work sits uninvoiced, and nobody notices until month end. A kanban board fixes this by putting every job in one place where anyone can see its stage and its owner.
What is a kanban board?
A kanban board is a board divided into columns, one for each stage of a workflow, with each piece of work shown as a card that moves from left to right as it progresses. Anyone looking at it can see what is waiting, what is in progress, who owns it, and what is stuck.
Kanban is a Japanese word meaning "signboard". According to the Project Management Institute (PMI), the method was introduced as part of Toyota's just-in-time manufacturing in the early 1950s, where cards signalled demand so that production matched it. Teams outside factories adopted the idea because it works for any repeatable flow of work, from renovation jobs to design orders. In Bahasa Malaysia you might hear it called a papan kanban or papan tugasan.
The board can be a whiteboard with sticky notes for a team in one room, or a shared digital board when staff work across sites, branches or from home.
How do I set up the columns on a kanban board?
Make one column for each real stage that work passes through in your business, in the order it happens, and stop at the point where the job is paid or closed. Start with four to six columns; more than that becomes hard to read.
A generic board has To do, In progress, Review and Done. Most SMEs get more value by naming their own stages:
| Business | Suggested columns |
|---|---|
| Renovation contractor, Klang Valley | Quoted → Confirmed → Materials ordered → On site → Handover → Invoiced |
| Signage maker, Kuching | New order → Design → Customer approval → Production → Installation → Invoiced |
| Digital agency, Penang | Brief → In progress → Internal review → Client review → Live → Invoiced |
| Aircon service company, Ipoh | Booked → Scheduled → Job done → Report sent → Invoiced |
| Accounting firm, Johor Bahru | Records requested → Received → In preparation → Partner review → Delivered |
Two columns are worth adding in almost every business. A Waiting or Blocked column (or a clear "blocked" label) shows work held up by a customer or supplier. An Invoiced column at the end stops finished jobs from disappearing before they are billed.
What should go on a kanban card?
Each card is one job or one task, with a clear name, one owner, a due date and the information needed to do the work. If someone has to ask a question before starting, the card is missing something.
- A specific title: "Teratai Café: install menu lightbox," not "Café job".
- One owner: the person responsible for moving it forward, even when several people help.
- A due date: the date the customer was promised, or the internal deadline for this stage.
- Key details: the address, contact, scope notes, drawings or the accepted quotation.
- A checklist for multi-step tasks, so progress is visible inside the card.
- Comments, so decisions are recorded on the card rather than lost in a chat.
Keep personal data to what the job needs. A delivery address and a contact number are usually enough; identity card numbers and bank details don't belong on a work card.
In HumbleBear, each card in a Space can have an owner and dates, and a job's quotation, purchase orders and invoice can be linked to its card, so the paperwork travels with the work.
What is a work-in-progress limit, and why use one?
A work-in-progress (WIP) limit is the maximum number of cards allowed in a column, or held by one person, at the same time. When a column is full, the team finishes something before starting anything new.
It feels slower, but it usually speeds work up. PMI's guidance on controlling WIP notes that as the WIP limit goes above capacity, the throughput of the system declines, a principle that comes from queueing theory. Half-finished work also hides problems: ten jobs "in progress" can mean ten jobs waiting on the same overloaded person.
To set WIP limits:
- Count what each stage can really handle. If two installers can each manage one site at a time, the On site column's limit is two.
- Set the limit slightly above that to start, then lower it as the team gets used to finishing first.
- Make the limit visible, for example "On site (max 2)" in the column title.
- When a column hits its limit, help clear it before pulling new work in. A full Review column means someone should be reviewing, not starting new designs.
- Review the limits monthly. If a column is always full, it is your bottleneck; add capacity there or reduce work coming in.
WIP limits also protect people. A visible limit makes it harder to quietly pile a fifth urgent job onto someone who is already behind. See how to plan team workload.
How do I run a weekly kanban review?
Stand in front of the board, or share it on screen, and walk the columns from right to left: what is nearly done, what is stuck, and only then what can start. Fifteen to thirty minutes is enough for most small teams.
- Invoiced and Done: confirm finished jobs have been billed. Archive closed cards.
- Review and Handover: what's needed to finish these this week?
- Blocked: for each stuck card, agree one action and one owner to unblock it.
- In progress: is anyone over their limit? Are any due dates at risk?
- To do: pull new work in only where there is capacity.
Walking right to left keeps attention on finishing. For keeping meetings short and decisions clear, see effective meetings and handovers.
How does a kanban board help cash flow?
It shows work that has been delivered but not yet billed. Every card sitting between "Job done" and "Invoiced" is money the customer would pay if only they had an invoice.
Example (illustrative): A Kuching signage maker reviews its board on a Friday and finds six finished installations still sitting in Job done:
| Job | Value (RM) | Days since installation |
|---|---|---|
| Shop lot fascia, Jalan Padungan | 6,800 | 12 |
| Clinic lightbox | 2,400 | 9 |
| Café menu board | 1,350 | 8 |
| Office directory signs | 3,900 | 6 |
| Exhibition backdrop | 2,600 | 4 |
| Car sticker set | 1,350 | 2 |
| Total not yet invoiced | 18,400 |
With 30-day payment terms, every day a job waits to be invoiced pushes its payment back by a day. The fascia job's RM6,800 will now arrive at least 12 days later than it needed to. The fix is simple: invoice on the day of handover, and make "Invoiced" the column every job must reach. Our guide to accounts receivable collections covers what happens after the invoice goes out.
What are common mistakes with kanban boards?
The common ones are too many columns, cards with no owner, and a board that stops being updated so people go back to asking in the chat.
| Mistake | Fix |
|---|---|
| Ten or more columns | Merge stages; keep four to six |
| Cards with no owner | One name per card, always |
| Old cards never closed | Archive at each weekly review |
| Board updated only by the manager | Each owner moves their own cards |
| Status still asked in chat | Reply with the card, and update the card first |
| No limit on work in progress | Set a limit on the busiest columns |
Frequently asked questions
What columns should a basic kanban board have?
Start with To do, In progress, Review and Done. Then rename them to match your real stages, such as Quoted, Confirmed, On site and Invoiced for a contractor. Add a Blocked column, or a blocked label, for work waiting on someone else.
Is a kanban board only for software teams?
No. Kanban started in car manufacturing, and it works for any business where jobs pass through repeatable stages, such as renovation, printing, servicing, events or accounting. The columns change; the method doesn't.
How many cards should one person have in progress?
Usually two or three at most for project work, and often only one for tasks that need deep focus. If someone has many cards in progress, most of them are probably waiting. Set a limit and help them finish before adding more.
Should each card be a whole job or a single task?
Use one card per job when the board tracks jobs across the business, and one card per task when a team needs to see detailed work. Many SMEs use one board for jobs, with a checklist inside each card for the tasks.
How often should a kanban board be updated?
Owners should move their own cards whenever the work changes stage, and the team should review the whole board weekly. If the board is more than a day or two out of date, people stop trusting it and go back to asking in chat.


