At Distributed we manage distributed teams that deliver work in hard-to-hire-for and expensive areas of digital marketing and tech on behalf of our clients. From content creation, through API design and analytics integrations and all the way up to the development of Artificial Intelligence.
We deliver this work at a higher quality, in less time, and at a lower cost than centralised agencies.
It’s not been easy building Distributed, but it’s working incredibly well, and we’re now in a position to scale and add a few more clients to our roster.
I’m not going to bore you with the story of how we built Distributed over the past 5 years, if you want to read more about us please check out this post that I wrote a little while back, I am however going to detail a few of the lessons we’ve learned about building and running distributed teams and hopefully offer some valuable insights that may help you reap the benefits of building your own distributed team.
People first, every time .
I can’t stress this highly enough, when you run distributed teams, you’re rarely in the same room together, now, most organisations would see this as a problem, but fortunately for us, and our clients, most organisations are wrong, and here’s why.
Companies believe that by having their staff in the same room or building that they are taking care of their team and managing them them effectively, they believe that managers are more effective, that they are promoting collaboration, team building and skill sharing, and they believe that their teams are happy, well, it’s a fallacy, and it’s an outmoded mind-set.
Distributed team members are more productive
Open-plan offices make workers more unfriendly and less productive
Offices are not designed for modern work
Distributed teams are happier
Distributed teams are more diverse
Offices are bad for your health
Working with distributed teams not only means that we have a happier, healthier company, but it actually helps us be a ‘people first’, company, because it requires us to really care about our team members, to check in on them regularly, to make time specifically to talk about them, their projects and how we can be doing things better, most of all, it makes us value them as individual contributors, we don’t have the luxury of believing that a 3 minute chat while making a coffee constitutes catching up with a team member.
With distributed teams it’s important that your tech stack enables productivity, we’ve found the following areas to be critical areas for our teams: