How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)

1. Organization and Architecture, Autonomy and Accountability Kevin Goldsmith  VP Engineering - Consumer @kevingoldsmith

2. How Spotify Builds Products Kevin Goldsmith  VP Engineering - Consumer @kevingoldsmith

3. How Spotify Builds Products (Manchester Remix) Kevin Goldsmith  VP Engineering - Consumer @kevingoldsmith

4. Some Principles

5. Speed of iteration beats quality of iteration - optimizing for speed leads to faster learning, including from failures, and faster learning leads to higher quality; optimizing for quality is an obstacle to speed, which undermines learning and slows down improvements to quality. Spotify Company Belief

6. Data >>> Opinion

7. DATA VISION EXPERIMENTSLEARNING PRODUCT INFORMS GUIDES GENERATES DRIVES PROVIDES

8. Speed without data means you aren’t learning

9. Data without speed means you aren’t learning fast enough

10. Autonomous teams go faster.

11. How many teams?

13. >100Teams

14. >100Teams autonomous

15. Autonomous adjective au·ton·o·mous - ȯ-ˈtä-nə-məs (of a country or region) having the freedom to govern itself or control its own affairs. "the federation included sixteen autonomous republics" having the freedom to act independently. "school governors are legally autonomous" synonyms: self-governing, independent, sovereign, free, self-ruling, self-determining, autarchic; self-sufficient "an autonomous republic" Full-Stack Autonomous Teams (Squads) PO UX iOS Android K&M QA Backend Agile Coach

16. Full-Stack Autonomous Teams PO UX iOS Android K&M QA Backend Agile Coach Fully empowered to fulfill their mission

17. Full-Stack Autonomous Teams PO UX iOS Android K&M QA Backend Agile Coach Collective Responsibility

18. Full-Stack Autonomous Teams PO UX iOS Android K&M QA Backend Agile Coach Individual Accountability

19. Full-Stack Autonomous Teams PO UX iOS Android K&M QA Backend Agile Coach No Manager?

23. Chapter Lead

24. Chapter Lead

25. Chapter Lead

26. Chapter Lead

29. Product Owner Agile Coach Chapter Lead Chapter Lead

30. Product Owner Agile Coach Chapter Lead Chapter Lead POCLAC

32. Squads

33. Squads

34. Squads Chapter Leads

35. Squads Chapters

36. Tribe Lead Squads Chapters

37. Tribe Squads Chapters Ideal size: 40-150 people

38. Tribe Squads Chapters

39. Tribe Squads Chapters Product Owner

40. Tribe Squads Chapters Product Owner User Experience

43. Product Area Leads

44. Design Leads

45. Trio TrioTrio

46. Guild

47. Trio TrioTrio

48. Alliance

49. Alliance

50. Organization Velocity=

51. Organization Velocity=

52. Organization VelocityEnables

53. Velocity is a core value at Spotify

54. Our organizational model supports ourvalues

55. Our organizational model supports ourvalues Not the otherway around

56. Requirements ofAutonomy

57. Autonomy needs communication

58. Autonomy needs context

59. Autonomy needs transparency

60. Autonomy needs trust

61. If you can’t trust the people you hire, you are bad at hiring people.

62. So

64. by giving teams context and trust

65. by giving teams context and trust and reducing dependencies on otherteams

66. by giving teams context and trust and reducing dependencies on otherteams they can make decisions on their own

67. by giving teams context and trust and reducing dependencies on otherteams they become AUTONOMOUS! they can make decisions on their own

68. Autonomous teams don’t have to synchronize with otherteams as often or get approval on decisions.

69. Autonomous teams don’t have to synchronize with otherteams as often or get approval on decisions. They can go faster.

70. Changeis constant

71. “Heisenberg Squads”

72. I'm not joking here. I can lock a tribe lead in a room and ask them repeatedly "so what squads do you have", and not get clear answers. It isn't a case of "it's hard to collect the information and keep it up to date" – it is a case of the wave-form of org-quantas not collapsing into reality until they are observed, and sometimes not even then. It's Schrödinger's squads, where sometimes the cat escaped before going in the box and sometimes the box gets stolen before opened. Mikael Krantz, Spotify Chief Architect

