Skip to content

STATIK: Systems Thinking Approach To Introducing Kanban

Definition

STATIK (Systems Thinking Approach To Introducing Kanban) is a repeatable, humane six-step iterative process for designing a Kanban system from scratch. Rather than imposing a standard board template, STATIK asks teams to first understand their current state: sources of dissatisfaction, patterns in demand, system capabilities, workflow activities, classes of service, and only then design the Kanban system (board, WIP limits, policies) appropriate to that specific context. The process is iterative—later steps may uncover new information that prompts revisiting earlier steps.

In the Book

The Official Kanban Guide presents STATIK as the answer to "If every board and Kanban system is unique, how can I design my own system?" The six steps are:

  1. Identify sources of dissatisfaction – "What are the people involved in service delivery dissatisfied with? What are customers dissatisfied with?"
  2. Analyze demand – "What do customers request, through which channels? What are types of work and patterns in demand?"
  3. Analyze system capabilities – "What are the capabilities of the system with regard to how much of the customer demand is being delivered, of what type, and how fast and predictable?"
  4. Model the workflow – "Which are the activities that each of the identified work item types go through?"
  5. Identify classes of service – "How do items enter and get treated in the system?"
  6. Design the Kanban system – "Based on all the insights gained in the prior steps, the Kanban system is then designed."

The guide notes: "STATIK is not intended as a one-pass, sequential process, but rather it is intended to function as a feedback loop that informs design and redesign activities. In practice, this process usually takes between 4 hours and 4 days...it should be done with at least a representative group of the people involved. While everyone will have a picture of how the work is done in mind, it rarely maps between people. The STATIK approach will reconcile these views into a shared view."

Why It Matters

Most teams copy a standard Kanban template without understanding their actual workflow, demand patterns, or pain points. STATIK inverts this: understand before designing. This ensures the board reflects reality, not wishful thinking, and that the design choices (WIP limits, workflow columns, service classes) solve actual problems. The iterative nature acknowledges that system design is not one-time; as teams learn, the system evolves. In any complex domain, designing without understanding the system you are designing for guarantees a solution that does not fit. STATIK embodies the Kanban principle "Start where you are now" by making diagnosis a non-negotiable first step.