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
Building and scaling effective distributed teams
Search
Lindsay Holmwood
November 27, 2017
Education
4
240
Building and scaling effective distributed teams
Lindsay Holmwood
November 27, 2017
Tweet
Share
More Decks by Lindsay Holmwood
See All by Lindsay Holmwood
Protecting sensitive data in DynamoDB with searchable encryption
auxesis
0
13
Your API ain't as secure as you think
auxesis
0
140
Footguns and factorisation: how to make users of your cryptographic library successful
auxesis
0
1.5k
Levelling up database security by thinking in APIs
auxesis
0
140
How to thwart your devops transformation with counterinsurgency doctrine
auxesis
1
91
Microservices are an antipattern
auxesis
0
220
Mirrors, networks, and boundaries
auxesis
0
120
Managing remotely, while remotely managing
auxesis
13
4.5k
Testing Conway’s Law in open source communities
auxesis
6
690
Other Decks in Education
See All in Education
生成AI活用セミナー/GAI-workshop
gnutar
0
110
Pydantic(AI)とJSONの詳細解説
mickey_kubo
0
190
みんなのコードD&I推進レポート2025 テクノロジー分野のジェンダーギャップとその取り組みについて
codeforeveryone
0
210
データで見る赤ちゃんの成長
syuchimu
0
270
JPCERTから始まる草の根活動~セキュリティ文化醸成のためのアクション~
masakiokuda
0
220
教える側は、初学者に谷越えまで伴走すべき(ダニング・クルーガー効果からの考察)
hysmrk
3
140
AI for Learning
fonylew
0
180
Alumnote inc. Company Deck
yukinumata
0
2k
自己紹介 / who-am-i
yasulab
PRO
3
5.4k
20250910_エンジニアの成長は自覚するところから_サポーターズ勉強会
ippei0923
0
230
Open Source Summit Japan 2025のボランティアをしませんか
kujiraitakahiro
0
850
2025年度春学期 統計学 第15回 分布についての仮説を検証する ー 仮説検定(2) (2025. 7. 17)
akiraasano
PRO
0
110
Featured
See All Featured
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
15
1.7k
What's in a price? How to price your products and services
michaelherold
246
12k
Practical Orchestrator
shlominoach
190
11k
Building Flexible Design Systems
yeseniaperezcruz
329
39k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
188
55k
Building a Scalable Design System with Sketch
lauravandoore
462
33k
How to Ace a Technical Interview
jacobian
279
23k
YesSQL, Process and Tooling at Scale
rocio
173
14k
A Modern Web Designer's Workflow
chriscoyier
696
190k
Principles of Awesome APIs and How to Build Them.
keavy
126
17k
A designer walks into a library…
pauljervisheath
207
24k
Context Engineering - Making Every Token Count
addyosmani
3
54
Transcript
Building and scaling effective distributed teams Lindsay Holmwood
About me Worked in and lead distributed software engineering teams
for 7 years
About me Lead teams with follow-the-sun coverage
About me Currently at Envato leading distributed team of 15
The journey 0. Fundamentals 1. Starting out 2. Growing the
team 3. Scaling to the whole org
Inclusion Practices Technology Sponsorship
No management buy in? Don’t even bother.
Starting out
Inclusion Practices Technology Sponsorship
Regular face to face catchups. Ideal: once a quarter
Regular face to face catchups. Likely: once a year
Establish rituals
Multiple internet connections Dongle with lots of data
Multiple internet connections Don’t skimp on quality (fast upload a
must)
Multiple internet connections Move to areas with NBN
Multiple internet connections Have backup equipment
Instant messaging Non-negotiable, primary comms method
Instant messaging Your lifeline to your team.
Instant messaging Scheduled do not disturb time
Instant messaging Announce start/stop
Ceremonies: Daily standup Rotate the facilitation responsibility
Ceremonies: Retrospectives Discuss and refactor practices
Leadership participation Show endorsement. Build empathy.
Growing the team
Inclusion Practices Technology Sponsorship
The basics Even more important!
The basics Bring in coaches to observe and facilitate.
Hack: Greet everyone to check
Hack: Ask questions in the negative “Does anyone disagree?” not
“Do we all agree?”
Team design: Time zone coverage How many time zones? How
much time zone overlap?
Team design: Time zone coverage Add people in new time
zones in pairs.
Team design: Time zone coverage Beginning & end of day
standups.
Team design: Time zone coverage Record crucial meetings.
Team design: Antipattern: Forcing everyone to work at exactly the
same time
Team design: Antipattern: Communication in physical spaces that excludes remoters
Team design: Antipattern: Activities that exclude remoters (use of whiteboards)
(in-person icebreakers)
Google Quick Draw
Team design: Defining question How would this decision make me
feel if I was working from home?
Leadership participation Show endorsement. Build empathy.
Scaling to the whole org
Inclusion Practices Technology Sponsorship
What does it take to make distributed teams a first
class citizen in the organisation?
The executive and management working remotely at least 2 days
a week.
Guilds Share lessons learnt with other teams
Feedback loops Keep refactoring your ways of working.
Feedback loops “What got us here won’t get us there."
Thank you! (and questions?)