METHODS / PROJECTS, PROCESSES, AND KNOWLEDGE / KANBAN
FRAMEWORK
Kanban
Kanban is a strategy for improving the flow of work through a defined process. A board makes the workflow visible, while explicit policies and work-in-progress controls determine how work enters, moves, waits, and finishes.
REFERENCE The Kanban Guide
Leadership requests, approvals, board deliverables, event operations, onboarding work, and other recurring flows where too much has started or handoffs remain hidden.
A board reflects reality only when the work and policies stay current. It cannot create capacity or resolve unclear authority.
WHAT IT IS
How a board becomes a managed flow of work.
A Kanban system defines the work item, the points where work starts and finishes, the states it passes through, how work in progress is controlled, and the policies governing movement. The board makes that definition visible.
The team actively manages aging and blocked items, pulls new work when capacity becomes available, and reviews flow data to improve the workflow. Columns and cards provide visibility. The operating rules turn the board into a framework for managing flow.
FIT
When Kanban is useful.
Reach for it when
- A team receives a continuing queue of recognizable requests.
- New work starts before active work finishes.
- Waiting, blockers, and handoffs are difficult to see.
- The team can agree on entry, movement, urgency, and completion rules.
Use another approach when
- The need is a personal reminder system.
- The work is a one-time sequence that a checklist can handle.
- An active incident requires live command and triage.
- The team cannot yet agree what counts as started or finished.
THE OPERATING PIECES
What gives the board operational meaning.
- Work item: the unit of work that moves through the flow
- Started and finished: the boundaries used to define work in progress and elapsed time
- Workflow states: the meaningful stages the work passes through
- WIP control: the rule that limits how much work may be active
- Explicit policies: the rules for movement, blocking, urgency, access, and completion
- Service level expectation: a forecast that a stated percentage of items will finish within a stated elapsed time, based on historical cycle-time data when available
- Flow measures: work in progress, throughput, work-item age, and cycle time
HOW TO BUILD IT
Define the flow before filling the board.
EXAMPLE
Managing leadership requests and board deliverables.
An executive operations team uses Ready, Active, Waiting, Review, and Done. Work remains in progress while it waits for input or approval. A last-minute board request can enter through the urgent policy only after an authorized person names what it displaces.
During the weekly review, the team examines the oldest items and repeated blockers before starting more work.
KEEP IT USEFUL
Common implementation and access considerations.
Common implementation issues
- Treating the board as a visual task list with no WIP control or movement rules.
- Removing blocked items from the active count.
- Mixing work types that differ too much in size or flow for useful comparison.
- Keeping cards open after the underlying work has changed or ended.
- Starting urgent work without naming what it displaces.
Team and access considerations
- Leaders need to accept that urgent work consumes capacity already assigned elsewhere.
- Keep confidential HR, legal, security, and board details in restricted records.
- Review a team or service flow rather than using throughput as an individual quota.
- Agree on exception authority before a high-pressure request arrives.
- Change the workflow when the board repeatedly exposes the same delay or handoff failure.
AI AND JUDGMENT
Use AI to keep the flow visible. People control priority, authority, and workflow changes.
AI can help
- Draft work items from approved intake and request records.
- Flag aging, blocked, duplicated, or ownerless items.
- Flag unusual movement in flow measures that were calculated from structured timestamps and formulas.
- Prepare a review of repeated delays and handoffs with links to the affected work.
People remain responsible for
- Deciding what may enter the workflow and what it displaces.
- Setting WIP controls, urgency rules, and access boundaries.
- Confirming ownership, completion, and exception authority.
- Deciding whether a delay reflects the workflow, capacity, or the nature of the work.
AI may detect a pattern without understanding the customer, political, legal, or operational reason behind it. Review the underlying work before changing the policy.
SOURCES
What the sources cover.
Independent evidence
The 2025 Kanban Guide defines the workflow, WIP controls, service-level expectation, active management, improvement practice, and core flow measures. Independent syntheses report recurring benefits and challenges primarily in software work, so executive operations teams should test the same mechanisms against their own flow.
View sources (3)OpenClose
WHERE IT FITS