STATIK for Defining the Kanban Board
STATIK (Systems Thinking Approach to Implementing Kanban) is a structured method developed by David J. Anderson for designing and implementing Kanban systems. Rather than copying a generic board template, STATIK helps you understand your unique workflow and design a Kanban system that truly fits your context.
What is STATIK?
STATIK is a facilitated workshop approach that guides teams through understanding their current system and designing an appropriate Kanban board. It emphasizes understanding the work, the workflow, and the sources of dissatisfaction before jumping to solutions.
Why Use STATIK?
- Ensures your Kanban system fits your actual workflow, not a generic template
- Builds team understanding and buy-in through collaborative design
- Identifies improvement opportunities before implementation
- Creates a shared mental model of how work flows through your system
- Reduces the risk of implementing a Kanban system that doesn't address real needs
The Eight Steps of STATIK
1. Understand Sources of Dissatisfaction
Begin by identifying what's not working well in your current system. What frustrates your team? What causes delays? What creates quality issues?
Example: "Work sits waiting for review," "Priorities constantly change," "We don't know what's in progress"
2. Analyze Demand
Understand the types of work requests coming into your system. Different types of work may need different treatment, policies, or swim lanes.
Example: "Standard features," "Urgent bugs," "Technical debt," "Expedite requests"
3. Analyze Capability
Examine your team's current capacity and capability to deliver. What skills exist? What are the constraints? How does work currently flow?
Example: "3 developers, 1 designer, 1 QA," "Design is often a bottleneck," "Testing happens at the end"
4. Model the Workflow
Map out how work actually flows through your system today. Identify the states work passes through and who is involved at each stage.
Example: "Backlog → Design → Development → Code Review → Testing → Deployment → Done"
5. Discover Classes of Service
Define how different types of work should be treated. Classes of service help you manage different priorities, risks, and expectations appropriately.
Example: "Expedite (handle immediately), Fixed Date (deadline-driven), Standard (normal flow), Intangible (improvement work)"
6. Design the Kanban System
Now that you understand your context, design your board. Define columns, swim lanes, WIP limits, and policies that address your sources of dissatisfaction.
Example: "Columns match workflow states, swim lanes for work types, WIP limits based on team capacity"
7. Establish Cadences
Define the regular meetings and rhythms that will support your Kanban system. When will you review the board? When will you replenish work? When will you review metrics?
Example: "Daily standup, weekly replenishment meeting, monthly service delivery review"
8. Establish Policies
Make explicit the rules and agreements about how work flows through your system. Clear policies reduce confusion and enable better decision-making.
Example: "Definition of Ready, Definition of Done, WIP limit policies, escalation procedures"
Key Principles
- Start with what you do now: Don't try to redesign everything at once. Understand your current system first.
- Agree to pursue evolutionary change: STATIK helps you design a starting point, not a final destination. Your system will evolve.
- Respect current roles and responsibilities: Work with your existing structure rather than forcing organizational change.
- Leadership at all levels: Everyone contributes to understanding and designing the system.
Practical Application
When using STATIK to design your Kanban board, you'll discover that the board itself is less important than the understanding you gain through the process. The conversations about workflow, policies, and service delivery create shared understanding that makes your Kanban system effective.
Your Kanban Swimlane Boards (KSB) app can be configured to reflect the design decisions you make through STATIK. The columns, swim lanes, and policies you define during the STATIK process directly inform how you set up your board.
Learn More
For a comprehensive understanding of STATIK and Kanban implementation, we recommend: