culture eats devops for breakfast

29
Culture eats DevOps for Breakfast DevOps Summit Chris Flink @chrisflink

Upload: chris-flink

Post on 16-Apr-2017

510 views

Category:

Leadership & Management


2 download

TRANSCRIPT

Page 1: Culture eats DevOps for Breakfast

Culture eats DevOps for Breakfast

DevOps Summit Chris Flink

@chrisflink

Page 2: Culture eats DevOps for Breakfast

What is DevOps about?

The Cloud?

DevOpsSummitBrussels @chrisflink

Page 3: Culture eats DevOps for Breakfast

What is DevOps about?

10 Deploys a day?

DevOpsSummitBrussels @chrisflink

Page 4: Culture eats DevOps for Breakfast

What is DevOps about?

The Tools?

DevOpsSummitBrussels @chrisflink

Page 5: Culture eats DevOps for Breakfast

DevOps is about…

•  Not ( just) the tools, but the people •  Separate Goals and Means

•  Not ( just) the people, but the culture •  Make people feel safe and co-operate

•  Not ( just) the culture, but the behaviour •  It is what you do, how you react, how you behave

DevOpsSummitBrussels @chrisflink

Page 6: Culture eats DevOps for Breakfast

The questions are

•  How to make two departments collaborate •  How do you build a strong culture and influence

behaviour?

DevOpsSummitBrussels @chrisflink

Page 7: Culture eats DevOps for Breakfast

Implementing DevOps is about Changing Organisational Culture Nolost Capital helps companies create and maintain a culture that enables them to be

successful and achieve business goals.

•  Using: Research, Data Analysis, Science •  Providing: Business Intelligence, Coaching, Interventions

•  Chris Flink – Co-Founder •  Data / Process / People / IT •  Computer Science, Business and Psychology

DevOpsSummitBrussels @chrisflink

Page 8: Culture eats DevOps for Breakfast

A short story

Tension between office and outside sales force

“Why can’t they pay more attention to the quality of their notes for the offer?”

“Why are they always complaining, can’t they

see I’m busy generating business?”

DevOpsSummitBrussels @chrisflink

Page 9: Culture eats DevOps for Breakfast

The problem is not unique

•  MarSals (Marketing – Sales)? •  ManLogs (Manufactoring – Logistics)?

•  What can we learn from this?

DevOpsSummitBrussels @chrisflink

Page 10: Culture eats DevOps for Breakfast

What’s causing the behaviour

•  Different goals and targets •  No understanding of the peculiarities of each

others work •  Busy doing ‘their ’ work and no time for each

other •  No dialog, no constructive feedback, just

blaming

DevOpsSummitBrussels @chrisflink

Page 11: Culture eats DevOps for Breakfast

Find a shared goal

•  Search for a broader perspective •  Get together and have a dialog

•  Hint: Look at the company’s mission

•  Make Customers Happy •  Enable the Business •  Grow number of projects / clients / users •  Etc.

DevOpsSummitBrussels @chrisflink

Page 12: Culture eats DevOps for Breakfast

Define a shared strategy

•  How to achieve this goal together

DevOpsSummitBrussels @chrisflink

Page 13: Culture eats DevOps for Breakfast

Make it fun!

DevOpsSummitBrussels @chrisflink

TheFunTheory-h;p://www.youtube.be/watch?v=2lXh2n0aPyw

Page 14: Culture eats DevOps for Breakfast

It’s never ready

•  Continuous Feedback and learning

DevOpsSummitBrussels @chrisflink

Page 15: Culture eats DevOps for Breakfast

Second Question

How do you build a strong culture and

influence behaviour?

DevOpsSummitBrussels @chrisflink

Page 16: Culture eats DevOps for Breakfast

Story: Coolblue •  Fast growing company •  Doubling in size every 20 months •  € 500+ million turnover •  Secret of their success?

– A very strong focus on the customer (external) and organisation culture (internal)

Source: https://www.youtube.com/watch?v=CahqmZPZfVc (Dutch)

DevOpsSummitBrussels @chrisflink

Page 17: Culture eats DevOps for Breakfast

Approach

•  Know where you stand and where you are coming from

•  Know where you want to go •  Know what steps to take when

DevOpsSummitBrussels @chrisflink

Page 18: Culture eats DevOps for Breakfast

Assess current situation

•  Employee research (questionnaires, interviews, ...) –  What is working well and should be secured –  What is not and should be changed –  Hidden frustrations, incomprehension, resistance

•  Management / Stakeholder interviews –  Business objectives –  Restrictions –  Willingness to change

DevOpsSummitBrussels @chrisflink

Page 19: Culture eats DevOps for Breakfast

What do you want to achieve

•  What is the desired behaviour? – Make it explicit: “After helping someone, you always ask if everything is clear and if there is anything else he / she needs help with” “When someone makes an error we don’t judge but ask how we can help to recover first, and ask how we can prevent it in the future after”

DevOpsSummitBrussels @chrisflink

Page 20: Culture eats DevOps for Breakfast

Take the right step at the right time

•  Laws of Psychology apply – Maslow Pyramid – Adam’s Equity model

DevOpsSummitBrussels @chrisflink

Page 21: Culture eats DevOps for Breakfast

DevOpsSummitBrussels @chrisflink

Page 22: Culture eats DevOps for Breakfast

Start!

•  Make sure everybody feels safe – To make errors – To be unknowing – To speak up

•  Plan time to evaluate, give feedback, and discuss improvements – Sometimes standing still is the best way to make

progress

DevOpsSummitBrussels @chrisflink

Page 23: Culture eats DevOps for Breakfast

Applied to DevOps

•  Know your target group (no stereotyping but often…)

– Technical – Data and metrics driven – Love their tools – Communication (feedback) skills – Combine with values of Open Source Culture

DevOpsSummitBrussels @chrisflink

Page 24: Culture eats DevOps for Breakfast

Things to take into account

•  It’s a continuous process •  Group influence is a very strong driver for

behaviour

DevOpsSummitBrussels @chrisflink

Page 25: Culture eats DevOps for Breakfast

Things to take into account

DevOpsSummitBrussels @chrisflink

TheAschExperiment-h;ps://www.youtube.com/watch?v=qA-gbpt7Ts8

Page 26: Culture eats DevOps for Breakfast

Things to take into account

•  Support and train people where required

•  You are the example •  Make it fun!

DevOpsSummitBrussels @chrisflink

Page 27: Culture eats DevOps for Breakfast

Benefits of strong culture

•  Easier to attract and hire talent •  Lower employee turnover •  Happy employees

– Are more productive – Make less errors – Have lower absenteeism rate – Are more resilient

DevOpsSummitBrussels @chrisflink

Page 28: Culture eats DevOps for Breakfast

Questions?

DevOpsSummitBrussels @chrisflink

Page 29: Culture eats DevOps for Breakfast

Thank you!

Contact: nolostcapital.nl

[email protected] @chrisflink

DevOpsSummitBrussels @chrisflink