Manage Learn to apply best practices and optimize your operations.

How to optimize the performance of remote teams: Three variations

Remote teams may not be the ideal, but they are a fact of the modern workplace. Here are three types of remote teams and tips on how to help them work better.

Editor's note: In part one of this three-part series on how to manage and optimize distributed teams, management...

expert Joseph Flahiff laid out eight tips for facilitating collaboration among on-site and remote teams. Here, he describes the problems associated with three of six types of remote teams and offers pointers on how to fix them.

Not all remote work is created equal. There is a spectrum of remote work. Some of it can be really good, some can really stink.

#1.  Big team, one solo

This is the worst of all possible options for collaboration: A large group of people are collocated and able to collaborate face to face. Only one person is remote.

The good thing about this option is that with only one person remote, there won't be contention on the phone or video conference for speaking time. 

However, the one person who is remote will always feel like an outsider. Collaborative teams work best when people feel safe socially and psychologically and that psychosocial safety net is difficult to achieve when only one person is remote. If you have ever been on the other side of the phone, you know what I am talking about. It is hard to understand what is happening in the room. People tend to talk over one another. Many of the nonverbal cues -- which can account for between 55% and 93% of communications -- are missed by the remote person. Video teleconferencing technology helps, but the solo person is always going to have a hard time jumping in and participating in the dynamics of the live conversation happening in the room. 

it teams, employees, remote workers, distributed teams, big team, one solo

Optimizations

  1. To make the most of this situation, have someone in the room be the phone person's "buddy." The job of the buddy is to ALWAYS be thinking about that person on the phone.  
  2. Use multiple forms of communication. Have the remote person on text message or an instant message link. That way, if you have a technical problem setting up the call, you will have an alternative communication channel already connected. Messaging can also help the remote person break into conversations, because the on-site buddy can then advocate for him or her.

#2.  One group and lots of solo

In this option, you have a small group of people who are collocated and the majority of people in individual remote sites. This option is a little better just by dint of the numbers -- the more remote people, the more influence they have in the group. If more than half your team comprises solo remote people, the local team is more likely to pay attention to them because they are the majority. Still it will be difficult to communicate, especially with lots of people on telecommunications devices. Live, in-person conversations are messier than you might think. Even when we try to be polite, we end up talking over each other and interrupting each other with nonverbal cues. Technology solutions today cannot simulate this perfectly. Although these tools are getting better every day, there is still a slight delay when switching from one speaker to another, even in full duplex systems.

Optimizations

  1. Set protocols for speaking in turn. Always ask if anyone has anything to add. Maybe speak in some predetermined order, alphabetical or by location. 
  2. Voting protocols. Use collaboration tools or visual cues for voting. The key is to avoid the cognitive bias of anchoring. This is hard to do over a telecom connection.
  3. Pair remote people with other remote people, local people with local people. By pairing people with like communications limitations you will optimize their skills. If you pair remote workers with collocated workers, the collocated workers miss out on the benefits of their collocation.

#3.  Large team and a small team

This combination is actually quite workable, with a few caveats. Ideally, each team can function as a fully autonomous unit. That is, if one team takes on a piece of work, it should have all the skills necessary to complete the work. It is NOT advisable to have one team be a test team and another be the creating team, because the handoffs will eat up a lot of time. Additionally, you may end up creating an "us and them" mentality. While separate but equally able teams sound good in theory, there is a risk of creating divergent, even adversarial, team cultures. Additionally, it is easy for each team to tell themselves stories about the other team. For example, "Oh, they are not as good as we are at x" or "That team thinks they are awesome, but they really aren't." Rumors live on lack of communication. The more your large and small teams communicate with each other, the less likely those rumors will fly.

Optimizations

  1. Leaders should visit whatever site they are not at as often as they can. Making this a regular, predictable schedule is also a good idea so that people grow to expect your presence on predictable days.
  2. The trick with this team is to break the work in such a way that there are limited interdependencies between the remote sites. By the very nature of being a team the work will be somewhat interdependent, but strive for as little as possible.
it teams, employees, remote workers, distributed teams, big team, one solo

Go to part three of this series on managing and optimizing remote teams to read about three more team configurations: all-distributed teams; equivalent teams; and collocated teams.

About the author:
Joseph Flahiff is an internationally recognized leadership and organizational agility expert at 
Whitewater Projects Inc. He has worked with Fortune 50 and Fortune 500 companies, government agencies, startups and publicly traded firms, where he has been recognized as an experienced, pragmatic and innovative adviser. He is the author of Being Agile in a Waterfall World: A practical guide for complex organizations. Learn more at www.whitewaterprojects.com.

Next Steps

Previous management tips from Joseph Flahiff:

Three attributes of a successful business reorganization

Destroy your way to organizational agility

Fire your managers: Practice supportive leadership

This was last published in May 2016

Dig Deeper on IT staff development and retention

PRO+

Content

Find more PRO+ content and other member only offers, here.

Join the conversation

3 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

What is the worst remote team configuration you have experienced?
Cancel
Before even reading this article, I was going to say #1. Or something really similar to it. We are a big co-located team with a few remote workers. It's really evident that the remote workers have to put in a lot more effort to stay engaged, and they really lack the context and understanding of our work that the rest of the team is exposed to daily. 
Cancel

team at AT&T doing end-to-end testing 20 hours a day of 66 interlocking systems, what made it worst was not the 10-hour shifts but that we weren't always on the same 10-hour shift.

Cancel

-ADS BY GOOGLE

SearchCompliance

SearchHealthIT

SearchCloudComputing

SearchMobileComputing

SearchDataCenter

Close