Kanban as Method, Not Methodology: Management Approach Without Prescription

Definition

Kanban is intentionally not a methodology or framework. A methodology prescribes defined workflows, roles, and responsibilities specific to a domain (like software development). A framework provides incomplete scaffolding requiring customization. Kanban is neither—it is a management method or approach layered onto whatever process already exists, asking "how can we manage work better?" without saying "replace your current way of working."

In the Book

The Official Kanban Guide states clearly: "Kanban is not a methodology nor a process framework. Rather, it is a management method or approach that should be applied to an existing process or way of working. There is never a question of using Kanban versus a given methodology or framework. Rather, it is always adding Kanban using an existing methodology, framework, or way of working."

The guide elaborates on the distinction: "In software engineering a methodology is a process definition approach to software development and project management...Methodologies contain prescriptive, defined workflows and processes, including roles, and responsibilities...A process framework on the other hand is an incomplete methodology – a set of scaffolding that is intended to have broader applicability but requires customization for each context." Kanban is neither of these. Its purpose is narrower and more focused: "Kanban is intended to help you manage work better and to improve service delivery to the point where you consistently meet customer expectations. Kanban is a means to improve what and how you already do things. It is not a replacement for what you already do."

Why It Matters

Teams often treat Kanban as a replacement methodology ("we're going Kanban now") when its actual power lies in its non-prescriptive nature. A team using Waterfall, Scrum, or any custom process can apply Kanban's management principles on top without discarding their existing structure. This distinction enables adoption in complex organizations where wholesale process replacement is politically or operationally unfeasible. The freedom to "start where you are now" with Kanban makes evolutionary change possible—organizations improve incrementally without the disruption of big-bang transformation. In any established system, a method that works with existing culture rather than demanding it be replaced has vastly higher adoption and sustainability.