Kanban Method for Business: A Practical Guide

Say "Kanban" and most people picture a board covered in colourful sticky notes. The board really is part of the method, but it is the easy part. Plenty of businesses open a board in Trello or monday.com, move every task onto it, and a month later find themselves staring at two hundred cards with nobody quite sure what is actually being worked on.

Kanban is first and foremost a way to see work as it really is, limit how many things are in progress at once, and improve the process one step at a time. Done properly, fewer things get stuck, your team stops jumping between tasks, and you can tell a client with confidence when something will be ready.

In this guide, we cover:

• what Kanban is and where it came from;
• the six practices of the method and the metrics worth tracking;
• how Kanban differs from Scrum and when each one fits;
• how to get started in six steps, with sample boards for different kinds of business work;
• which mistakes undermine the method and which tools help you put it into practice.

What Kanban is and where it came from

Kanban is a method for managing work built on two ideas: make the work visible to everyone, and limit the amount of work in progress at any given moment. The Japanese word translates roughly as "signboard" or "card".

The method was born in Toyota's factories in the middle of the last century. Engineer Taiichi Ohno was looking for a way to produce only what the next stage of the production line actually needed, and physical cards signalled when one station required parts from the one before it. In the early 2000s, David J. Anderson adapted the principle to knowledge work, mainly software development, and from there it spread to marketing, design, customer service and operations.

Kanban is usually grouped with the Agile family of methods. If you are still deciding how to run a whole project, we have a guide comparing the main approaches: Agile vs Waterfall.

A task board is not yet Kanban

The distinction matters because it explains why so many attempts fail. A board with "To do", "Doing" and "Done" columns is only a display. It becomes Kanban when it also has clear limits on work in progress, written rules for moving between stages, and regular measurement of how work flows. Without those three things, your board is just a to-do list with nicer styling.

The six practices of Kanban

The professional literature describes six practices. The first three concern day-to-day work, and the last three concern how an organisation manages and improves itself.

1. Make the work visible

Every task is a card, and every stage of the process is a column. The card says what needs doing, who owns it and what is needed to do it, including files and links. Columns should reflect your real process. For a business that builds websites, they might be "Scoping", "Design", "Development", "Testing" and "Client approval".

2. Limit work in progress

This is the practice that separates Kanban from an ordinary board. It is known as a WIP limit, short for Work In Progress. For each column, you decide how many cards it may hold at once. If "Testing" allows three cards and three are already there, nobody moves a fourth one in. Instead, whoever has finished something helps clear the bottleneck.

The limit feels artificial at first, but the logic is simple: the more things you have open, the later each one finishes. Switching between tasks costs time and focus, and work that has been started but not finished creates no value for anyone.

3. Manage the flow

The goal is for tasks to move across the board at a steady, predictable pace. Kanban does not mean everyone picks whatever they feel like. Before a task enters the workflow, decide who needs it, whether it is really necessary and how urgent it is. From there until completion, watch where cards pile up: a stack in one column is a sign of a bottleneck in the process. If urgent requests keep pushing everything else aside, also read our guide on how to stop firefighting.

4. Make the rules explicit

Everyone on the team should know when a task is ready to move on. Write down what counts as "done" at each stage, who may add tasks to the board, and how genuinely urgent work is handled. For example: a page moves from "Development" to "Testing" only after it has been checked on mobile and all its links work. A written, visible rule saves arguments and saves work bouncing back and forth.

5. Build feedback loops

The literature describes seven kinds of recurring meetings, including risk reviews, strategy reviews and replenishment meetings. A small business does not need all of them. Two are usually enough: a short meeting in front of the board a few times a week, where you talk about what is stuck rather than what everyone did, and a monthly review of the process itself.

6. Improve collaboratively, through experiments

Kanban starts from what already exists. You do not abolish roles or change everything in a day. You identify one problem, try a small change, measure it and decide whether to keep it. The people doing the work are also the ones proposing improvements, which is why the changes tend to stick.

The metrics worth tracking

You do not need a complicated dashboard. Three numbers give you a good picture:

