HomeFrameworksOrganization & Management › Kanban
// framework

Kanban

Taiichi Ohno / Toyota, 1940s–50s; adapted for knowledge work by David Anderson, 2000s

Visual workflow management on a board — cards move from Backlog to In Progress to Done, with a strict limit on how many things can be in progress at once.

// description

A visual workflow management system using cards on a board (typically: To Do, In Progress, Done) to represent work items moving through a process. Core principles: visualise work, limit work-in-progress (WIP), manage flow, make policies explicit, improve continuously.

// history

Kanban (Japanese for "signboard" or "visual signal") was developed by Taiichi Ohno at Toyota in the 1940s to control inventory flow in manufacturing, inspired by how supermarkets restock shelves. David Anderson adapted Kanban for software development in 2004, introducing WIP limits as a mechanism for improving flow and reducing context-switching. Kanban boards (physical or digital via Trello, Notion, Linear) are now ubiquitous in creative and technical work.

// example

A creator's Kanban board: Backlog (all content ideas), To Write (this week's priorities), In Progress (WIP limit: 2 items max), In Review (finished but needs polish), Published. When "In Progress" is full, no new cards can move in — forcing completion before starting something new.

// katharyne's take

Kanban is the system I come back to every time I get overwhelmed. The WIP limit is the entire genius of it — you cannot start something new until something finishes. I have a Notion Kanban for my content pipeline and a physical magnetic board in my office for product development. The visual aspect is important. When you can see that "In Progress" has twelve things in it, you know why you feel frantic. The board doesn't lie.

// creative uses
// quick actions
// prompt ideas
Design a Kanban board structure for my creator business in [Notion / Trello / a physical board]. I run [describe your business streams — e.g. KDP publishing, Etsy shop, email newsletter, course]. For each stream, define the columns I need, what cards go in each column, and what my WIP limit should be for the "In Progress" stage given that I work approximately [X hours/week].
I feel overwhelmed and like I'm always busy but nothing ever finishes. Diagnose this using the Kanban framework. Here's what I currently have in progress: [list everything you're actively working on]. Apply WIP limit thinking to tell me: what should I pause, what should I complete first, and what's my recommended maximum simultaneous work-in-progress count for someone with my workload?
Help me set up a Kanban system for my [KDP production pipeline / Etsy listing refresh / content creation workflow]. Define all the stages a work item moves through from idea to completion, the definition of "done" for each stage, and the WIP limit for each stage. Then help me populate the backlog by listing all current work items by stage.
See also: Scrum, Agile Manifesto, Lean Manufacturing
← Scrum Lean Manufacturing →