July flash sale
Flow Manager, Delivery Manager, and Demand Manager are related but not interchangeable roles. One emphasizes movement of customer-valued work, one manages predictable service delivery, and one shapes upstream demand and discovery. Organizations should begin with the constraint they need to address, not with the newest title.
Official reference: current Kanban University course catalog. Course names, prerequisites, credentials, platform features, and award rules can change; confirm them on the official page for the class or credential you are considering.
Choose Flow Manager for an end-to-end visibility gap
Use this focus when teams optimize locally but nobody can explain the complete journey from request to customer outcome. The practical work includes mapping flow, measuring time and WIP, managing aging, facilitating cross-team finishing, and exposing dependencies. It is a useful bridge between team-level practices and service-level management.
Kanban manager role selection in practice
A SaaS company has too many half-started initiatives, slow releases, and weak customer evidence. It first assigns a Flow Manager accountability to map the service. Data shows the largest queue is upstream. A product leader adopts Demand Manager practices to limit discovery and improve replenishment, while a delivery lead strengthens service expectations and risk reviews. The solution is a connected management system, not a contest between role names.
Choose Delivery Manager for a reliability gap
Use this focus when a customer-facing service needs stronger commitment, forecasting, policy, risk management, and management cadences. Delivery Managers work with a designed Kanban system and lead decisions that improve predictability and fitness for purpose. Kanban University lists Flow Manager or a KMP class as a prerequisite for its Delivery Manager course.
Choose Demand Manager for an upstream decision gap
Use this focus when too many requests enter, discovery is overloaded, priorities change without evidence, or delivery receives poorly formed options. Demand management covers customer requests, capacity planning, upstream governance, decision filters, discovery, product-market fit, and Fit for Purpose. The official course also expects prior Flow Manager or KMP learning.
Roles can be accountabilities rather than job titles
A smaller organization may distribute these responsibilities among an existing product manager, delivery lead, service manager, and team. Name the accountability, decision rights, evidence, and cadences before creating positions. At larger scale, distinct people may be justified when demand, delivery, and flow each require sustained attention.
Avoid three separate optimization silos
Demand decisions affect delivery WIP; delivery policies affect end-to-end flow; flow data should reshape upstream selection. Use shared service outcomes and connected reviews. If each role owns a different dashboard and optimizes its own target, the organization recreates the boundaries Kanban is meant to make manageable.
A reusable table for Kanban manager role selection
| Role | Primary question | Typical evidence | First useful action |
|---|---|---|---|
| Flow Manager | How does value move end to end? | WIP, age, lead time, blockers | Map one service |
| Delivery Manager | Can the service meet expectations? | SLE performance, risk, feedback | Define service policies |
| Demand Manager | Are we selecting the right demand? | Arrivals, options, purpose, abandonment | Design upstream states |
Convert this Kanban manager role selection guide into action
- Name the customer-facing problem.
- Identify whether the constraint is upstream, delivery, or end-to-end.
- Assign decision rights rather than only a title.
- Define one shared service outcome.
- Connect replenishment, delivery, and service reviews.
- Reassess the role design after ninety days.
Four weeks from baseline to review for Kanban manager role selection
During the first week, use Flow Manager vs Delivery Manager vs Demand Manager to establish a shared boundary and baseline. Begin with this action: Name the customer-facing problem. Invite the people who request, perform, manage, and receive the work; their different views will reveal assumptions that a board or dashboard cannot settle alone. Record definitions, missing data, known exceptions, and current customer consequences. Do not change several policies during the baseline week, because the service needs a credible comparison for the experiment that follows.
During weeks two and three, complete these actions: Identify whether the constraint is upstream, delivery, or end-to-end. Assign decision rights rather than only a title. Define one shared service outcome. Select one policy experiment that is within the group's authority, state why it should influence the observed behavior, and name a safety boundary for quality, workload, compliance, or customer harm. Keep unrelated changes visible. Use the working table above during the relevant cadence so the resource becomes part of a decision rather than a document that people read once.
During week four, complete the remaining actions: Connect replenishment, delivery, and service reviews. Reassess the role design after ninety days. Compare the new evidence with the baseline, ask affected customers and service participants what changed, and look for displaced delay outside the original boundary. Decide explicitly to keep, adapt, stop, or extend the experiment. Store the decision beside the policy and link back to the current Kanban University course catalog, noting the access date, so future reviewers can distinguish official guidance from the local interpretation used in this service.
Learning routes connected to Kanban manager role selection
Develop the relevant foundations through Team Kanban Practitioner training, Kanban System Design training, Kanban Systems Improvement training. Continue with Flow Manager playbook, Delivery Manager playbook, Demand Manager playbook. Choose the path that matches your service responsibility and apply the learning with the people who operate and use the service.
Questions to take into a Kanban manager role selection review
- Which customer or service decision should this Flow Manager vs Delivery Manager vs Demand Manager help us make?
- What evidence do we have, and where are the measurement boundaries unclear?
- Which policy or behavior is within our authority to change?
- What unintended consequence should we watch during the experiment?
- When will we review the outcome and decide to keep, adapt, or stop?
