I got Trapped!
Systems thinking traps
of IT Teams
and how to battle them
Slide 2
Slide 2 text
2
@kenny_baas
Slide 3
Slide 3 text
3
@kenny_baas
The hands that manipulate it
suppress or release some behaviour
that is latent within
the structure of the spring
Slide 4
Slide 4 text
4
@kenny_baas
A system is an interconnected set of
elements that is coherently organized in
a way that achieves something.
(Function or Purpose)
Slide 5
Slide 5 text
5
@kenny_baas
Some systems examples
Slide 6
Slide 6 text
6
@kenny_baas
Element
Interconnections
Function/Purpose
Most easy to observe
and change
Changes greatly
alters the system
Least obvious and
changes can be drastic
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
8
@kenny_baas
Inflow Outflow
Water in tub
(Stock)
Slide 9
Slide 9 text
9
@kenny_baas
Slide 10
Slide 10 text
10
@kenny_baas
Inflow Outflow
Water in tub
(Stock)
desired temperature
Discrepancy
B B
20
@kenny_baas
The way out
Take the focus off short-term relief and put it on
long-term restructuring.
Slide 21
Slide 21 text
A group of people is not a team,
focus on collaboration as a team.
Slide 22
Slide 22 text
22
@kenny_baas
Guiding heuristic
Focus on team collaboration
Slide 23
Slide 23 text
23
Slide 24
Slide 24 text
24
@kenny_baas
Other examples
“Temporary code or fix”
Hire more manual testers
Hire more developers
Security
Operations
Consultants
Slide 25
Slide 25 text
No content
Slide 26
Slide 26 text
26
@kenny_baas
Drift to low performance
Slide 27
Slide 27 text
27
@kenny_baas
The way out
Keep performance standard absolute.
Let standards be enhanced by
the best actual performance.
Slide 28
Slide 28 text
28
@kenny_baas
Guiding heuristics
Make agreements on team standards,
improve collaboration by mobbing and pairing.
Keep repeating and reiterating
on made agreements.
Slide 29
Slide 29 text
No content
Slide 30
Slide 30 text
30
@kenny_baas
Other observations
Sprint forecasting
Slide 31
Slide 31 text
31
@kenny_baas
Slide 32
Slide 32 text
Success to Successful
Slide 33
Slide 33 text
33
@kenny_baas
The way out
Diversification
Slide 34
Slide 34 text
34
@kenny_baas
Guiding heuristics
Pair up with new team members
Slide 35
Slide 35 text
35
@kenny_baas
guiding heuristics
Focus on (neuro)diversity,
everyone is an individual and different.
Focus on equality,
equal access to opportunities
Focus on inclusion,
create a sense of belonging.
Slide 36
Slide 36 text
36
@kenny_baas
guiding heuristics
Create collective autocracy within teams.
Slide 37
Slide 37 text
37
@kenny_baas
Slide 38
Slide 38 text
38
@kenny_baas
Other observations
Maturity models and job hierarchy with promotions
can lead to:
Peter principle
Social darwinism
Slide 39
Slide 39 text
39
@kenny_baas
Slide 40
Slide 40 text
Policy Resistance
Slide 41
Slide 41 text
41
@kenny_baas
The way out
Bring in all the actors and
seek out mutually satisfactory ways
for all goals to be realised
Slide 42
Slide 42 text
42
@kenny_baas
Slide 43
Slide 43 text
43
@kenny_baas
Slide 44
Slide 44 text
44
@kenny_baas
How many beans?
Slide 45
Slide 45 text
45
@kenny_baas
Slide 46
Slide 46 text
46
@kenny_baas
How many beans?
Slide 47
Slide 47 text
47
@kenny_baas
Slide 48
Slide 48 text
48
@kenny_baas
How many beans?
Slide 49
Slide 49 text
49
@kenny_baas
Guiding heuristic
Create a shared mindset
of how software is delivered.
Use visualisation and measure the delivery.
60
@kenny_baas
The way out
Reflect the real welfare of the system.
Don’t confuse effort with result.
Slide 61
Slide 61 text
61
@kenny_baas
Guiding heuristics
The team should be autonomous,
focus on result rather than effort.
Slide 62
Slide 62 text
62
@kenny_baas
"When a measure becomes a target,
it ceases to be a good measure."
- Goodhart's law
Slide 63
Slide 63 text
63
@kenny_baas
Other observation
unrealistic deadlines
Ops solving incidents
Slide 64
Slide 64 text
No content
Slide 65
Slide 65 text
Tragedy of the commons
Slide 66
Slide 66 text
66
@kenny_baas
Other observations
Shared data to reports
Shared database
end to end (chain) testing
Slide 67
Slide 67 text
67
@kenny_baas
The way out
Educate, exhort and create awareness,
so people understand
the consequences of abusing the resource.
Restore or strengthen the feedback loop
by privatizing or giving direct consequences.
Slide 68
Slide 68 text
68
@kenny_baas
Guiding heuristics
Make a team owner of the shared library.
Slide 69
Slide 69 text
69
@kenny_baas
Guiding heuristics
Put in place proper CI/CD
Only change the software when
other team(s) collectively reviewed it.
Slide 70
Slide 70 text
No content
Slide 71
Slide 71 text
71
@kenny_baas
If we have a system of improvement
that is directed at improving the parts
taken separately.
You can be absolutely sure that the
improvement of the whole
will not be improved.
https://www.youtube.com/watch?v=OqEeIG8aPPk
Russ Ackoff
Slide 72
Slide 72 text
72
@kenny_baas
Slide 73
Slide 73 text
73
@kenny_baas
Order Payment Packaging
Slide 74
Slide 74 text
No content
Slide 75
Slide 75 text
@kenny_baas
Big Picture EventStorming
https://leanpub.com/ddd_first_15_years
Slide 76
Slide 76 text
@kenny_baas credits: Ruth Malan
Slide 77
Slide 77 text
@kenny_baas
When you start judging,
you stop listening and learning