Leadership @ Spotify by Kristian Lindwall at the Lean IT Summit 2014

Preview:

DESCRIPTION

Spotify has been growing quickly as a company, and they are continuously experimenting with ways of making the company work as effectively as possible. At the Lean IT Summit 2014, Kristian explained how management and leadership work in a large agile organization like Spotify. Find out what leadership looks like in a large agile organization? How can a leader support autonomy and alignment? How different forms of leadership – both formal and informal, product, organizational and technical – overlap and interact to create successful teams. More Lean IT on www.lean-it-summit.com

Citation preview

1 Section name

Scaling Agile @ Spotify •  Released oct 2012 •  Presented at Agile 2013 •  Many questions around leadership •  How do you make decisions?

2

40M active users. 10M paying subscribers.

1.5B playlists.

3

56 countries

Growing  fast  

30  

4  years  ago  

Growing  fast  

Now  

350 50 50

150 10

Structure for innovation

Section name 7

Vision and purpose

Alignment with the organization

Personal and professional growth

Any act in support of these is an act of leadership

Highly effective

x 75

Autonomy Continuous learning and improvement

Section name 8

9

Container squads

IOS Android Desktop Web

Feature squads

Infrastructure squads

Enable & support

Enable & support

Enable & support

Section name 10

Chapters

P Squad

P P P Squad Squad Squad

Chapter

Chapter

Section name 11

Tribes

P P P P Squad Squad Squad Squad

Chapter

Chapter

P P P P Squad Squad Squad Squad

Chapter

Chapter

Tribe Tribe

Hierarchy of needs at Spotify

Section name 13

Maslow

•  Self-actualization

•  Self-esteem

•  Belonging

•  Safety

•  Physiological

Section name 14

Maslow

•  Physiological – kickass work environment

Section name 15

Maslow

•  Safety – no fear culture, embrace failure

”We  aim  to  make  mistakes  faster  than  anyone  else.”  

Section name 16

Maslow

•  Belonging – social events, strong teams, tribes...

Section name 17

Maslow

Formal leadership roles

Section name 19

Chapter Lead

•  Grow individuals •  Grow chapter competence •  Hire the right people •  Salary reviews

P Squad

P P P Squad Squad Squad

Chapter

Chapter CL

P C

CL

CL

20 Section name

•  What do we do – and why?

•  Product vision •  Squad mission •  Purpose •  Alignment •  Support the squad

Product Owner P

21 Section name

Product Owner framework •  Working with the world •  Working with the product •  Working with the squad •  Working with the process

P

22 Section name

Example How we created an artist page roadmap together

Product Owner P

23 Section name

Agile Coach

•  Grow high performing teams •  Continuous improvement •  Ways of working •  Collaboration •  Grow a high performing organization

P C

Levels of agile coaching, The agile coaching institute

24 Section name

juli  29,  2014  

juli  29,  2014  

We  definitely  do  the  basics...  

Scrum  

Kanban  

User  stories  

Stand  ups  

Retrospec:ves  

Sprints  

Planning  Poker  XP  

Story  Points  Demos  

25 Section name

•  Team members

•  Product owners

•  Chapter leads

•  Senior management

1 on 1 coaching

26 Section name

•  Group of coaches came up with new

visualization

•  Ran workshops with all squads in a tribe

Squad roadmapping

27 Section name

•  Maturity workshops

•  Big cultural shift

•  Cross tribe initative

Continuous delivery

Section name 28

Chapter (Team) lead Product Owner

Agile Coach ”POTLAC”

How  can  we  support  our  squad?  

Squad support P CL AC

Section name 29

Tribe Lead

P Squad

P P P Squad Squad Squad

Chapter

Chapter

Tribe

•  High-performing tribe •  Grow strong chapter leads •  Coach the agile coaches •  Build a strong tribe leadership team

Section name 30

Tribe Leadership Team

P

P

P

P

Tribe lead, CL, PO, AC Examples •  Recruitment / onboarding •  Grow high-performing tribe and

teams •  Culture •  Alignment

31

Dysfunctional leadership team

Good manager

Bad manager

Strong leadership team P CL AC

Leadership teams

Growing high performing squads

Section name 33

Dependency and inclusion

Counter-dependency and

fight Trust and structure

Work and productivity

1

2 3

4

TEAM DYNAMICS RESULT DRIVEN ACTIVITIES

Lean & Agile methods

Innovation

Speed

Quality Value

High-performing squads

Section name 34

Dependency and inclusion

Counter-dependency and

fight Trust and structure

Work and productivity

1

2 3

4

TEAM DYNAMICS RESULT DRIVEN ACTIVITIES

Lean & Agile methods

Innovation

Speed

Quality Value

High-performing squads

Section name 35

Alignment

Autonomy

Autonomy vs. Alignment

Section name 36

Alig

nmen

t

Autonomy

Micromanaging organization Indifferent culture

Authoritative organization Conformist culture

Entrepreneurial organization

Chaotic culture

Innovative organization

Collaborative culture

Autonomy vs. Alignment

Section name 37

Innovative organization

Collaborative culture

Supporting squad autonomy

Section name 38

Example: Ongoing experiment with Priorities

Section name 39 Example: Dominating individuals in a squad

1.  Give  feedback  2.  Improve  team  dynamics  3.  Reinforce  feedback  culture  4.  Nurture  informal  

leadership  P CL AC

Section name 40

1.  DraK  new  missions  2.  Facilitate  squad  split  3.  Support  individuals  4.  Kick-­‐off  new  squads  

P CL AC

Example: A squad is growing too big

Growing a high performing organization

42

CTO

Tribe lead Tribe lead Tribe lead

Chapter lead

Engineer Engineer Engineer

Chapter lead Agile coaches

CPO

VP Product VP Product

Product Owner Product Owner

The reporting structure

43

CTO

Tribe lead Tribe lead Tribe lead

Chapter lead

Engineer Engineer Engineer

Chapter lead Agile coaches

CPO

VP Product VP Product

Product Owner Product Owner

supporting The reporting structure

Section name 44

Organic structure If you need to know exactly

who is making decisions, you are in the wrong place

How  do  we  know  how  we’re  doing?  

46 Section name

Squad health check

47 Section name

Section name 48

Summary

Cause -> Effect

-­‐  Go  for  the  minimum  viable  org  structure  -­‐  Trust  people  and  give  them  the  freedom  to  innovate  and  perform  -­‐  Create  Tght  feedback  loops  

49 Section name

TODO: INSERT PICTURE OF US?

Thank you!

KrisTan  Lindwall  @klindwall    

Recommended