"I'm overburdened." "Each task is urgent!".
All of the statements above are red flags and call for help. People loose motivation and energy, when they don't know which direction to go to finally break the blockers. If they ask for help, I propose the method, which helped many teams I had a chance to work with. It's called STATIK: System Thinking Approach to Implementing Kanban. Even, if it says explicitly "Kanban", the method is primarily about understanding, where you are and what your problem is.
The power of STATIK is hidden in its simplicity and methodical approaching the problematic state, in which team exists. Through the set of logical steps, it helps people to digest issues and find a specific, team-customized solution. Gathering the whole team in one place becomes the first catalyzing activity in a stalemate situation.
I would like to share the experience of working with multiple teams: developers, maintenance groups and business.
1 of 16
Download to read offline
More Related Content
What to do when you stuck in delivering? The way STATIK helps teams to move forward.
5. THE FATHERS OF STATIK
Dragos Dumitriu Kanban ("Blue Book") David J. Anderson
6. THE
STEPS
TO BE
TAKEN
Step 1: Understand what makes the service fit for purpose
Step 2: Understand sources of dissatisfaction
Step 3: Analyze demand
Step 4: Analyze capability
Step 5: Model workflow
Step 6: Discover classes of services
Step 7: Design the kanban system
Step 8: Socialize the design and negotiate implementation
7. SYMPTOM 1
"I have no idea who my customer is."
Then...
Understand what makes your service fit
for purpose for your customers.
First...
Understand who you deliver the service to.
8. SYMPTOM 2
"I feel so annoyed with everything."
Go into your customer's shoes: tell
yourselves, what customer may not like.
Identify internal sources of
dissatisfaction.
9. SYMPTOM 3
"I have no idea, what I'm doing."
Identify work item types.
Analyze work that comes from your
customers.
Identify classes of services.
10. SYMPTOM 4
"It's too much! I'm not able to do it."
Analyze work item types and associate
them with your capability.
Understand how capable you are to fullfill
your customers' requirements.
11. SYMPTOM 5
"What's going on in this process?"
Map the series of dominant steps to
discover new knowledge.
Model workflow for each work item type.
12. SYMPTOM 6
"I don't want to talk to them"
Listen respectfully to the others expressing
their feelings and observations.
Tell honestly, what you think about the
process (not people!).
13. WHAT ELSE
DOES HURT
YOU?
Team doesn't really care?
Bring them together in one room, give them time, space
and... let them talk.
Nothing can be improved?
Use STATIK sessions to look for your teammates ideas.
Afraid talking to your stakeholders?
Bring them data and information.
14. If you think you've
tried everything
already...
...try one more
time.
STATIK IS A WAY OF
UNDERSTANDING HOW A
SYSTEM BEHAVES AS A
WHOLE RATHER THAN
THROUGH ANALYSIS OF
COMPONENT PARTS IN
ISOLATION.
David J. Anderson
15. LETS TALK!
If you want to learn more about Kanban,
visit our webpage or YT channel.
You can find us on LinkedIn & Facebook.