TeamsFoundations

Applying Professional Kanban by Designing a Kanban System You Can Run at Work

Hands-on Kanban for people who already have a board: compare your own simulation results with loose and tight work-in-progress limits, then write down how your work really flows.

FoundationsProKanban.orgTraditional (Full Day) · Traditional (Half Day) · Immersive

What changes for your team

  • Measured by your team, not claimed by us
  • Write down how you really work
  • One chart on its own misleads

Immersive training pays back differently to a two-day course. Sessions spread across several weeks mean each idea is applied in your real work before the next one lands — so capability builds instead of fading under a backlog. Why immersive produces better returns →  ·  Other formats available in the panel above.

Your teams have a board. Do they have a Kanban system?

In my experience, without a Kanban system delivery gets slower and harder to predict.
Everything is in progress, little finishes. Work piles up as started but not done.
Limits rise under pressure. The instinct to start more is stronger than the explanation of why not to.
A healthy report can hide stuck work. A good throughput figure can sit beside work waiting on someone outside the team.
In my experience, being told that limiting work in progress helps rarely changes how a team works. People change it once they have watched it happen.

A board is not a system

Kanban here is a strategy for change that starts with what a team does now, not a tool.

A board

A Kanban system

Work is shown, not how the team really works How the team really works is made visible
Work in progress is not limited Work in progress is limited
Policies live in people's heads Policies are explicit
Flow is judged from one chart at a time Flow is managed from its measures read together

Evidence first, theory second

Participants play first and learn the theory afterwards, so each step uses their own results from the step before.

A timed game, passing work along a line of players, first in big batches and then in small ones

Teams play timed rounds of a simple game, and between the first two rounds the number of pieces of work passed on at once changes. They see for themselves how soon the first and last pieces of work reach the end.

The ideas behind the game, explained afterwards

Once they have played, participants learn what Kanban is and how to get work from start to finish without waiting. They also learn Little’s Law, a rule that links how much work is under way, how long each piece takes and how many pieces finish. It describes what has already happened; it does not predict.

A team’s work, simulated twice, first with a loose cap on how much work can be started, then a tight one

Teams run a simulation of a team’s work on a Kanban board twice, and keep their own charts from both rounds showing how long each piece took to finish and how long unfinished pieces had been waiting. After each round they discuss it, first how it felt, then what their charts show.

Naming what they did in the simulation

Teams list the moves they used to keep work moving and stop items sitting unfinished for too long. Then they pick out, in the simulation they just played, the parts every Kanban system must have: what counts as a piece of work, where it starts and finishes, the stages, the cap on work in progress, and the agreed rules.

Their own work, written on a blank sheet

Each participant writes down how their own work really flows today, rather than copying their current Kanban board (the wall or screen where a team tracks each piece of work), if they have one, which rarely shows it. The sheet covers where work starts and finishes, the stages in between, the rules the team has agreed for how work moves, and how long a piece of work should usually take.

What to measure, and what the numbers cannot tell you

Participants learn to measure how much work is under way, how long pieces take, how many finish and how old unfinished pieces are, and what Little’s Law can and cannot tell them. They learn which numbers warn early and which only confirm after the event, and they practise reading a chart of how long pieces took to finish.

Example boards and a case study that show where things go wrong

Groups visit example Kanban boards showing familiar failures, such as the cap on work started being ignored or finished work piling up, and work out what to ask the team, not what to tell them. In a case study, the reports say all is well while stakeholders say the team is unresponsive, and participants find that no single number tells the whole story.

Advice from peers, on prepared and real problems

Participants give advice on prepared problems and, in the eight-session format or where time allows, bring their own real problems for their peers to help with. They leave with guidance on preparing for the Professional Kanban I (PK I) certification assessment from ProKanban.org.

Common objections

“We can learn it from the guide and a book.”

The rules, yes. On the course your people compare their own charts from a simulation run first with a loose and then a tight cap on how much work can be started.

“We already have a board.”

The workflow exercise checks every required element of your own way of working and shows which ones are missing.

“A simulation is not our work.”

That is why the simulation is followed by a workflow written for your own work and, where time allows, your own problems put to your peers.

What you get back

A team that holds its WiP limits under pressure

A manager who asks the board a question instead of trusting one report

A workflow the team agreed and can improve

Choose a delivery

