The document introduces STATIK, a repeatable process for implementing Kanban. STATIK stands for 0) understand purpose, 1) understand sources of dissatisfaction, 2) analyze demand and capability, 3) model the knowledge discovery process, 4) discover classes of service, 5) design Kanban systems, and 6) roll out. It discusses each step in STATIK for understanding the current system and designing an improved Kanban system to enable continuous improvement through evolutionary change. The overall goal of STATIK and Kanban is to achieve sustained, purposeful change through understanding, agreement, respect, collaboration, transparency, balance and flow.

1. Introducing Kanban
(using STATIK)
Mike Burrows
@asplake
@KanbanInside
mike@djaa.com
Introducing Kanban (using STATIK) @asplake #investni

2. Continuous improvement:
• Very hard to sustain on its own
• Creative knowledge work presents its own special
Introducing Kanban (using STATIK) @asplake #investni
challenges

3. The Kanban Method
• “Evolutionary change for your technology business”
(Anderson)
• The humane, “start with what you do now” approach to
change (@KanbanInside)
• Developed pragmatically by and for people engaged
in creative knowledge work
Introducing Kanban (using STATIK) @asplake #investni

4. • A new name for the Kanban Method’s best-kept secret
• A repeatable (and humane) way to get started with
Introducing Kanban (using STATIK) @asplake #investni
Kanban
• A way to invigorate even the most shallow of
implementations
STATIK

5. STATIK
0. Understand the purpose of the system
1. Understand sources of dissatisfaction
2. Analyze demand and capability
3. Model the knowledge discovery process
4. Discover classes of service
5. Design kanban systems
6. Roll out
Introducing Kanban (using STATIK) @asplake #investni

6. Reverse STATIK
0. Understand the purpose of the system
1. Understand sources of dissatisfaction
2. Analyze demand and capability
3. Model the knowledge discovery process
4. Discover classes of service
5. Design kanban systems
6. Roll out
Introducing Kanban (using STATIK) @asplake #investni

7. 5. Kanban systems
Introducing Kanban (using STATIK) @asplake #investni

8. 5. Kanban systems
How well is our work represented?
Introducing Kanban (using STATIK) @asplake #investni

9. 5. Kanban systems
How well does it support our workflow?
Introducing Kanban (using STATIK) @asplake #investni

10. 5. Kanban systems
~~~~~ ~~ ~~
~~~ ~~~~~~
Policies?
~~~ ~~
~~~ ~~
~~~~~ ~~ ~~
~~~ ~~~~~~
Introducing Kanban (using STATIK) @asplake #investni

11. 5. Kanban systems
4
Limits on work-in-progress (WIP)?
Introducing Kanban (using STATIK) @asplake #investni

12. 5. Kanban systems
4
Limits on work-in-progress (WIP)?
Introducing Kanban (using STATIK) @asplake #investni

13. 5. Kanban systems
4
Limits on work-in-progress (WIP)?
Introducing Kanban (using STATIK) @asplake #investni

14. 5. Kanban systems
Is our capacity respected when we replenish & commit?
Introducing Kanban (using STATIK) @asplake #investni

15. 5. Kanban systems
Do we coordinate deliveries effectively, commit at the right time?
Introducing Kanban (using STATIK) @asplake #investni

16. 5. Kanban systems
Effective feedback loops?
Introducing Kanban (using STATIK) @asplake #investni

17. 5. Kanban systems
Introducing Kanban (using STATIK) @asplake #investni

18. 4. Classes of service
5. Kanban systems
Review:
• Different types of work items and where
they sit
• WIP limits and other controls on WIP
• Commitment points
• Policies
• Feedback loops
6. Roll out
Introducing Kanban (using STATIK) @asplake #investni

19. 4. Classes of service
Managing to different kinds of expectations
Introducing Kanban (using STATIK) @asplake #investni

20. 4. Classes of service
Managing to different kinds of expectations
Introducing Kanban (using STATIK) @asplake #investni
Fixed Date

21. 4. Classes of service
Expedited Fixed Date
Managing to different kinds of expectations
Introducing Kanban (using STATIK) @asplake #investni

22. 4. Classes of service
Standard Expedited Fixed Date
Managing to different kinds of expectations
Introducing Kanban (using STATIK) @asplake #investni

23. 4. Classes of service
Standard Expedited Intangible Fixed Date
Managing to different kinds of expectations
Introducing Kanban (using STATIK) @asplake #investni

24. 4. Classes of service
Q: Fixed Date, Expedited, Standard or Intangible?
1. Manually add space to a server that has reached 90% full
2. Roll out an automated disk space provisioning system
3. Fix the server that is keeping the trading system out of the
market (and costing us $1m per hour)
4. Report to the board next Friday to explain ourselves
Introducing Kanban (using STATIK) @asplake #investni

