Leading Distributed Teams - Stretch Conference 2020
•
0 likes•662 views
This talk was presented at the Stretch Leadership Conference in Budapest, Hungary on February 14, 2020 In this talk, Kevin Goldsmith discusses four main challenges to leading distributed teams: Conway’s Law, Amdahl’s Law (as applied to organizations), Empathy, and Communication. He gives examples of these problems and solutions from his experience leading distributed teams over the last 25 years. Distributed teams can either be very powerful, finding the best developers wherever they are, or it can be a nightmare of bad video meetings and flame wars. What makes distributed teams especially challenging? How can we address these challenges to make our distributed organizations more effective?
Recommended
Recommended
More Related Content
What's hot
Similar to Leading Distributed Teams - Stretch Conference 2020
Similar to Leading Distributed Teams - Stretch Conference 2020 (20)
More from Kevin Goldsmith
More from Kevin Goldsmith (20)
Recently uploaded
Recently uploaded (20)
Leading Distributed Teams - Stretch Conference 2020
- 1. LEADING DISTRIBUTED TEAMS KEVIN GOLDSMITH, CTO @ ONFIDO
- 3. @KevinGoldsmith YOU ARE ALREADY IN A DISTRIBUTED TEAM
- 10. @KevinGoldsmith WHAT MAKES DISTRIBUTED TEAMS CHALLENGING?
- 22. @KevinGoldsmith ORGANIZATIONS WHICH DESIGN SYSTEMS... ARE CONSTRAINED TO PRODUCE DESIGNS WHICH ARE COPIES OF THE COMMUNICATION STRUCTURES OF THESE ORGANIZATIONS. Melvin Conway CONWAY’S LAW
- 24. @KevinGoldsmith CONWAY’S LAW THE HOMOMORPHIC FORCE “Speaking as a mathematician might, we would say that there is a homomorphism from the linear graph of a system to the linear graph of its design organization.”
- 25. @KevinGoldsmith CONWAY’S LAW By Hagmann P, Cammoun L, Gigandet X, Meuli R, Honey CJ, et al. - File:Medial surface of cerebral cortex - gyri.png, CC BY 2.5, https:// commons.wikimedia.org/w/index.php?curid=8636113
- 27. @KevinGoldsmith ARE WE TRAPPED BY CONWAY’S LAW?
- 30. @KevinGoldsmith IT EASIER TO WORK WITH CONWAY’S LAW THAN TO FIGHT IT
- 32. @KevinGoldsmith FIND COMMUNICATION BOTTLENECKS THAT CONFLICT WITH ARCHITECTURE AND ELIMINATE THEM.
- 33. @KevinGoldsmith DESIGN THE ORGANIZATION TO DESIGN THE ARCHITECTURE.
- 35. @KevinGoldsmith NETFLIX LEARNED FROM THIS [AMAZON] EXAMPLE, AND ENSURED THAT FROM THE BEGINNING IT STRUCTURED ITSELF AROUND SMALL, INDEPENDENT TEAMS, SO THAT THE SERVICES THEY CREATED WOULD ALSO BE INDEPENDENT FROM EACH OTHER. THIS ENSURED THAT THE ARCHITECTURE OF THE SYSTEM WAS OPTIMIZED FOR SPEED OF CHANGE. EFFECTIVELY, NETFLIX DESIGNED THE ORGANIZATIONAL STRUCTURE FOR THE SYSTEM ARCHITECTURE IT WANTED. Sam Newman, Building Microservices BY MICHAEL J. BENNETT [CC BY-SA 3.0 (HTTPS:// CREATIVECOMMONS.ORG/LICENSES/BY-SA/3.0)], FROM WIKIMEDIA COMMONS
- 37. THE PERFORMANCE OF THE WHOLE IS ONLY AS FAST AS IT’S SLOWEST PART AMDAHL’S LAW (PARAPHRASED)
- 38. @KevinGoldsmith AMDAHL’S LAW SERVER CORE LIBRARY IOS / MAC ANDROID WEB INFRASTRUCTURE
- 41. @KevinGoldsmith SPEED UP THE SLOWEST ELEMENT?
- 43. @KevinGoldsmith RETHINK THE WHOLE SYSTEM!
- 44. @KevinGoldsmith WHERE ARE THE BOTTLENECKS?
- 50. @KevinGoldsmith TEAMS DECIDE BEST HOW TO DELIVER AGAINST THAT STRATEGY
- 51. @KevinGoldsmith USE MUTUALLY AGREED UPON BUSINESS METRICS TO TRACK ACHIEVEMENT
- 55. @KevinGoldsmith IS NOT THE SAME AS
- 56. @KevinGoldsmith EMPATHY Image by Andreas Fischler
- 59. TAKE NOTES ON PAPER SOLUTIONS
- 64. @KevinGoldsmith WELL THAT IS FINE FOR YOU PEOPLE AT CORPORATE… Someone who has forgotten that the people they work with are actual humans EMPATHY WARNING SIGNS
- 83. DON’T GET TOO OBSESSED WITH TOOLS SOLUTIONS
- 85. ESTABLISH COMMON WORKING TIMES SOLUTIONS
- 86. @KevinGoldsmith COMMUNICATION GMT +1 +2 +3 +4 +5 +6 +7 +8 +9 +10 +11 +12-1-2-3-4-5-6-7 -8-9-10-11-12
- 88. @KevinGoldsmith THE MODERN WORKFORCE IS DISTRIBUTED
- 90. @KevinGoldsmith THE CHALLENGES CAN BE OVERCOME