None of these outcomes is guaranteed for your organisation.

Every format includes a PK I attempt, with a free second attempt if you do not pass within 14 days. We do not promise a pass rate; the course is built around running a Kanban system, not exam coaching. The class materials are sized for up to 20 people.

Eight immersive sessions

The format we recommend. Each session is 2 hours of training and 2 hours of consulting, one session every one to two weeks.

  • Suits teams who want to apply it to their own system from the first session
  • Something to try in your own work after every session
  • Consulting hours apply each session to your own team's work

Four half days

Four sessions of 4 hours.

  • Suits people who can give half a day at a time but not a full day

Two full days

Two days of 8 hours.

  • Suits people who need the shortest calendar time

Who to send, and how

Team members, team leads, managers, Scrum Masters, agile coaches, Product Owners, product and project managers, and business analysts, in any knowledge work.

It is a foundations course, not for people who already run and measure a Kanban system.

A private class for one organisation. In my experience this works best, because the workflow exercise is richer with a real, shared process. If you are arranging it for a team, you are welcome to attend with them.
A seat in a public class. Mixed teams build a workflow from one member’s real work. Ask us whether one is scheduled.

PMI PDUs

Participants are able to claim PMI PDUs for the hours they attend: 14 after 2 days, 16 after 4 half-days, or 32 after 8 half-day sessions. PDUs are earned for attendance, not for passing an assessment. You claim them yourself in PMI's Continuing Certification Requirements System at ccrs.pmi.org, under Education.

Frequently Asked Questions

The Applying Professional Kanban (APK) course is intended for team members, team leads, managers, Scrum Masters, Product Owners, project managers, business analysts, and anyone looking to improve workflow, delivery, or process improvement with Kanban. If you’re not interested in hands-on changes to team workflow or you aren’t planning to apply Kanban in your work, this course won’t be a good fit.

No specific prior experience or formal qualifications are needed; APK is open to anyone interested in improving value delivery using Kanban.

Certification is included—after the course, you’ll take an online assessment covering key Kanban concepts. If you don’t pass, you’ll get guidance on areas to improve and can retake the assessment.

APK is practical and hands-on, with a strong emphasis on exercises and real-world application. You’ll participate in live group sessions where you apply concepts instead of just listening to lectures.

After APK, you’ll be able to create visual workflow boards, set and manage WiP limits, and use flow metrics to drive improvements. You’ll leave with practical strategies and tools to launch or evolve a Kanban system in your team.

Syllabus

Here is exactly what your team will cover, and how we deliver it. Every format teaches the same modules; what changes is how the time is spread and what happens between sessions:

Immersive RecommendedTraditional (Full Day)Traditional (Half Day)
Sessions 8 sessions 2 days 4 half-days
Each session 4h: 2h reflect + 2h learn 8h incl. breaks and lunch 4h incl. breaks
Total time with an expert 32h 16h 16h
New concept and practice
incl. breaks
16h 16h 16h
Facilitated reflection
what happened when you tried it
16h — —
~Expert time per topic
breaks removed
~3h20
1h40 reflect + 1h40 learn
~1h30 ~1h40
Time to apply between sessions 1–2 working weeks (≈36–72h) Overnight Half a working day (≈4h)

Each immersive session follows a learning cycle: reflect on what happened when you applied the last concept, learn the next one and practise it, then take it back to work as an outcome-based assignment. It is designed for triple-loop learning, so participants do not just change what they do; they question why they do it and how they see their organisation.

Need more support? The immersive experience can be combined with additional coaching, consulting or mentoring to create a Mentor Program for your team.

Choose a format above to see how the modules group into sessions.

Before You Start

Complete the pre-work below before your first session so you arrive ready to participate.

Session 1 · 2h facilitated reflection + 2h new concept and practice · 10m break each hour

Feeling Batch Size

Module 1

Learn a new concept

Participants say what they already know and use of Kanban, so the class starts from what people do now. Then they play timed rounds of the Penny Game, where only the batch size changes between the first two rounds, and see for themselves how batch size changes when the first and last items are delivered. Each team keeps its own round times for the next session.

Outcome-based assignment: Count what is actually in progress · Immersive only

