Tweet
Tweet

Slide 1

Slide 1 text

Embracing Change or 
 Bracing for Change Fostering a Culture of Continuous 
 Improvement in Product Teams Emily Webber / @ewebber emilywebber.co.uk / tacitlondon.com

Slide 2

Slide 2 text

Hello. I’m Emily @EWEBBER

Slide 3

Slide 3 text

Write down:
 What is the vision for your team if everything was as good as it could be @EWEBBER

Slide 4

Slide 4 text

@EWEBBER Ideas Code Data MEASURE LEARN BUILD The Lean startup

Slide 5

Slide 5 text

@EWEBBER The Scientific method Ask a question Do background 
 research Construct a
 hypothesis Test your 
 hypothesis Analyse data 
 and draw 
 conclusions

Slide 6

Slide 6 text

Because I think [this] is true I think that doing [this] will mean [this will happen] And I will know [like this] @EWEBBER

Slide 7

Slide 7 text

Why aren’t your team already embracing change? @EWEBBER

Slide 8

Slide 8 text

Photo from musictour.eu @EWEBBER

Slide 9

Slide 9 text

Photo from musictour.eu @EWEBBER “This is just how we do
 things around here”

Slide 10

Slide 10 text

Five reasons people 
 resist change @EWEBBER

Slide 11

Slide 11 text

Photo by Jethro Taylor @EWEBBER “Uncertainty can cause more stress than inevitable pain” www.ucl.ac.uk/news/news-articles/0316/290316-uncertainty-stress

Slide 12

Slide 12 text

Photo by Jethro Taylor @EWEBBER Get into the habit 
 of changing

Slide 13

Slide 13 text

Photo by Jake Edwards @EWEBBER Change means 
 learning new skills

Slide 14

Slide 14 text

Photo by Jake Edwards @EWEBBER Be willing to support people learning new skills

Slide 15

Slide 15 text

Photo by Aaron Silvers @EWEBBER A condition in which a person suffers from a sense of powerlessness, arising from a traumatic event or persistent failure 
 to succeed. Learned helplessness

Slide 16

Slide 16 text

Photo by Aaron Silvers @EWEBBER Create a safe to fail environment

Slide 17

Slide 17 text

@EWEBBER It could mean throwing away their hard work

Slide 18

Slide 18 text

@EWEBBER Build on what 
 already exists

Slide 19

Slide 19 text

Photo by Nancy Kamergorodsky @EWEBBER They don’t understand the reason for change

Slide 20

Slide 20 text

Photo by Nancy Kamergorodsky @EWEBBER Have a vision for the future state

Slide 21

Slide 21 text

Evolution vs revolution @EWEBBER

Slide 22

Slide 22 text

@EWEBBER Satir Change Curve /stevenmsmith.com/ar-satir-change-model/

Slide 23

Slide 23 text

AVOID CHAOS (unless you need a revolution) @EWEBBER

Slide 24

Slide 24 text

@EWEBBER Kaizen

Slide 25

Slide 25 text

@EWEBBER Understand the direction of challenge Grasp the current condition Establish the next target condition Experiment towards the target condition Planning phase Executing phase Improvement Kata

Slide 26

Slide 26 text

Because I think [this] is true I think that doing [this] will mean [this will happen] And I will know [like this] @EWEBBER

Slide 27

Slide 27 text

Photo by Elaine with Grey Cats @EWEBBER

Slide 28

Slide 28 text

Telling @EWEBBER

Slide 29

Slide 29 text

@EWEBBER https://www.youtube.com/watch?v=9ACi-D5DI6A

Slide 30

Slide 30 text

@EWEBBER https://www.youtube.com/watch?v=9ACi-D5DI6A

Slide 31

Slide 31 text

@EWEBBER https://www.youtube.com/watch?v=9ACi-D5DI6A

Slide 32

Slide 32 text

@EWEBBER https://www.youtube.com/watch?v=9ACi-D5DI6A

Slide 33

Slide 33 text

Questioning @EWEBBER

Slide 34

Slide 34 text

@EWEBBER https://www.youtube.com/watch?v=9ACi-D5DI6A

Slide 35

Slide 35 text

@EWEBBER https://www.youtube.com/watch?v=9ACi-D5DI6A

Slide 36

Slide 36 text

@EWEBBER https://www.youtube.com/watch?v=9ACi-D5DI6A

Slide 37

Slide 37 text

@EWEBBER https://www.youtube.com/watch?v=9ACi-D5DI6A

Slide 38

Slide 38 text

@EWEBBER https://www.youtube.com/watch?v=9ACi-D5DI6A

Slide 39

Slide 39 text

Identifying what to change @EWEBBER

Slide 40

Slide 40 text

On a regular basis the team get together to reflect on how they work together and find ways to improve The Agile Retrospective @EWEBBER

Slide 41

Slide 41 text

@EWEBBER Have you been part of a retrospective? within the last 6 months within the last 3 months within the last month within the last 2 weeks

Slide 42

Slide 42 text

Photo by J Marks Dodds The 30 second retrospective @EWEBBER

Slide 43

Slide 43 text

@EWEBBER 1. What is the next improvement for your team? 2. What one change can you make towards it? 3. How will you know it’s worked?

Slide 44

Slide 44 text

@EWEBBER 1. What is the next improvement for your team? 2. What one change can you make towards it? 3. How will you know it’s worked?

Slide 45

Slide 45 text

@EWEBBER Lots of ideas at retrospectivewiki.org

Slide 46

Slide 46 text

Some other 
 techniques @EWEBBER

Slide 47

Slide 47 text

• map out your pain points • review your blockers • #retro slack channel • one to ones • five whys @EWEBBER

Slide 48

Slide 48 text

Remember… @EWEBBER

Slide 49

Slide 49 text

Change is hard @EWEBBER

Slide 50

Slide 50 text

Understand what direction you are 
 heading in @EWEBBER

Slide 51

Slide 51 text

Use experimentation and the scientific method @EWEBBER

Slide 52

Slide 52 text

Make small changes @EWEBBER

Slide 53

Slide 53 text

Get into the habit of experimenting @EWEBBER

Slide 54

Slide 54 text

Embrace change, don’t brace for change @EWEBBER

Slide 55

Slide 55 text

Thank you. Emily Webber @ewebber emilywebber.co.uk / tacitlondon.com