25. 3. Knowledge discovery process
4. Classes of service
• Recognise different kinds of customer
expectation
• Qualitative categories before any
quantitative ranking
• Make explicit both internally and externally
• Select (prioritise) and risk-manage items
accordingly
6. Kanban systems
Introducing Kanban (using STATIK) @asplake #investni

26. 3. Knowledge discovery process
What don’t we know?
Introducing Kanban (using STATIK) @asplake #investni

27. 3. Knowledge discovery process
What are we discovering here?
Introducing Kanban (using STATIK) @asplake #investni

28. 3. Knowledge discovery process
Or here?
Introducing Kanban (using STATIK) @asplake #investni

29. 2. Demand & capability
3. Knowledge discovery process
• Creative knowledge work demands a shift:
• away from taking orders, satisfying
requirements
• towards building the capability to anticipate,
explore & meet needs at the right time
• Understand what kind of knowledge is acquired
at each stage of the process
• Implement through customer validation,
collaboration, policies, allocations
4. Classes of service
Introducing Kanban (using STATIK) @asplake #investni

30. 2. Demand & capability
Demand
• How work arrives
• How frequently
• From whom
• Of what types
• In what sizes
• etc
Capability
• How work leaves
• Batches
• Lead time(s), delivery rate
• Predictability
• Flow efficiency
• etc
Are these in balance?
Introducing Kanban (using STATIK) @asplake #investni

31. 2. Demand & capability
Demand
• Weekly calls with business
Introducing Kanban (using STATIK) @asplake #investni
managers
• Ad-hoc meetings with user reps
• Mostly business-driven work;
some market-driven, regulatory
and infrastructure change
• Typically 2-10 days
development work per item
Capability
• Releases every 6 weeks
• But ~18 week lead time
• Flow efficiency percentage in
single digits
• (5 days in 18 weeks is 4%)
Outline example

32. 1. Sources of dissatisfaction
2. Demand & capability
• Attend to both sides of this equation
• Outside-in as well as inside-out
• Expect changes at the boundaries to impact
system design, and vice-versa
3. Knowledge discovery process
Introducing Kanban (using STATIK) @asplake #investni

33. 1. Sources of dissatisfaction
Internal
External
Introducing Kanban (using STATIK) @asplake #investni

34. 0. Purpose
1. Sources of dissatisfaction
• Outside-in as well as inside-out
• Assumes a system scope and a boundary,
both potential sources of dissatisfaction in
their own right
• Sources are much easier to identify when
there is already some transparency
2. Demand & capability
Introducing Kanban (using STATIK) @asplake #investni

35. “STATIK Lite”
0. Understand the purpose of the system
1. Understand sources of dissatisfaction
2. Analyze demand and capability
3. Model the knowledge discovery process
4. Discover classes of service
5. Design kanban systems
6. Roll out
Introducing Kanban (using STATIK) @asplake #investni

36. Introducing Kanban (using STATIK) @asplake #investni
0. Purpose
What Who WHY

37. STATIK-0
0. Understand the purpose of the system
1. Understand sources of dissatisfaction
2. Analyze demand and capability
3. Model the knowledge discovery process
4. Discover classes of service
5. Design kanban systems
6. Roll out
Introducing Kanban (using STATIK) @asplake #investni

38. Sustained, purposeful change with Kanban
0. Understand the purpose of the system
1. Understand sources of dissatisfaction
2. Analyze demand and capability
3. Model the knowledge discovery process
4. Discover classes of service
5. Design kanban systems
6. Roll out
Introducing Kanban (using STATIK) @asplake #investni

39. Sustained, purposeful change with Kanban
0. Understand the purpose of the system
1. Understand sources of dissatisfaction
2. Analyze demand and capability
3. Model the knowledge discovery process
4. Discover classes of service
5. Design kanban systems
6. Roll out
Understanding
Introducing Kanban (using STATIK) @asplake #investni
Agreement
Respect
Collaboration
Transparency Balance Flow
Leadership

40. Resources
B L U E
H O L E
P RESS
B L U E
H O L E
P RESS
Introducing Kanban (using STATIK) @asplake #investni
Kanban from the Inside print cover FINAL OUTLINED 270 pages.indd 1 9/1/2014 10:43:40 PM

41. Autumn Conference Series
Moscow, London, Paris, Istanbul, Hamburg, Bangalore
– see conf.leankanban.com
Introducing Kanban (using STATIK) @asplake #investni

42. More Resources
Community Connections
Coaching Tools
Games
See positiveincline.com/index.php/resources/
Introducing Kanban (using STATIK) @asplake #investni

43. Thank you!
Mike Burrows
@asplake
@kanbanInside
mike@djaa.com
Introducing Kanban (using STATIK) @asplake #investni