Ask Look at your team’s current work and record what is started but not finished, how large the batches are, and where work waits. Change nothing yet.
For example, you might:
  • Count every item your team has started and not finished today, wherever it is tracked or held.
  • Note how work arrives and moves: one item at a time, or in batches, and how large those batches are.
  • Mark the places where work sits waiting for someone or something.
  • Compare your count with what your board shows, and note any differences.
→ Reflected on at the start of Module 2: Naming What You Felt

Session 2 · 2h facilitated reflection + 2h new concept and practice · 10m break each hour

Naming What You Felt

Module 2

Facilitated reflection: Count what is actually in progress · Immersive only

Facilitated reflection: Count what is actually in progress

Learn a new concept

Participants name what they saw in the Penny Game and in their own counts. They learn what flow optimisation is, what Kanban is (a strategy for change built on visualising work, limiting work in progress, managing flow and making policies explicit), and how Little’s Law relates work in progress, cycle time and throughput as a description of past behaviour, not a forecast. They finish by agreeing a Kanban strategy and getting ready for the simulation.

Outcome-based assignment: Describe how work moves now · Immersive only

Ask Using the counts you made, describe how work moves through your team today: who pulls and who pushes, where it queues, and what, if anything, limits starting new work.
For example, you might:
  • Have a conversation with your team about how work is started: is it pulled when there is capacity, or pushed when it arrives?
  • Identify the queues in your process and how long items usually wait in them.
  • Find out whether anything stops new work starting, and who decides.
  • Bring your work-in-progress counts to the next session.
→ Reflected on at the start of Module 3: Two Rounds, Your Own Evidence

Session 3 · 2h facilitated reflection + 2h new concept and practice · 10m break each hour

Two Rounds, Your Own Evidence

Module 3

Facilitated reflection: Describe how work moves now · Immersive only

Facilitated reflection: Describe how work moves now

Learn a new concept

Teams play TWiG twice in one session. Only the WiP limits change between rounds, from loose to tight. Each team captures its own cycle time scatter plot and work item aging chart in both rounds and keeps the first round open to compare. The first debrief covers what the round felt like, and the second covers what the numbers show. If a team finishes early, a third round tests an improvement it chooses.

Outcome-based assignment: Age your own work · Immersive only

Ask List every item your team has started and not finished, with the number of days since each one started, and decide which ones need attention first.
For example, you might:
  • Record a start date for each item in progress, and work out its age in days.
  • Sort the items by age, and discuss with your team why the oldest ones are still open.
  • Agree which item you would act on first, and why.
  • Note whether your current tools show item age at all.
→ Reflected on at the start of Module 4: What You Did, Named

Session 4 · 2h facilitated reflection + 2h new concept and practice · 10m break each hour

What You Did, Named

Module 4

Facilitated reflection: Age your own work · Immersive only

Facilitated reflection: Age your own work

Learn a new concept

Participants name the tactics they used to manage work in the simulation and how they managed its age, and share what they learnt in a 1-2-4-All. Then they find the required workflow elements in the simulation they have just played. A short retrospective closes the first half of the course.

Outcome-based assignment: Gather the raw material for your workflow · Immersive only

Ask Collect the evidence for each workflow element in your own work by observing and asking, not designing: the work items, where work starts and finishes, its states, what limits work in progress, the rules people follow, and how long things take.
For example, you might:
  • Watch how work actually starts and finishes in your team, and write down what you see.
  • Ask the people doing the work which rules they really follow, written down or not.
  • Note what, if anything, limits how much work is started.
  • Find out how long a typical item takes from start to finish.
→ Reflected on at the start of Module 5: Writing Down How You Really Work

Session 5 · 2h facilitated reflection + 2h new concept and practice · 10m break each hour

Writing Down How You Really Work

Module 5

Facilitated reflection: Gather the raw material for your workflow · Immersive only

Facilitated reflection: Gather the raw material for your workflow

Learn a new concept

On a blank sheet, participants define the workflow for their own real work, from the evidence they gathered, rather than copying an existing board. It covers the work items, start and finish points, states, how WiP is controlled, explicit policies and a service level expectation. Where people from the same organisation attend together they work on their shared workflow; in a public class a mixed team builds one member’s real workflow. Teams share and review each other’s workflows.

Outcome-based assignment: Test your workflow against real work · Immersive only

Ask Walk three or four real items through the workflow you drafted, with the people who do the work, mark what is missing or only true on paper, and revise it.
For example, you might:
  • Walk real items through your draft workflow with the people who did the work.
  • Mark each state, policy or limit that does not match what happened.
  • Revise the workflow, and bring both versions to the next session.

