Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Centralising the right things
Search
Tom Booth
June 09, 2017
Technology
1
1.2k
Centralising the right things
Tom Booth
June 09, 2017
Tweet
Share
More Decks by Tom Booth
See All by Tom Booth
Painting in Clojure
tombooth
0
130
Using data and visualisation to improve government
tombooth
0
260
Other Decks in Technology
See All in Technology
15 years with Rails and DDD (AI Edition)
andrzejkrzywda
0
110
フロントエンド開発者のための「厄払い」
optim
0
190
セキュリティ はじめの一歩
nikinusu
0
1.3k
~Everything as Codeを諦めない~ 後からCDK
mu7889yoon
2
130
Introduction to Sansan for Engineers / エンジニア向け会社紹介
sansan33
PRO
6
66k
Claude Codeベストプラクティスまとめ
minorun365
58
31k
DatabricksホストモデルでAIコーディング環境を構築する
databricksjapan
0
210
IaaS/SaaS管理における SREの実践 - SRE Kaigi 2026
bbqallstars
3
910
コスト削減から「セキュリティと利便性」を担うプラットフォームへ
sansantech
PRO
1
490
メルカリのAI活用を支えるAIセキュリティ
s3h
8
5.7k
Werner Vogelsが14年間 問い続けてきたこと
yusukeshimizu
2
270
Amazon Bedrock AgentCore EvaluationsでAIエージェントを評価してみよう!
yuu551
0
200
Featured
See All Featured
Navigating Team Friction
lara
192
16k
The Cult of Friendly URLs
andyhume
79
6.8k
Dominate Local Search Results - an insider guide to GBP, reviews, and Local SEO
greggifford
PRO
0
52
The B2B funnel & how to create a winning content strategy
katarinadahlin
PRO
0
260
How People are Using Generative and Agentic AI to Supercharge Their Products, Projects, Services and Value Streams Today
helenjbeal
1
110
Highjacked: Video Game Concept Design
rkendrick25
PRO
1
280
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
35
2.4k
Mind Mapping
helmedeiros
PRO
0
67
Designing for humans not robots
tammielis
254
26k
HU Berlin: Industrial-Strength Natural Language Processing with spaCy and Prodigy
inesmontani
PRO
0
170
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
27k
The Cost Of JavaScript in 2023
addyosmani
55
9.5k
Transcript
@tombooth Centralising the right things Tom Booth
@tombooth
@tombooth tl;dr
@tombooth Build a central team to empower and support others
@tombooth Centralised Decentralised Re-centralised
@tombooth Centralised Decentralised Re-centralised
@tombooth
@tombooth We weren’t one business, we were compe>ng func>ons
@tombooth Protec>onism built through compe>>on
@tombooth
@tombooth Every 3 weeks, …
@tombooth
@tombooth Every 3 weeks, we had a wild ride of
forgoHen changes
@tombooth Opera>ons would get the blame for developer problems
@tombooth
@tombooth Why did their change break my code?
@tombooth Centrally provided tools were very poor
@tombooth GeLng features to our users was slow When we
were centralised,
@tombooth Change was complex because of poor design When we
were centralised,
@tombooth Func>onal ownership caused serious fric>on When we were centralised,
@tombooth Centralised Decentralised Re-centralised
@tombooth One team needs to own the whole service
@tombooth
@tombooth You have to embrace change
@tombooth Deploying con>nuously is beHer for users
@tombooth A team should own its own architecture and infrastructure
@tombooth
@tombooth Every team with their own direc>on, liHle shared
@tombooth Solving the same problems, in the same way with
different implementa>ons
@tombooth Opera>ng at larger scale requires deeper knowledge
@tombooth GeLng features to our users was slow When we
were centralised,
@tombooth Change is complex because of poor architecture When we
were centralised,
@tombooth Func>onal ownership caused serious fric>on When we were centralised,
@tombooth The same problems were being solved repeatedly When we
were decentralised,
@tombooth No-one has the complete picture When we were decentralised,
@tombooth We weren’t focusing on our users as much as
we should When we were decentralised,
@tombooth Centralised Decentralised Re-centralised
@tombooth Retain ownership in the service teams
@tombooth Iden>fy common paHerns in our infrastructure
@tombooth Support common paHerns with great tooling
@tombooth Always ask, how can we help each other?
@tombooth Give teams room to experiment, do what’s best for
them
@tombooth Outside impressions maHer
@tombooth
@tombooth Help our owners, investors and auditors understand our services
@tombooth Work together not apart
@tombooth Work together on architecture
@tombooth Work together on issues
@tombooth Work together on bugs in produc>on at 3am
@tombooth GeLng features to our users was slow When we
were centralised,
@tombooth Change is complex because of poor architecture When we
were centralised,
@tombooth Func>onal ownership caused serious fric>on When we were centralised,
@tombooth The same problems were being solved repeatedly When we
were decentralised,
@tombooth No-one has the complete picture When we were decentralised,
@tombooth We weren’t focusing on our users as much as
we should When we were decentralised,
@tombooth Build a central team to empower and support others