73. It is better to solve the problems created by fluidity rather than imposing more structure.

74. It is better to solve the problems created by fluidity rather than imposing more structure. Minimum Viable Bureaucracy

75. =Autonomy

76. =Autonomy Chaos?

77. =Autonomy Chaos?

80. How do we prevent the chaos?

81. What / Why

82. What / Why

83. What / Why How

84. What / Why How

85. Grow MAU Simplify Navigation

87. Investment Investment Time Think it Build it Ship it Tweak it

90. Investment Investment Time Think it Build it Ship it Tweak it Paper Prototypes UI Mockups User Testing MVP Employee Testing Gradual Rollout A/B Testing User Testing Analytics Validation A/B Testing User Testing Analytics ValidationBeta  Testing

91. That is still a lot of full- stack teams building the product!

92. Full-stack autonomous teams Requires structuring your application in loosely coupled parts

93. Microservices!

98. LoadBallancer

102. Microservices yay! Easierto scale based on real-world bottlenecks

103. Microservices yay! Easierto test

104. Microservices yay! Easierto deploy

105. Microservices yay! Easierto monitor

106. Microservices yay! Can be versioned independently

108. Microservices yay! Are less susceptible to large failures

110. Microservices boo! are harderto monitor

111. Microservices boo! need good documentation / discoverytools

113. Microservices boo! create increased latency

116. Microservices @ Spotify

117. Microservices @ Spotify ‣ 810activeservices

118. Microservices @ Spotify ‣ 810activeservices ‣ ~10Systemspersquad

119. Microservices @ Spotify ‣ 810activeservices ‣ ~10Systemspersquad ‣ ~1.7Systemsperpersonwithaccessto productionservers

120. Microservices @ Spotify ‣ 810activeservices ‣ ~10Systemspersquad ‣ ~1.7Systemsperpersonwithaccessto productionservers ‣ ~1.15Systemspermemberof Technology

121. Microservices @ Spotify

122. Microservices @ Spotify ‣ Owned/Operatedbysquads

123. Microservices @ Spotify ‣ Owned/Operatedbysquads ‣ On-callusuallyownedbychapters

124. Microservices @ Spotify ‣ Owned/Operatedbysquads ‣ On-callusuallyownedbychapters ‣ Significanttoolingcreatedby infrastructuretosimplifybuilding/ supporting

125. Microservices @ Spotify ‣ Owned/Operatedbysquads ‣ On-callusuallyownedbychapters ‣ Significanttoolingcreatedby infrastructuretosimplifybuilding/ supporting ‣ ArchitectureReviewsencouraged

126. Microservices @ Spotify ‣ Owned/Operatedbysquads ‣ On-callusuallyownedbychapters ‣ Significanttoolingcreatedby infrastructuretosimplifybuilding/ supporting ‣ ArchitectureReviewsencouraged ‣ SecurityReviewsrequired

127. Client

128. Server Core Library Platform Platform Platform Platform Infrastructure

134. Challenges

135. Challenges Synchronization

136. Challenges Synchronization Client UX implementation

137. Challenges Synchronization Client UX implementation depends on

138. Challenges Synchronization Client UX implementation Core Library Implementation depends on

139. Challenges Synchronization Client UX implementation Core Library Implementation depends on depends on

140. Challenges Synchronization Client UX implementation Core Library Implementation depends on depends on Server Implementation

141. Challenges Synchronization Client UX implementation Core Library Implementation depends on depends on depends onServer Implementation

142. Challenges Synchronization Client UX implementation Core Library Implementation depends on depends on depends onServer Implementation Infrastructure Implementation

146. Shared Frameworks

147. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam

148. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team

151. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team UI Interface Guidelines

152. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team Common UI Components UI Interface Guidelines

153. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team Common UI Components UI Interface Guidelines SharedTesting Frameworks

156. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release TeamUI Consistency Validation

157. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team IntegrationTesting UI Consistency Validation

158. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team IntegrationTesting App Submittal UI Consistency Validation

160. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team Shared DevelopmentTree

161. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team Shared DevelopmentTree Best Practice Sharing

162. Shipping @ speed

163. Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Development Stabilization Beta 1 Beta 2 Release

165. Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Development Stabilization Beta 1 Beta 2 Release

166. Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Development Stabilization Beta 1 Beta 2 Release Week 3 Week 4 Week 5 Week 6 Stabilization Beta 1 Beta 2 Release Week 1 Week 2 Week 3 Week 4 We Development Sta Beta 1 Bet

167. 4 Weeks Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Development Stabilization Beta 1 Beta 2 Release Week 3 Week 4 Week 5 Week 6 Stabilization Beta 1 Beta 2 Release Week 1 Week 2 Week 3 Week 4 We Development Sta Beta 1 Bet

168. 4 Weeks Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Development Stabilization Beta 1 Beta 2 Release Week 3 Week 4 Week 5 Week 6 Stabilization Beta 1 Beta 2 Release Week 1 Week 2 Week 3 Week 4 We Development Sta Beta 1 Bet 12 releases / year

169. Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Wee Development Week 4 Stabilization Release

170. 3 Weeks 3 Weeks3 Weeks Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Wee Development Week 4 Stabilization Release

171. 3 Weeks 3 Weeks3 Weeks Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Wee Development Week 4 Stabilization Release 17 releases / year

172. Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 We Development St Be

173. Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 We Development St Be 2 Weeks 2 Weeks 2 Weeks 2 Weeks 2 Weeks

174. Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 We Development St Be 2 Weeks 2 Weeks 2 Weeks 2 Weeks 2 Weeks

175. Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 We Development St Be 2 Weeks 2 Weeks 2 Weeks 2 Weeks 2 Weeks 26 releases / year

176. Whatdoesn’t workwell?

177. Big Projects

178. Big Projects ‣ Autonomousteamsmakescoordination difficult

179. Big Projects ‣ Autonomousteamsmakescoordination difficult ‣ Nofull-timeprojectmanagersin technologyorganization

180. Big Projects ‣ Autonomousteamsmakescoordination difficult ‣ Nofull-timeprojectmanagersin technologyorganization ‣ Veryunevenexecutionrecord

181. Big Projects ‣ Autonomousteamsmakescoordination difficult ‣ Nofull-timeprojectmanagersin technologyorganization ‣ Veryunevenexecutionrecord ‣ Gotintosomebadanti-patterns

182. Growing Senior Leaders

183. Growing Senior Leaders ‣ Tribeleadshavepeoplemanagement, strategyanddeliveryresponsibility

184. Growing Senior Leaders ‣ Tribeleadshavepeoplemanagement, strategyanddeliveryresponsibility ‣ ChapterLeadshavepeople managementresponsibilityandoperate inhighlyconsensus-driventeams

185. Resource Efficiency

186. Resource Efficiency ‣ Autonomousteamsareresourcehungry becausetheyneedtobeself-sufficient

187. Resource Efficiency ‣ Autonomousteamsareresourcehungry becausetheyneedtobeself-sufficient ‣ Teamscangetfocusedonimproving thingswithintheirsphereofcontrol, ignoringlargerissues

188. So…

189. So… ‣ Wewanttolearnfasterthanourcompetition

190. So… ‣ Wewanttolearnfasterthanourcompetition ‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast

191. So… ‣ Wewanttolearnfasterthanourcompetition ‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast ‣ Autonomousteamshelpusgofaster

192. So… ‣ Wewanttolearnfasterthanourcompetition ‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast ‣ Autonomousteamshelpusgofaster ‣ Looselycoupledarchitectureshelpautonomousteamsworkwithoutcoordination bottlenecks

193. So… ‣ Wewanttolearnfasterthanourcompetition ‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast ‣ Autonomousteamshelpusgofaster ‣ Looselycoupledarchitectureshelpautonomousteamsworkwithoutcoordination bottlenecks ‣ Reducingtimebetweenreleasesincreaseslearningopportunities

194. Questions? twitter: @kevingoldsmith

How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)

How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)

Recommended

More Related Content

What's hot

What's hot(20)

Similar to How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)

Similar to How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)(20)

More from Kevin Goldsmith

More from Kevin Goldsmith(20)

Recently uploaded

Recently uploaded(10)

How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)