Kanban System Design (KMP-I) Learner Outcome Case

The role and the starting problem

Representative role

A delivery manager whose team uses To Do, Doing, and Done but still misses expectations

The board shows activity but hides intake, external review, blocked work, and customer expectations. Adding more status meetings has not improved predictability.

How the course work applies

Apply STATIK to understand services, demand, capability, and dissatisfaction.
Map the real workflow, including waiting and feedback loops.
Define initial WIP, pull, and class-of-service policies as testable agreements.

Artifacts that show applied learning

Attendance alone does not demonstrate workplace transfer. These work products make the reasoning, choices, and follow-up visible.

STATIK workshop record
Service definition
Workflow and policy board
Baseline flow report

Evidence to review

Work in progress
Work-item age
Throughput
Lead-time distribution

A 30-day transfer plan

Week 1: identify one service and collect representative demand.
Week 2: map actual workflow states with service participants.
Week 3: introduce one pull or WIP policy and record exceptions.
Week 4: review aging work and decide the next system experiment.

From a task board to a service design that exposes delay