Apemag

  • #MyStartupStory
  • tech
  • maker
  • Startup Lessons
  • In the South
    • Tennessee
    • Alabama
    • Arkansas
    • Florida
    • Georgia
    • Kentucky
    • Louisiana
    • Mississippi
    • North Carolina
    • South Carolina
  • Startup Support
    • Accelerators
    • Coding Bootcamps
    • Colleges and Universities
    • Incubators
Columnists, Scott Barstow, Startup Lessons, Talent Management, Technology

Communication Secrets of the Best Distributed Teams

- Scott Barstow -

This post originally appeared on scottbarstow.com.

This is the fifth post in my series on Building Distributed Teams. So far, we’ve covered why you need to be building a distributed team,  what makes an ideal distributed team member, individual vs pods when hiring and team leadership. As a reminder, this series is focused on building a distributed technology product team. While the principles here might apply to building a distributed sales team, it is not the focus.

In this post we’re going to talk about how a highly functioning distributed team communicates and where a lot of companies get tripped up with this model.

There are three things that the best distributed teams do to facilitate great communication:

  • Company leadership ensures that everything that’s important for the team to move fast is written down
  • Everyone on the team is online and available for a set period of time each day
  • All important communication is handled in publicly available channels

Writing It Down

One of the main reasons you build a distributed team is so that you can be as or more productive than if everyone is sitting in the same office. However, you’ll be sorely disappointed in how quickly the team moves if you don’t do your job as the leader of the team to ensure that everyone has what they need when they need it.

One of the best examples I’ve seen of publishing everything that’s required for a distributed team to function in recent times is Gitlab’s Employee Handbook. You should stop what you’re doing and go read this right now. Everything a team member needs to know about working at Gitlab is right there in easy to read bullets.

If every time a new team member has a question they have to wait for someone else on the team to be available, things will grind to a halt.

This is a two-way street, of course. Every team member has to care enough to write the specifics of their particular area down as they work on them or the system breaks. If it’s not written down, it’s not done.

Schedule Overlap

Regardless of how widely distributed your team is in terms of timezones, you must ensure that everyone on the team is available for a set period of time each day. For example, you might mandate that everyone is online from 8-10 a.m. EST. This window is used to cover important communication that everyone in the company needs to know, and to address key questions that might be slowing parts of the team down.

This also facilitates everyone getting to know each other. You have to be intentional about this or your team will not function.

You might consider using one day a week during this time to share wider information about how the company is doing, key milestones upcoming, or new customers that were onboarded since the last time the team met.

Communicate in Public Channels

Before Slack and HipChat came along, I ran all of my teams using Hangouts or other messaging systems. Nearly all communication in a distributed team happens via written channels, not voice or video. Why? In any size team, someone will be missing on any given day. If you use voice or video channels, that person may miss something important. If you use written channels, if someone was missing they simply catch up the next time they’re online.

Also, if you’re having face to face meetings in your main office, you must remember that a good number of your team are not sitting with you. If you make key decisions in those meetings, you have to be intentional about communicating the what AND the why to those who were not sitting with you.

A great practice is to record all face to face meetings in your office and share the audio in your public comm channels. Others can listen to the audio on their own time and ask questions as needed.

Of all the the things that make distributed teams fail, poor communication structures are probably #1 on the list. You must over-communicate at all times, and ensure that the rest of the team understands that every side conversation that is not shared weakens the team.

Writing everything down, ensuring there is sufficient schedule overlap, and forcing all communication into asynchronous, public channels as much as possible will go a long way toward ensuring your distributed team functions at their highest possible output.

In our last post, we’ll talk about the most common reasons why this model fails and how you can avoid the pitfalls. See you next time!

Apr 13, 2017Scott Barstow

Why Startups Need to Know the Norms When It Comes to Raising CapitalGet to Know Blake Hogan, the Dot Connector behind Bunker Labs Nashville
3 years ago Columnists, Scott Barstow, Startup Lessons, Talent Management, Technologydistributed team, employee communication, Scott Barstow71
Scott Barstow

Scott Barstow writes a blog series focused on helping untechnical founders successfully start and launch technology companies without lighting their money on fire. He is a venture partner at Sovereign’s Capital and an adviser to multiple startups in Raleigh-Durham and elsewhere. Scott is the former CTO of Bandwidth and current CEO of Rocket Hangar, an incubator of new technology products. You can find out everything you need to know about Scott and subscribe to his newsletter at http://scottbarstow.com. You can reach out to Scott on Twitter at @scottbarstow.

Website Twitter

Leave a Reply Cancel reply

Share It!
0
GooglePlus
0
Facebook
0
Twitter
0
Linkedin
Posts
Recent Comments
  • East Tennessee Startups Have Chance to Win $15,000 on 2017 Startup Day « Startup Southerner on #MyStartupStory: Start a Beer Fund With BrewFund
  • East Tennessee Startups Have Chance to Win $15,000 on 2017 Startup Day « Startup Southerner on Ed Pershing, CEO of PYA, Reflects on Entrepreneurial Journey
  • Salemtown Board Co.: Scaling a Social Enterprise « Startup Southerner on Entrepreneurial Thinking for Nonprofits
  • Salemtown Board Co.: Scaling a Social Enterprise « Startup Southerner on The EntrepreLingo Series: S Is for Scalability
  • Domonique Townsend on The Unbalanced Reality of Work-Life Balance for Working Mothers
Be up-to-date!
  You Might Also Like  
Columnists, Scott Barstow, Startup Lessons, Technology

Scott Barstow on 2 Questions to Ask Before Building More Software

Scott Barstow explains why the tech founder sometimes has the wrong motive when it comes to product development.

Columnists, Company culture, Scott Barstow, Startup Lessons, Talent Management

Five Lessons I Learned at My First Startup

Columnist Scott Barstow still uses the lessons he learned from his first startup experience.

Startup Lessons, Talent Management

Talent Management Tips for a Merger or Acquisition

We're filing this one under good problems to have. Frank Williamson walks us through talent management during M&A.

Columnists, Productivity, Scott Barstow, Startup Lessons, Talent Management, Technology

3 Reasons to Build a Distributed Team for Your Startup

Scott Barstow explains why distributed technology product teams are great for startups.

Columnists, Company culture, Scott Barstow, Startup Lessons, Talent Management

Building a Distributed Team: Who Makes the Ideal Team Member?

Scott Barstow identifies the key characteristics of the most effective remote workers.

Columnists, Scott Barstow, Startup Lessons, Talent Management

Building Distributed Teams: Individuals vs. Pods

Scott Barstow describes the pros and cons of hiring individuals vs. groups of people for your distributed teams.

Columnists, Scott Barstow, Startup Lessons, Talent Management

Distributed Team Success Starts With the Leader

Want your distributed team to be successful? Scott Barstow says that starts with its leader.

Columnists, Company culture, Scott Barstow, Startup Lessons, Talent Management, Technology

Scott Barstow on What Causes Distributed Teams to Fail

Don't miss the final installment in Scott Barstow's insightful six-part series on distributed teams.

  • About
  • Contact Us
  • Advertise
Most Viewed
2016 FOUNDING SPONSOR
your-image-description
2016 FOUNDING SPONSOR
2017 © Startup Southerner, LLC