July flash sale
A Flow Manager helps people see and improve how customer-valued work travels across an end-to-end service. The role is not a new project controller and should not become the person who moves every ticket. Its value comes from making flow conditions observable, facilitating decisions, and helping teams finish work across boundaries that no single team owns.
Official reference: Kanban University Flow Manager course. 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.
Define the service before managing its flow
Write down the customer, the purpose of the service, the request event, the commitment event, and the delivery event. Then trace the people and systems involved. A team board may begin after analysis and end before release; the customer journey may begin during intake and finish only when an outcome is usable. A Flow Manager keeps both views available so local speed does not conceal upstream or downstream waiting.
Create a weekly flow evidence pack
Use a small, stable set of evidence: arrivals, departures, WIP, work-item age, lead-time distribution, blocked time, and the percentage of work meeting the service level expectation. Segment materially different work types. Add a short narrative explaining unusual demand, policy changes, and data-quality limitations. The evidence pack should help a conversation, not become a scorecard used to rank individuals.
Facilitate finishing decisions
Walk active work from right to left. Ask what is closest to a customer outcome, which item is aging beyond expectation, what is blocked, and where additional help would reduce elapsed time. When new demand arrives, expose the cost of starting it. The Flow Manager makes trade-offs visible while the accountable service participants decide priorities and policy exceptions.
Improve across team boundaries
Track handoffs and shared services without blaming the receiving team. Clarify entry criteria, response expectations, escalation routes, and the information required for a good request. Repeated dependency delays belong in a service delivery or operations review where leaders can change capacity and policy. Chasing individual tickets treats symptoms while leaving the dependency unchanged.
Protect the role from common failure modes
Do not turn the Flow Manager into a reporting secretary, ticket dispatcher, or substitute product owner. Avoid targets that reward closing easy items, lowering quality, or excluding inconvenient work. A healthy role increases shared capability: teams understand the measures, policies are visible, and improvement continues when the Flow Manager is absent.
Scenario: the Flow Manager role
A feature team reports a five-day cycle time, yet customers wait twenty-three days. The Flow Manager traces the wider service and finds eight days in approval before commitment and ten days waiting for release after development. The next experiment changes the approval threshold and creates a twice-weekly release readiness decision. The team does not work faster; the service removes waiting that the original board could not show.
The working model for the Flow Manager role
| Cadence | Question | Useful evidence | Likely decision |
|---|---|---|---|
| Daily flow review | What needs attention now? | Age, blocker, next action | Swarm, unblock, or stop starting |
| Replenishment | What should enter next? | Demand, capacity, risk | Select, defer, split, or discard |
| Service delivery review | Are expectations being met? | Lead-time distribution and feedback | Change a service policy |
| Operations review | What limits several services? | Dependencies and system trends | Change capacity or cross-service policy |
Use the Flow Manager role in a real service conversation
- Map one customer-valued service end to end.
- Publish measurement boundaries beside each metric.
- Establish a right-to-left daily flow review.
- Create an aging and blocker escalation policy.
- Review one cross-team constraint every month.
- Measure whether experiments improved customer outcomes.
Introduce the Flow Manager role without a big-bang change
During the first week, use Flow Manager Role Playbook for End-to-End Kanban Flow to establish a shared boundary and baseline. Begin with this action: Map one customer-valued service end to end. 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: Publish measurement boundaries beside each metric. Establish a right-to-left daily flow review. Create an aging and blocker escalation policy. 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: Review one cross-team constraint every month. Measure whether experiments improved customer outcomes. 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 Kanban University Flow Manager course, noting the access date, so future reviewers can distinguish official guidance from the local interpretation used in this service.
Where the Flow Manager role fits the certification path
Develop the relevant foundations through Team Kanban Practitioner training, Kanban System Design training. Continue with Kanban feedback-loop guide, aging WIP guide. Choose the path that matches your service responsibility and apply the learning with the people who operate and use the service.
Close the learning loop on the Flow Manager role
- Which customer or service decision should this Flow Manager role playbook 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?
