July flash sale
Business Analysts often see the work before developers do and after stakeholders believe it has started. They see requests waiting for clarification, decisions cycling through approvals, dependencies surfacing late and requirements ageing while nobody counts them as work in progress. That vantage point makes KMP 1 useful when the analyst wants to improve the service, not only document individual items.
Kanban System Design (KMP 1) training develops a systems view of demand, capability, workflow, policies and risk. It can help a Business Analyst or Delivery Analyst turn recurring delivery friction into evidence the service can inspect.
Translate analysis queues into visible work
| Hidden activity | Visibility decision | Policy question |
|---|---|---|
| Waiting for stakeholder answer | Show an explicit blocked or waiting state | Who follows up and when? |
| Options under discovery | Separate options from committed delivery | What allows commitment? |
| Compliance review | Model the review in the workflow | Which work requires it? |
| Dependency clarification | Track dependency and age | When is escalation triggered? |
| Rejected or stale request | Show exit and discard | Who may close demand? |
Do not make every document a work-item type
A work-item type should represent demand with meaningfully different risk, workflow or treatment. User stories, use cases and requirement documents may be representations rather than separate service demand. Too many types make policy hard to understand; one generic type can hide material differences. Use evidence to find the useful level.
Where analysts contribute to STATIK
- Collect sources of dissatisfaction from customers and service participants.
- Describe arrival patterns and identify demand that is currently discarded or reworked.
- Map workflow as work actually happens, including waiting and loops.
- Surface policies that different stakeholders currently interpret differently.
- Help define observable outcomes for the first system-design experiment.
The analyst should not become the permanent owner of the Kanban system. Policies need agreement from people who perform and govern the service. Facilitation and evidence are more useful than privately designing the perfect board and asking everybody else to adopt it.
A preparation exercise using one request
Choose one recently completed item and reconstruct its timeline. Mark request date, commitment, active work, waiting, blocked periods, delivery and any return loops. Note where data is unavailable. The gaps themselves reveal how little the organisation can currently explain about flow.
Role fit versus certificate collection
KMP 1 fits analysts who influence delivery systems, service improvement, workflow policy or operational reporting. A general business-analysis course is more direct when the gap is elicitation, modelling or requirements technique. The strongest combination is role craft plus the ability to see and improve how demand becomes value.
Questions analysts should ask the trainer
Ask whether class cases include upstream discovery, approval queues and non-development work. Confirm that exercises examine actual demand and workflow rather than assuming every request is already a user story. Also ask how learners receive feedback on service boundaries and work-item types. Those choices are where an analyst's detailed knowledge can either clarify the system or make it unnecessarily complicated.
Use the STATIK preparation guide and end-to-end service design guide to prepare a case for class.
