Quotes waiting to be priced, jobs waiting for materials and finished work waiting to be invoiced may not show up in a weekly report. The Kanban method is a way of managing work by making it visible on a board, limiting how much is in progress at once and improving how it flows.
Kanban shows where work is waiting. This guide explains where the method comes from, its core practices, how a Kanban board and work-in-progress (WIP) limits work, which measures it uses and how it compares with Scrum, with examples from heating, ventilation and air conditioning (HVAC), electrical contracting and renewables businesses turning over £1M–£50M.
What is the Kanban method?
The Kanban method is a management approach that makes work visible, controls how many items are in progress and improves the flow of work over time. It is applied to the process a team already runs, rather than replacing it, and it suits any workflow where items move through a series of stages.
The Kanban Guide (May 2025 edition) states that “Kanban is a strategy for optimizing the flow of value through a process.” Kanban University’s Official Guide to The Kanban Method says Kanban “is not a methodology nor a process framework” but “a management method or approach that should be applied to an existing process or way of working.”
Kanban sits alongside the principles of the Agile Manifesto, which favour frequent delivery and regular reflection; how they apply outside software is set out in the 12 agile principles for business. Kanban and Scrum are both approaches teams use to put agile methodology into practice.
Where does the Kanban method come from?
The Kanban method has its roots in Lean Manufacturing and the Toyota Production System, where a kanban card or board signals when a process should make or move parts; Toyota’s “supermarket method” of 1954 evolved into its Kanban system. Kanban University bases today’s Kanban method for knowledge work on David J Anderson’s 2010 book.
Toyota’s own history, 75 Years of Toyota: Supermarket Method, records that “in 1954, the ‘supermarket method’ was introduced”, based on hints from a report on a Lockheed aircraft plant, with the earlier process acting as the “supermarket” from which the next process takes what it needs. The same page says the supermarket method “evolved into the Kanban System with the addition of a production instruction sheet known as the Kanban”.
The Lean Enterprise Institute’s lexicon entry on kanban defines a kanban as “a signaling device that gives authorization and instructions for the production or withdrawal (conveyance) of items in a pull system”, and notes that the word is Japanese for “sign” or “signboard”. Toyota’s production system page sums up Just-in-Time, the principle behind the supermarket method, as “Making only what is needed, when it is needed, and in the amount needed”.
What are the core practices of the Kanban method?
The core practices of the Kanban method, as Kanban University lists them, are six: visualise, limit work in progress, manage flow, make policies explicit, implement feedback loops, and improve collaboratively and evolve experimentally. The separate Kanban Guide names three practices of its own: defining and visualising, actively managing and improving a workflow.
- Visualise. Every item of work, and the stage it has reached, is shown on a board that the whole team can see.
- Limit work in progress. Each stage, person or the whole system has a maximum number of items, so new work starts only when there is capacity.
- Manage flow. The team watches how items move and acts on those that are stuck, rather than on how busy people look.
- Make policies explicit. The rules for moving an item, such as what “ready to invoice” means, are written down and agreed.
- Implement feedback loops. Kanban University’s guide names the usual means as “the board, metrics, and a set of regular meetings and reviews which are referred to as cadences.”
- Improve collaboratively, evolve experimentally. Changes to the workflow are made in small steps and checked against what happens.
How does a Kanban board work in a contracting business?
A Kanban board works in a contracting business by showing each job, quote or task as a card in a column for its current stage, from start to finish. Cards move across as work progresses, so anyone can see what is waiting, what is in progress and where items are building up.
The Kanban Guide says “The visualization of a DoW is a Kanban board”, where the Definition of Workflow (DoW) is the team’s shared understanding of how work flows. It does not prescribe a layout, but sets out six minimum elements: a definition of work items, start and finish points, one or more states in between, a method for controlling WIP, explicit policies for how items move, and a service level expectation. The GOV.UK Service Manual page on agile tools and techniques, which does not name Kanban, describes a similar team wall that “may be a physical wall in an office or a digital board” and “shows what your team has done, what you’re currently working on and what’s still to do.”
For an HVAC or electrical contractor, a board for the office side of a job might run through seven columns: enquiry, survey booked, quote being priced, quote sent, materials ordered, ready to schedule, and complete and ready to invoice. Those stages broadly follow the first six steps of the quote to cash process. Workflow architecture design decides the stages, hand-offs and owners that the board reflects. A visible board is also one of the building blocks of an agile operating model for a contracting business.
How do work-in-progress limits work in the Kanban method?
Work-in-progress limits work in the Kanban method by capping how many items can sit in a stage, with a person or across the whole board at one time. When a column is full, the team finishes or unblocks existing items before pulling in new ones, which helps keep queues short and shows where work is stuck.
The Kanban Guide states that “Kanban system members must explicitly control the number of work items in a workflow from started to finished.” Kanban University’s guide says WIP limits can be set per work state, per person, per lane, per type of work or for a whole system, and that they are “key to establishing a pull system”, in which work is pulled only when capacity exists. It calls “Stop starting, start finishing” a good mantra to remember.
In an office workflow, a limit of, say, five quotes being priced at once means an estimator finishes or hands back a quote before opening a new one. Why limiting work in progress shortens the time each job waits is explained in how work in progress affects workflow efficiency. A first limit is a starting point to adjust, not a target.
Some items need different handling. Kanban University describes classes of service, a way of treating defined types of item differently, with an “expedite” class that may pass through even when the WIP limit is fully used. For a contractor, an emergency breakdown call is an example of work that may need its own lane and rules.
Which flow measures does the Kanban method use?
The Kanban method uses four flow measures: work in progress, throughput, work item age and cycle time. Together they show how much work is open, how much is finished each week, how long open items have been waiting and how long finished items took, which gives a factual basis for planning and improvement.
The Kanban Guide defines four flow measures: WIP, throughput, work item age and cycle time.
- WIP. “The number of work items started but not finished”, for example the number of quotes currently being priced.
- Throughput. “The number of work items finished per unit of time”, for example jobs invoiced each week.
- Work item age. “The elapsed time between when a work item started and the current date”, for example how long an open quote has been waiting.
- Cycle time. “The elapsed time between when a work item started and when a work item finished”, for example days from job completion to invoice.
The guide also describes a service level expectation, a forecast based on historical cycle time and stated as a time period with a probability. Its example is “85% of work items will be finished in eight days or less.” A contractor could use the same form to state, from its own records, how quickly quotes usually go out.
A check Rostone Operating Partners uses with work item age is the oldest-card review: at each weekly review, the three oldest open cards on the board are discussed first, whatever their priority, so items that have quietly stalled are not left behind newer, louder work.
How is the Kanban method different from Scrum?
The Kanban method differs from Scrum mainly in rhythm and roles. Scrum runs work in fixed-length Sprints of one month or less with defined roles, while Kanban manages a continuous flow of work through stages with WIP limits and no required roles.
The Scrum Guide (November 2020) describes Scrum as “a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems”, with Sprints that are “fixed length events of one month or less” and a Scrum Team made up of “one Scrum Master, one Product Owner, and Developers.”
| Aspect | Kanban method | Scrum |
|---|---|---|
| Rhythm | Continuous flow; work is pulled when there is capacity | Fixed-length Sprints of one month or less |
| Roles | No roles required; applied to the current team | Scrum Master, Product Owner and Developers |
| Controlling workload | Explicit WIP limits on stages, people or the whole system | The amount of work selected for each Sprint |
| Change to current process | Starts with what the team does now | Introduces Sprints and defined roles |
| Example in a contracting business | Service calls, quotes and invoices that arrive continuously | A project or system change planned in short cycles |
Which parts of an HVAC, electrical or renewables business suit the Kanban method?
The parts of an HVAC, electrical or renewables business that suit the Kanban method are mostly office and management workflows where items queue between stages: estimating, design, procurement, scheduling, handover documents and invoicing. Site methods, safety procedures and statutory sign-offs follow their own rules and are not replaced by a board.
Six workflows lend themselves to a Kanban board in a contracting business: estimating, design and approvals, procurement, scheduling, handover documents and invoicing.
- Estimating. Enquiries and tenders queued for pricing, with a WIP limit per estimator.
- Design and approvals. Heat loss calculations, system designs and Distribution Network Operator (DNO) applications waiting for information or a response.
- Procurement. Heat pumps, battery systems and other long-lead equipment tracked from order to delivery.
- Scheduling. Jobs ready for engineers, and jobs on hold waiting for access or materials.
- Handover documents. Commissioning records, certificates and operation and maintenance manuals collected before a job closes.
- Invoicing. Completed jobs waiting for paperwork, valuation or approval before an invoice goes out.
Rostone sees queues in contracting businesses form in the office stages between the site and the cash, which a report focused on site progress can miss. A board covering those stages makes the queues visible to the owner and managers without extra paperwork.
What gets in the way of the Kanban method working?
What can get in the way of the Kanban method working is how it is introduced rather than the method itself: a board that is not kept up to date, no WIP limits, too many columns, a board used to monitor individuals instead of the flow of work, or software chosen before the process is agreed.
Five problems are worth watching for: a stale board, missing limits, too much detail, monitoring people instead of work, and a tool chosen before the process.
- A stale board. If cards are moved only before a meeting, the board stops showing reality. Moving cards as the work moves, and reviewing the board at a set time, keeps it current.
- No WIP limits. A board without limits shows the queue but does nothing to shorten it.
- Too much detail. A column for every small step makes the board hard to read; the stages where work waits matter most.
- Monitoring people, not work. Kanban University’s service delivery principles include “Manage the work; let people self-organize around it”. A board used to judge individuals can lead people to hide problems.
- Tool before process. Buying software before agreeing the stages and policies can copy an unclear process into a new system.
How can a business start using the Kanban method?
A business can start using the Kanban method by choosing one workflow, mapping its current stages onto a simple board, agreeing what each stage means, setting a first WIP limit and reviewing the board weekly. Limits, columns and policies are then adjusted in small steps based on what the flow measures show.
Five steps cover a first board: choose the workflow, map current stages, write the policies, set limits and review weekly.
- Choose one workflow. Pick one where delays cost money or customers, such as quotes or invoicing.
- Map the current stages. Following Kanban University’s principle “Start with what you do now”, put the stages as they actually run onto a whiteboard or a simple digital board.
- Write the policies. Agree what must be true for a card to move into each column, and who moves it.
- Set a first WIP limit. Start with the stage where work most visibly piles up.
- Review weekly. Look at the oldest cards, throughput and cycle time, and agree one change at a time.
The weekly review is where Kanban connects with continuous improvement: each change to the board is a small experiment that is kept, adjusted or dropped.
Rostone looks at visible workflow through the four GRAX options: Grow, Raise, Acquire and Exit. To grow, a board shows where extra work will queue before more staff are hired. To raise finance, flow measures can show a lender how reliably work turns into invoices. To acquire, a target’s boards and measures show how its office runs. To exit, a workflow that is visible and managed without the owner is easier for a buyer to understand.
The business improvement service for HVAC, renewables and electrical contractors works inside a business each month on margin, cash and capacity, building a weekly rhythm of meetings and numbers that runs without the owner.
Frequently asked questions
A Kanban board is a visual display of a workflow, with columns for each stage and a card for each item of work. The Kanban Guide describes it as the visualisation of the team’s Definition of Workflow. It can be a physical board or a digital one.
WIP stands for work in progress: the number of work items started but not finished. The Kanban Guide states that the number of items in a workflow must be explicitly controlled. WIP limits cap the number of items allowed in a stage, with a person or across the whole board.
Kanban University lists six general practices: visualise, limit work in progress, manage flow, make policies explicit, implement feedback loops, and improve collaboratively and evolve experimentally. The separate Kanban Guide names three practices: defining and visualising a workflow, actively managing items in a workflow, and improving a workflow.
Scrum organises work into fixed-length Sprints of one month or less and a Scrum Team of a Scrum Master, a Product Owner and Developers, according to the 2020 Scrum Guide. Kanban manages a continuous flow of work with WIP limits and no required roles, applied to the team’s existing process. Some teams combine elements of both.
The Kanban Guide defines four flow measures: WIP, throughput, work item age and cycle time. Throughput counts items finished per unit of time, work item age measures how long an open item has been in progress, and cycle time measures how long a finished item took from start to finish.
The Kanban method has its roots in Toyota’s production system. Toyota’s history records that its “supermarket method” was introduced in 1954 and evolved into the Kanban system, with a production instruction card or board known as the Kanban. Kanban University bases the Kanban method for knowledge work on David J Anderson’s 2010 book.
Sources
Kanban Guides: The Kanban Guide (May 2025)
Kanban University: The Official Guide to The Kanban Method
Toyota Motor Corporation: 75 Years of Toyota: Supermarket Method; Toyota Production System
Lean Enterprise Institute: Lexicon: Kanban
GOV.UK Service Manual: Agile tools and techniques
Scrum Guides: The Scrum Guide (November 2020)
Last updated: 14 November 2026




