Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Centralising the right things
Search
Sponsored
·
Ship Features Fearlessly
Turn features on and off without deploys. Used by thousands of Ruby developers.
→
Tom Booth
June 09, 2017
Technology
1.3k
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Centralising the right things
Tom Booth
June 09, 2017
More Decks by Tom Booth
See All by Tom Booth
Painting in Clojure
tombooth
0
140
Using data and visualisation to improve government
tombooth
0
310
Other Decks in Technology
See All in Technology
Making AI Agents Safe and Fast- Jev, Obsidian, and the Meta-Harness
x5gtrn
PRO
0
100
事業課題から技術的負債に向き合う
sansantech
PRO
2
2.2k
安心して変更できるWebフロントエンドの作り方
pirosikick
5
2.9k
銀行勘定系システムにおける開発プロセス刷新×AIによる環境モダナイゼーション / Development Process Transformation and AI-Driven Environment Modernization
muit
1
2.5k
Claude in Chrome 入門 / Introduction to Claude in Chrome
cielo1985
0
880
AIによるクリエイティブ生成を行う上での試行錯誤
plaidtech
PRO
0
170
AIは推し活である。
kurazuuuuuu
1
930
`t*(42&t>>10)`だけで音楽が鳴る、Swiftで実装するBytebeat / iOSDC Japan 2026
yutailang0119
0
120
品質と信頼性を地続きにする
grimoh
2
880
Issue 駆動でスペシャリストの意図を届ける、AI 実装のアクセシビリティ向上
thkt
0
130
Claude Codeを「使うほど育つ」AI秘書にするノウハウ
minorun365
PRO
33
30k
CLIライブラリ開発を支える技術
htnabe
0
140
Featured
See All Featured
Mind Mapping
helmedeiros
1
370
Between Models and Reality
mayunak
4
460
Accessibility Awareness
sabderemane
1
210
Being A Developer After 40
akosma
91
590k
Sam Torres - BigQuery for SEOs
techseoconnect
PRO
0
540
Navigating the Design Leadership Dip - Product Design Week Design Leaders+ Conference 2024
apolaine
2
430
Public Speaking Without Barfing On Your Shoes - THAT 2023
reverentgeek
1
570
SEO in 2025: How to Prepare for the Future of Search
ipullrank
3
3.8k
Abbi's Birthday
coloredviolet
4
10k
New Earth Scene 8
popppiees
4
2.6k
The Spectacular Lies of Maps
axbom
PRO
1
1k
A designer walks into a library…
pauljervisheath
211
25k
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