Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Building Distributed Systems of People

Building Distributed Systems of People

Past a certain size, all teams become distributed. Whether it's across rooms, floors, or office locations, collaboration becomes harder as organizations grow. In this talk, Juan Pablo will cover the most important lessons he's learned while building distributed engineering teams for fast-growing startups, which you can apply today to improve the effectiveness of your teams, whether they're in the same city or not. 

Juan Pablo Buriticá

April 09, 2019
Tweet

More Decks by Juan Pablo Buriticá

Other Decks in Technology

Transcript

  1. building distributed
    systems of people
    juan pablo buriticá

    View Slide

  2. View Slide

  3. all teams past a
    certain size become
    distributed

    View Slide

  4. why should you
    consider distributed
    teams?

    View Slide

  5. distributed teams are
    not better, they're
    different

    View Slide

  6. access to talent

    View Slide

  7. scalability

    View Slide

  8. representation

    View Slide

  9. cost

    View Slide

  10. how do you build and
    manage distributed
    teams?

    View Slide

  11. decentralized or
    hybrid?

    View Slide

  12. trust is not optional in
    distributed teams

    View Slide

  13. communication is
    fundamental

    View Slide

  14. explicit channels
    enable consistency
    and replication

    View Slide

  15. synchronous comms
    are best suited for
    collaboration and
    coordination

    View Slide

  16. asynchronous comms
    protect focus and
    enable eventual
    consistency

    View Slide

  17. encourage
    acknowledgement of
    communications

    View Slide

  18. whenever possible,
    keep comms
    accessible

    View Slide

  19. fault tolerance

    View Slide

  20. people don't read

    View Slide

  21. tools are your
    infrastructure

    View Slide

  22. invest in A/V software
    & equipment

    View Slide

  23. you'll need a chat, a
    forum, a wiki, a collab
    word processor and a
    project board

    View Slide

  24. you can use tools as
    interfaces within or
    between teams

    View Slide

  25. effective management
    routes, balances
    loads, and monitors
    your system

    View Slide

  26. standard practices
    make your system
    observable

    View Slide

  27. focus on the outcome
    of the practices, not
    the implementation

    View Slide

  28. culture is how you
    scale your behaviors

    View Slide

  29. in person time helps
    build strong
    relationships

    View Slide

  30. talent is equally
    distributed, opportunity
    is not
    Leila Janah

    View Slide

  31. thank you


    @buritica
    @theRemoteShow

    View Slide