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
230
Building and scaling effective distributed teams
Lindsay Holmwood
November 27, 2017
Tweet
Share
More Decks by Lindsay Holmwood
See All by Lindsay Holmwood
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.4k
Levelling up database security by thinking in APIs
auxesis
0
140
How to thwart your devops transformation with counterinsurgency doctrine
auxesis
1
90
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
680
Mirror, mirror, on the wall
auxesis
2
300
Other Decks in Education
See All in Education
日本の教育の未来 を考える テクノロジーは教育をどのように変えるのか
kzkmaeda
1
220
SARA Annual Report 2024-25
sara2023
1
190
Data Management and Analytics Specialisation
signer
PRO
0
1.4k
Interaction - Lecture 10 - Information Visualisation (4019538FNR)
signer
PRO
0
2k
万博非公式マップとFOSS4G
barsaka2
0
630
モンテカルロ法(3) 発展的アルゴリズム / Simulation 04
kaityo256
PRO
7
1.4k
2025年度春学期 統計学 第3回 クロス集計と感度・特異度,データの可視化 (2025. 4. 24)
akiraasano
PRO
0
200
予習動画
takenawa
0
11k
2025.05.10 技術書とVoicyとわたし #RPALT
kaitou
1
240
미국 교환학생 가서 무료 홈스테이 살면서 인턴 취업하기
maryang
0
110
アントレプレナーシップ教育 ~ 自分で自分の幸せを決めるために ~
yoshizaki
0
150
ARアプリを活用した防災まち歩きデータ作成ハンズオン
nro2daisuke
0
130
Featured
See All Featured
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
18
1k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Building Applications with DynamoDB
mza
95
6.5k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.4k
Building a Scalable Design System with Sketch
lauravandoore
462
33k
Build your cross-platform service in a week with App Engine
jlugia
231
18k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
47
9.6k
Bootstrapping a Software Product
garrettdimon
PRO
307
110k
The Cult of Friendly URLs
andyhume
79
6.5k
Java REST API Framework Comparison - PWX 2021
mraible
31
8.7k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
60k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
31
2.4k
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?)