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

Remote-first? (MiXiT 2017)

Remote-first? (MiXiT 2017)

En entreprise, le télétravail est de plus en plus répandu, mais souvent limité ou difficile. En co-créant TailorDev, nous avons fait du travail à distance (remote work) le mode de travail par défaut. Entre exemples, astuces et retours d'expérience, je vous présenterai comment et pourquoi j'ai construit une entreprise "remote-first".

Online slides: http://slides.williamdurand.fr/remote-first/
Sources: https://github.com/willdurand-slides/remote-first


William Durand

April 21, 2017


  1. Remote-First? William Durand – MiXiT 2017

  2. Remote (Friendly | First | Only)

  3. Remote Friendly • Remote work is "allowed" (typically time boxed)

    • No access to all resources • Meetings Just because you happen to use chat rooms doesn’t mean you’ve suddenly become a glorious haven for remote workers, dammit. Zach Holman (ex-GitHub) in 2015 “
  4. Remote First • Everything is done to make it work

    • It is a mindset, not a place • Great tools and processes Working remote is the default. It means making sure your remote employees are as much a part of the team as those in the office. Alyssa Mazzina (StackOverflow) in 2017 “ 1
  5. Remote Only Remote First without any physical offices/HQs.

  6. Distributed Teams You have a distributed team when you start

    dealing with different time zones.
  7. Inspirations • Zapier: 20 employees (likely more now) • Litmus:

    70 employees (2016) • Buffer: 80 employees (2016) • GitLab: 140 employees (2017) • Automattic: 548 employees in 53 countries speaking 76 different languages (2017) And many others on ! remotebase.io
  8. • French company with 2 employees • France / Germany

    • Remote First (office in Clermont-Fd) • Not a product-based company
  9. A Typical Day

  10. Flexible Work Place I have a desk in a coworking

    space, but I usually work from a coffee place on Friday mornings. This morning, I have to wait the plumber and a package from Amazon. I'll join the office from home.
  11. Going to the Office • Open Slack • Say write

    Hello • Read iDoneThis digest • Indicate macro schedule • Reply to issues / Slack • Prioritize daily tasks • Set goals for the day
  12. Getting Things Done • GitHub / GitLab • Slack for

    follow-ups / questions • Automated deployments via Slack or CD • Shared KeePassX for secrets • to collaborate with designers ​ • for time-tracking • A lot of Gifs and screenshots 1 2 Zeplin Watson
  13. Quick Calls My customer pings me on Slack and asks

    for help. We agree on a quick Appear.in to resolve the problem. • Short summary in #project • Issues in GitHub / GitLab
  14. Pair-Programming, you said? • with screen sharing • (shared SSH

    sessions) Appear.in Teleconsole
  15. Accounting / Admin? • Wave Accounting with notifications in #business

    (via Zapier) • ownCloud for storing documents • Emails with our accountant • for eSigning HelloSign
  16. Leaving the Office • Write "Bye" in Slack • Log

    what has been done • Disconnect (running, shopping, reading, ...)
  17. How to start?

  18. Top-down Approach When a CEO uses their lunch break to

    hit the gym, others feel empowered to do the same. And when a manager spends their entire vacation answering emails, it’s harder for others to disconnect in their own downtime. Paul Farnell (Litmus) in 2016 “
  19. Trust, trust, trust • Hire people you can trust •

    Trust people you hired If I can’t see what my team is doing, then how do I know they’re not sitting on Twitter all day? <Insert someone you know here> “
  20. Communicate, communicate, communicate • A chat is required (but not

    enough) • Invest in tools and care about processes • Embrace asynchronous communication
  21. Don't Forget • Water cooler is essential (#random) • Write

    great documentation (handbook) • Team building / company retreats ✈
  22. Pros • Access to more and better talent, faster •

    Happy team, great lifestyle, more productive • Distributed teams can handle disasters 24/7 • Usually leads to more transparency
  23. Cons • Company's culture • Remote work is not for

    everyone • Impossible to transition to an office Culture is about more than ping-pong tables. [...] As a remote team you don't delude yourself thinking that culture will magically happen. Wade Foster (Zapier) “
  24. Thank You. Questions? twitter.com/couac github.com/willdurand tailordev.fr

  25. Links 1/2 • • • • • • • •

    https://tailordev.fr/blog/2016/03/24/on-remote-work/ https://thinkgrowth.org/the-difference-between-remote-and-remote-first- 7dd38458855f https://speakerdeck.com/holman/how-github-works https://medium.com/@fox/building-remote-first-teams-a98bf8581db https://open.buffer.com/remote-work-bufferchat-recap/ https://www.helpscout.net/blog/remote-work-resources/ https://zapier.com/learn/remote-work/ https://www.groovehq.com/blog/arguments-against-remote-work
  26. Links 2/2 • • • • • • • •

    https://www.helpscout.net/blog/remote-work-resources/ https://open.buffer.com/remote-work-bufferchat-recap/ https://www.helpscout.net/blog/virtual-teams/ https://blog.travis-ci.com/2014-02-03-how-we-manage-work-in-a-remote-team/ https://weworkremotely.com/ https://zapier.com/learn/remote-work/ https://www.helpscout.net/blog/remote-work-resources/ https://about.gitlab.com/2015/04/08/the-remote-manifesto/