• Lead time: the total time from the moment you commit to a task until it is delivered. This is the number your client cares about.
• Cycle time: the time from when work on a task actually begins until it is finished. A big gap between this and lead time means tasks spend a long time waiting in the queue.
• Throughput: how many tasks are completed per week. It lets you give estimates based on data rather than gut feeling.

Kanban vs Scrum: which one suits you

Both methods are Agile, but they follow different logic.

Scrum works in fixed sprints, usually two weeks long. You plan in advance what goes into each sprint, and there are defined roles and regular ceremonies. It is a good fit for building a new product, when you have a stable team and clear goals for each cycle.

Kanban has no cycles. Tasks flow continuously, priorities can change every day, and you do not have to add any new roles. It works well when work arrives without a fixed rhythm: customer support, website maintenance, marketing, campaigns or a studio handling several clients at once.

One point is worth being precise about: Kanban has no sprints, but that does not mean it has no deadlines. You can set a due date on a card, and a task with a hard date can get its own fast lane. If a project requires long-range planning with fixed milestones, Kanban alone will not be enough, and it is worth combining it with a project roadmap. Many teams work with a hybrid: quarterly planning or a roadmap at the top, and Kanban for day-to-day execution.

How to get started: a six-step plan

Start small, with one team and one process. Trying to build perfect Kanban from day one usually ends with a board nobody updates.

Step 1: Map the process as it really is

Sit down with your team and describe how work actually moves through your business from the moment it comes in until it is finished. Not how it should work, but how it works in practice, including the time spent waiting for a client or a manager to approve something.

Step 2: Build a simple board

Turn the stages into columns. Five to seven columns are enough for most businesses. Add a "Backlog" column at the start of the board, followed by a small "Selected for work" column that holds only what you have decided to do soon.

Step 3: Move your existing work across

Put everything currently in progress on the board, even if the amount is uncomfortable to look at. Write cards of a sensible size: not "build a website", and not "change a button colour" either, but tasks that can be finished in anything from a day to a few days.

Step 4: Set limits before you begin

Do not postpone this step. A common starting point for a team of four to six people is two or three cards per column, adjusted to what you see in practice. If you never feel the limit, it is too high. If everything grinds to a halt, it is too low.

Step 5: Write down the rules

For each column, define what it takes to leave it, and decide who adds work to the board and what happens when something truly urgent comes in. Keep this somewhere visible, such as the top of the board.

Step 6: Measure and improve

Give your team two or three weeks to get used to the board, and only then start changing things. Once a month, check your average delivery time and where cards are piling up. Choose just one problem to work on the following month.

Examples: what a Kanban board looks like in a business

Columns vary according to the kind of work. Here are three examples you can start from:

• Website maintenance: Requests, Selected for work, In development, In testing, Client approval, Live.
• Content and marketing: Ideas, Selected, Writing, Design, Approval, Scheduled, Published.
• Customer enquiries: New, In progress, Waiting on customer, Waiting on third party, Closed.

Pay attention to the waiting columns. "Waiting on customer" and "Client approval" expose one of the most common causes of project delays, and they let you see how long a task sits idle with nobody working on it at all.

What to plan for in real-world teams

A few practical things are worth considering when you design your board:

• Holidays and absences. During holiday periods, or when part of the team is away, lower your WIP limits rather than overloading the people who remain. A visible board also makes it easier to hand tasks over when someone is out, especially if colleagues in different countries follow different public holiday calendars.
• Requests in chat. Plenty of requests arrive through WhatsApp, Slack or Teams and never get recorded anywhere. Set a simple rule: a request that has not become a card does not exist. That way, it also cannot quietly disappear.
• Distributed teams. If your team spans several languages or time zones, agree on one working language for column names and rules, and make handovers explicit on the card so nobody has to wait for a colleague to wake up to learn what happens next.
• Privacy. Cards for customer enquiries often contain phone numbers and personal details. Set permissions and do not share such boards through an open link. If you handle personal data of people in the EU, the GDPR applies to information held in task management tools as well, including how long you keep it. This is general information, not legal advice.

Advantages and disadvantages

The advantages

• Flexibility. You can start without changing roles and adjust priorities every day.
• Transparency. Anyone joining the team can see what is going on at a glance.
• Less context switching. A WIP limit lets people concentrate and finish.
• Visible bottlenecks. Cards piling up in a column point straight at the problem.
• Data-based estimates. After a few weeks of measuring, you can promise delivery times with more confidence.