Session 6 · 2h facilitated reflection + 2h new concept and practice · 10m break each hour

Measures, and What Little's Law Can and Cannot Do

Module 6

Facilitated reflection: Test your workflow against real work · Immersive only

Facilitated reflection: Test your workflow against real work

Learn a new concept

Participants say what changed when they tested their workflow at work, and review it. Then they define the workflow measures (work in progress, cycle time, throughput and work item age) on the simulation, learn which measures lead and which lag, and why Little’s Law explains past behaviour but does not forecast. They read a cycle time scatter plot and its percentiles.

Outcome-based assignment: Measure your own four · Immersive only

Ask Record your team’s work in progress each day, the age of each item in progress, and the cycle time and throughput of what finished, then plot the finished items on a cycle time scatter plot.
For example, you might:
  • Count work in progress at the same time each day.
  • Record a start and finish date for each item that finishes.
  • Plot finished items on a scatter plot, and mark where the 50th and 85th percentiles fall.
  • Discuss with your team what the plot shows and what it does not.

Session 7 · 2h facilitated reflection + 2h new concept and practice · 10m break each hour

Rehearsing the Traps, Reading the Whole Picture

Module 7

Facilitated reflection: Measure your own four · Immersive only

Facilitated reflection: Measure your own four

Learn a new concept

In Kanban Scenarios, groups move between example boards that show common problems, such as limits being ignored, finished work piling up and a blocked state, and work out what to ask the team rather than prescribing an answer. In the Metrics Case Study they read throughput, the cycle time scatter plot, work item age and the board one after another, and find that any one view on its own would mislead, including when the cause sits outside the team.

Outcome-based assignment: Ask the question, not the answer · Immersive only

Ask At your team’s board, when you see a problem, ask the team a question that helps them see it, rather than telling them the fix. Bring one real problem you have not yet resolved to the next session.
For example, you might:
  • Ask what is oldest, and where exactly blocked work is stuck.
  • Notice when someone suggests raising a limit, and ask what the limit is protecting.
  • Write down the questions you asked and what the team decided.
  • Choose one real problem you have not resolved to bring to the next session.
→ Reflected on at the start of Module 8: Taking It Back to Work

Session 8 · 2h facilitated reflection + 2h new concept and practice · 10m break each hour

Taking It Back to Work

Module 8

Facilitated reflection: Ask the question, not the answer · Immersive only

Facilitated reflection: Ask the question, not the answer

Learn a new concept

Participants advise on prepared scenarios, then use Give and Get Help (Troika) to put their own real problems to their peers. They review what they now understand about Kanban and how they will apply it to their own Kanban system, reflect on the course, and get guidance on preparing for the PK I assessment and on further reading.

Outcome-based assignment: Make one change, and take the PK I assessment · Immersive only

Ask Make one change to your Kanban system that needs no reorganisation, decide in advance which measure will show whether it helped, and take your PK I attempt.
For example, you might:
  • Choose one change, such as an explicit policy, a WiP limit or a service level expectation, that your team can make itself.
  • Agree with your team which measure you will watch, and what you expect it to show.
  • PK I: a timed, multiple-choice assessment from ProKanban.org.
  • APK includes a PK I attempt, with a free second attempt if you do not pass within 14 days.
→ Reflected on at the start of Catchup & After

Catchup & After · Immersive only

Catchup & After

Facilitated reflection: Make one change, and take the PK I assessment

Facilitated reflection: Make one change, and take the PK I assessment

Two weeks after completion, participants are invited to join a follow-up catch-up session designed to address any remaining questions, ideas, or challenges that have emerged since the training. This session provides an opportunity to reflect on your experiences applying the concepts learned in the course, share insights, and receive additional support.

* Assignments are part of our Immersive Training Programs, encouraging participants to apply their learning practically between sessions for a more hands-on experience.


Ready to bring this to your team?

Private delivery, fixed price, money-back guarantee. Tell us what you need and we'll put together a proposal.

If this isn't quite right for where you are

Not sure what would actually move the needle?

Most organisations don't need a course catalogue. They need a diagnosis. Tell me what's not working, who is involved, and what you've already tried. I'll tell you honestly whether training will help, and if so, what.