@tomboothCentralising the rightthingsTom Booth
View Slide
@tombooth
@tomboothtl;dr
@tomboothBuild a central team toempower and supportothers
@tomboothCentralisedDecentralisedRe-centralised
@tomboothWe weren’t one business,we were compe>ng func>ons
@tomboothProtec>onism built throughcompe>>on
@tomboothEvery 3 weeks, …
@tomboothEvery 3 weeks, we had awild ride of forgoHenchanges
@tomboothOpera>ons would get theblame for developer problems
@tomboothWhy did their change breakmy code?
@tomboothCentrally provided toolswere very poor
@tomboothGeLng features to ourusers was slowWhen we were centralised,
@tomboothChange was complexbecause of poor designWhen we were centralised,
@tomboothFunc>onal ownershipcaused serious fric>onWhen we were centralised,
@tomboothOne team needs to own thewhole service
@tomboothYou have to embracechange
@tomboothDeploying con>nuously isbeHer for users
@tomboothA team should own its ownarchitecture and infrastructure
@tomboothEvery team with their owndirec>on, liHle shared
@tomboothSolving the same problems,in the same way withdifferent implementa>ons
@tomboothOpera>ng at larger scalerequires deeper knowledge
@tomboothChange is complex becauseof poor architectureWhen we were centralised,
@tomboothThe same problems werebeing solved repeatedlyWhen we were decentralised,
@tomboothNo-one has the completepictureWhen we were decentralised,
@tomboothWe weren’t focusing on ourusers as much as we shouldWhen we were decentralised,
@tomboothRetain ownership in theservice teams
@tomboothIden>fy common paHernsin our infrastructure
@tomboothSupport common paHernswith great tooling
@tomboothAlways ask, how can wehelp each other?
@tomboothGive teams room toexperiment, do what’s bestfor them
@tomboothOutside impressions maHer
@tomboothHelp our owners, investorsand auditors understandour services
@tomboothWork togethernot apart
@tomboothWork together onarchitecture
@tomboothWork together onissues
@tomboothWork together onbugs in produc>on at 3am