Use this category only when the content is materially about Kanban as a strategy for observing work, managing flow, and improving value delivery.

Definition: Kanban is a change-management strategy, as described in the Kanban Guide, for improving an existing workflow through visualisation, WIP limits, explicit policies, flow management, and feedback from delivery metrics. It is not merely a task board or generic work-tracking tool.

Must have:

• Discusses “start with what you do now” or evolutionary improvement of an existing work system.
• Describes visualising work to make workflow, queues, blockers, or system behaviour observable.
• Mentions limiting work in progress (WIP) as a mechanism for improving flow.
• Explains managing flow using evidence such as lead time, throughput, service-level expectations, or bottlenecks.
• Refers to making policies explicit or creating shared understanding of how work moves through the system.

Strong fit:

• Primary: Kanban is the main subject and at least two Must have items are discussed.
• Secondary: Kanban is a substantial supporting theme and at least one Must have item is discussed.

Weak fit:

• Tertiary: Kanban is mentioned or adjacent, but the content is mostly about Scrum, Agile, DevOps, project management, or task tracking.
• Ignored: Kanban is absent, only implied, or supported only by generic references to boards, workflow, productivity, or collaboration.

Exclude:

• Scrum, sprint planning, roles, ceremonies, or timeboxes unless Kanban practices are materially discussed.
• Generic Agile, Lean, DevOps, or project-management improvement content without Kanban mechanisms.
• Visual task boards, to-do lists, ticket trackers, or workflow software described only as tools.
• Manufacturing kanban cards or inventory replenishment unless connected to the Kanban Guide’s workflow-change strategy.
• Generic terms such as flow, transparency, continuous improvement, value delivery, metrics, or bottlenecks are insufficient on their own.