July flash sale
Buying KMP 1 for a group should begin with the service the organisation wants to improve. Sending twenty people from unrelated teams to the same class may increase awareness without creating a shared system-design opportunity. A smaller cross-functional cohort around one service can produce more useful application.
Kanban University's Kanban System Design course focuses on understanding systems and designing an appropriate Kanban system. When discussing corporate training with AgileSeekers, ask how the accredited learning remains intact while exercises connect to your context.
Define the buying brief before requesting a proposal
- Name the service or family of services in scope.
- Describe current dissatisfaction without prescribing the board solution.
- Identify roles needed to understand demand, workflow, policy and governance.
- State delivery format, location, time zone and participant count.
- Separate accredited course requirements from optional application support.
- Define what leaders will make possible after training.
Invite a service-shaped cohort
| Participant | Contribution to system design |
|---|---|
| Customer or product representative | Demand, value, risk and expectations |
| People performing the work | Actual workflow, waiting, rework and policies |
| Service or delivery manager | Capability, coordination and improvement context |
| Specialist or dependency partner | Queues and constraints across boundaries |
| Leader or sponsor | Authority to change policy and remove systemic barriers |
Not every stakeholder needs to attend every learning activity, but excluding the people who perform the service makes the design theoretical. Avoid selecting participants only by seniority or availability.
Keep customisation within the accredited course
Ask which examples, cases or post-class workshops can use your context and which learning outcomes must remain standard. A provider should not remove essential KSD learning merely to spend the class configuring your tool. If the organisation needs consulting, label and scope that separately.
Private cohort or public batch?
A private cohort supports shared context, scheduling and protected organisational examples. A public batch can expose learners to other industries and may suit one or two participants better. Choose private delivery when enough roles from one service can attend and leaders will support application. Choose a public batch when the organisation cannot form a useful service-shaped cohort yet.
Questions for the provider meeting
- Who is the Accredited Kanban Trainer and what comparable services have they worked with?
- How much design practice and feedback will each learner receive?
- Which participation and certificate requirements apply?
- How will confidential organisational examples be protected?
- What optional support exists for the first implementation experiment?
- What is included in the total proposal, including taxes and travel?
Plan the environment that training alone cannot create
Learners need access to service evidence, time to convene stakeholders and permission to test policy. If leaders continue bypassing replenishment, demand full utilisation and punish visible delay, the class cannot produce adoption. Add leadership actions to the training plan.
Evaluate transfer, not attendance theatre
Track whether a cohort can define a service boundary, visualise hidden work, agree an initial policy and run an evidence-based review. Do not attribute all business outcomes to training, and do not use certificate count as the only success measure.
Compare this focused option with the corporate Kanban course selection guide. Once KSD is the right choice, use the KMP 1 course details to review the public learning offer.
