STATIK Kanban

The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Read more
Article

The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in a full continuously improving system design.

1. Understand the purpose of the system

Explore who your customers are and how you generate value for them. What, for whom and why are you doing what you are doing?

2. Identify sources of dissatisfaction

Determine the areas in service delivery that are considered unsatisfactory. Visualize internal and external sources of dissatisfaction.

3. Analyze demand

Evaluate customer requests with regard to channels, types of work, and demand patterns. What are the sources, arrival rates of requests, and where do they originate?

4. Analyze system capabilities

Assess the capability of meeting customer demand in quantity, type, speed, and predictability. Compare expectations with actual capabilities.

5. Model the workflow

Find the activities that every type of work item goes through which may serve as columns on the board. Think of it as value-stream mapping.

6. Identify classes of service

How the different types of work items are treated after entering the system. Take advantage of the cost of delay to identify the classes.

7. Design the Kanban system

Utilizing insights from the previous, design the Kanban system accordingly. Use WIP limits, explicit policies, cadences, and progress tracking.

8. Socialize the design and negotiate expectations

Get feedback from internal and external parties. Hold workshops to sync the processes of other Kanban systems.

Kanban STATIK Diagram

STATIK - Systems Thinking Approach To Introducing Kanban

Similar posters

Minto Pyramid
Minto Pyramid The Minto Pyramid Principle, a communication framework, advocates for a top-down approach to convey messages effectively
Spotify Health Check
Spotify Health Check The Spotify Health Check is a workshop, where teams assess their project and collaboration using 11 dimensions.
Maslow's Hierarchy Of Needs
Maslow's Hierarchy Of Needs Maslow's hierarchy of needs links basic human needs and desires, emphasizing that survival needs must be met before higher needs.
RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices 6 Kanban Practices: Visualize, Limit WIP, Manage Flow, Make policies explicit, Implement feedback loops, Improve collaboratively
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.