The disadvantages

• No built-in cycle that forces you to finish. Without due dates where they are needed, important but non-urgent tasks can be pushed back again and again.
• Prioritisation is an ongoing job. Without someone responsible for the queue, people take the interesting tasks and the rest are left hanging.
• It takes discipline. A board that is not kept up to date loses people's trust very quickly, and the method goes with it.
• Less suited to building a first product. When you need to point a team at a first release with a clear target, sprints sometimes give better focus.

Common mistakes to avoid

• A board without limits. This is the most common mistake. Without a WIP limit, you have a nice to-do list, not Kanban.
• Too many columns. A board with fifteen columns creates maintenance work of its own. Start simple.
• Cards that are too big. A card that sits in the same column for three weeks teaches you nothing. Break it into pieces.
• An endless backlog. A list of ideas with hundreds of items is a graveyard. Clean it out once a month.
• Going around the board. If a manager assigns tasks directly in chat, the board no longer reflects reality.
• Measuring people instead of the process. Metrics exist to show where the process gets stuck, not to compare employees. The moment they are used for individual appraisal, the data stops being reliable.
• Changing everything at once. Go back to the basic principle: one change, one measurement.

Kanban tools and automation

The tool matters less than the rules. Even so, the right one removes a lot of manual work. These are the common options:

• monday.com: a work management platform with a Kanban view, automations and templates for sales, marketing and operations.
• Trello: the simple way to get started with boards, well suited to small teams.
• Asana: a board view alongside lists and timelines, a good fit for marketing and content teams.
• Jira: built for development teams, and it lets you set a limit per board column.
• Notion: boards inside a workspace that also holds your documents and knowledge.
• ClickUp and Microsoft Planner: popular alternatives, with Planner particularly convenient if your organisation already runs on Microsoft 365.

Not every tool has a built-in WIP limit. If yours does not, put the limit in the column name and agree as a team to respect it.

Where automation saves the most

Most of the manual work around a board is repetitive, which makes it easy to automate with tools like n8n, Make or Zapier:

• an enquiry from a website form becomes a card in the "New" column, with all the details filled in;
• when a card moves to "Client approval", the client gets a message with a link to review;
• a card stuck in the same column for more than two days triggers an alert to its owner;
• once a week, the team receives a summary of what was completed and what got stuck;
• when a deal closes in your CRM, the client's onboarding cards are opened automatically.

How RJL Studio can help

We build websites and connect them to the systems a business runs on, so an orderly process for requests, testing and approvals is part of every project we take on.

If your leads come in from different sources and fall through the cracks, we can connect your website, your CRM and your work board with automation and integrations: every enquiry becomes a card, every status change notifies the right person, and the data stays in one place. We also build and maintain Webflow websites using an orderly process of requests, testing and approvals, much like the board described above.

Want to find out what you could automate? Talk to us and we will put together a short plan with you.

Frequently asked questions

Is Kanban only for software companies?

No. The method started in manufacturing and is now used by marketing, design, customer service, finance and HR teams. It fits almost any work that can be described as a sequence of stages, especially when tasks arrive unpredictably.

How many columns should a board have?

Most businesses get by with five to seven columns. Start with the real stages of your process, and add a column only when you need to see a wait or a stage that is currently hidden.

What do you do with an urgent task when the board is full?

Define an exception lane in advance, such as a separate row at the top of the board limited to one card at a time. Only let in what meets your written definition of "urgent", such as a website that has gone down. If everything counts as urgent, the lane loses its meaning.

Does Kanban replace Scrum?

Not necessarily. They are two approaches suited to different kinds of work, and you can combine them. When tasks arrive continuously and priorities shift often, Kanban feels more natural. When you are building a product in planned cycles, Scrum provides a stronger framework.

How long does it take to see results?

It usually takes two to three weeks for a team to get used to updating the board, and that is when bottlenecks start to show. A measurable improvement in delivery times typically takes two to three months of working with metrics and small changes. The pace depends mostly on consistency, so keep to the rules even in busy weeks.