Tag Archives: collaboration

A Sneak Peek at Results of The Grove’s Recent Survey: Five Minutes on Working Virtually

If you haven’t had a chance to take the five-minute survey yet and would like to, you can find it here.

The Grove recently launched a short survey on virtual work and remote meetings. Among other things, we asked hundreds of people who do virtual work about their biggest pain point: the one thing they wish would go away and just stop being a problem about working remotely.

The responses fall broadly into three categories. Respondents identified pain points related to technology, to people, and to the setting where the work is done. It may surprise you to learn that technology is not the category with the most pain points. The largest set of different pain points is related to people. In fact, the number of pain points having to do with people is almost twice as large as that in either of the other two categories. Note that this doesn’t say anything about how often a given point was cited; I’m not dealing with that here, just looking at unique responses. The image below is a compilation of the responses, sorted unscientifically by yours truly. (Click to see it bigger.)

List of pain points in remote work
Compilation of responses to the question: What is the most painful part of working remotely?

The pain points related to people have to do with how people feel in remote meetings, things people do or fail to do that make the work harder, the difficulty of making or maintaining interpersonal connections at a distance, and basic knowledge and skills around working remotely. I know I have struggled with most, if not all, of these issues in the past ten years of working virtually. Many of these pain points can be addressed through training (of facilitators and participants), making explicit agreements about how to work together and behave as a remote team, and extra time and effort involved in preparation. Sometimes, though, it seems as soon as a team gets one issue taken care of, another, hydralike, rears its annoying head.

Regarding technology, the agony is divided between tool-related issues and those dealing with connection (or lack thereof) when trying to communicate. One that we did not see, but that I expected, is overwhelm about the number of tools available. Does anyone else find it hard to keep up? I sometimes feel that if I just keep looking and keep testing, I will find the perfect tool for every task related to remote collaboration. I’m not saying I’ll find one tool that does everything. Rather, I’d love to find a set of tools that collectively do everything. Easily. Okay, maybe now I’m dreaming.

The setting we’re in when we do remote work accounts for the remainder of the pain. Real life issues, the consequences of not being physically in the same room, and the effects of having to be sitting at a computer are the main groups here. As with the other categories, some of the complaints can be addressed through group norms, different tools, or extra effort, but again I can empathize and have experienced all of these myself. What about you? Do you have a favorite, and how did you stop the pain?

If you’d like to get your voice in the mix, please hop on over and take the five-minute survey. It will remain open through June 30, 2015.

Role Mapping: Do you really know your teammates’ roles?

Do you know, I mean really know, what your teammates do? Do you understand their roles to the point where you could fill in for them for a day? Even if you don’t know their roles to that degree, do you know how they produce information they give to you, and what they do with information you give to them?

From left to right: Healer, DPS (with pet), Tank.

From left to right: Healer, DPS (with pet), Tank.

My family plays World of Warcraft, a popular MMO (massively multiplayer online game) created by Blizzard Entertainment. In this game, players sometimes form parties to tackle challenges that one player can’t handle alone. A five-person party usually includes three distinct roles: tank, healer, and damage-dealer (DPS, or damage-per-second). Any one player will have one of these roles at a given time, and his or her talents, abilities, equipment, and armor are tailored to support that one role. (For those unfamiliar with the lingo, the job of the tank is to stand there and get beat on by the big monster, keeping its attention; the healer’s job is to make sure the tank stays alive while this happens, and to heal the DPS players if they should need it; and the three DPS players are there to inflict as much damage on the monster as possible without taking a lot of damage themselves.)

Obviously, each player needs to understand his or her own role in order to be effective. But the really effective players — the ones you always want in your party — are the ones who also have a deep understanding of the roles they are not playing. Here’s why: A tank who deeply understands the healer’s role can time his or her own actions so that big-burst damage is mitigated by a tank ability, allowing the healer to more effectively keep the tank’s health stable by not spending precious resources on sudden massive heals. Healers who understand how the tank works know that if a monster does latch onto them, the best thing to do is run toward the tank, who has the ability to attract the monster’s attention so it forgets all about the healer — rather than running away, which is instinctive but not at all helpful. DPS who understand the other two roles can modify their own behavior to maximize their ability to do their primary role — dealing damage — while not draining the healer’s reserves, which are really needed for the tank, or pulling the monster away from the tank and causing it to run amok among the party. Even a basic level of understanding of other roles is helpful. When you run into tanks who also have a healer class character, or DPS who also have a tank character, the difference really shows. They do their jobs in a way that makes the other roles even more effective at theirs.

The same is true for a working team: the better you understand your teammates’ roles, the more effective your team can be overall. The points where your work overlaps theirs, or provides inputs to theirs, are where your team will feel the effects the most. Mapping out the intersections of your roles will give your team clearer insight into how to work together more effectively. Here’s one way to do that.

Sample role map
A sample map for three roles in a consultancy

Role Mapping

Choose a time when everyone can get together. If your team is distributed, consider supporting the meeting with graphic recording or graphic facilitation to create the maps of team interactions. Set aside at least an hour for the initial conversation.

  1. Identify the places where there are overlaps or shared inputs or outputs. What do you create that is then used by another team member? What do you use that other team members create? Make a list, and ask everyone on the team to make a list too. (This can be done as pre-work.)
  2. Get the team together. Compare your lists and rank the items to decide where to start. Look for items that appear on several lists, and start there for the biggest impact. Alternatively, select the most high-profile activities on the lists as a starting point.
  3. Take a few minutes to map out what happens around each item on the combined list. Give everyone who touches that item a chance to explain what they do and how they do it. What tools do they use? What information do they need to have handy when they start? What format do they prefer to work with? Allow everyone to describe their workflow and preferences without trying to problem-solve at this point. Just listen. It might help to draw a picture of the process as it is described, using a whiteboard or large sheet of paper. Make notes of questions or issues as they come up, but don’t try to solve them yet.
  4. Once everyone has spoken, have a conversation about the questions, issues, and other flags that came up. You might find that something as simple as changing the way information is conveyed or presented might make a big difference to the recipient. And once you understand why someone wants it this way or that way, it’s often easier to modify your own workflow slightly to accommodate them. Use a flip chart to clearly record new agreements or procedures your team wants to try.
  5. Repeat the process for each item on your combined list (this might take more than one meeting). At the end of the meeting, review the flipchart of agreements and make sure everyone understands what he or she has personally agreed to do. Agree on an evaluation period — two to four weeks, perhaps — after which you will all reconvene to talk about whether the changes are helping, identify new issues that have come up, or discuss new ideas.

This activity is particularly valuable for distributed teams where members do not have a way to physically see what their co-workers do. On teams like that, the way that inputs and outputs are created and delivered can make a huge difference in team effectiveness. For example, it’s common for someone to create a document and send it as a PDF, but if the recipient needs to extract information from the PDF to use elsewhere, it can be time consuming. Something as simple as switching to a shared document editor or keeping the shared information in another system might result in a much smoother workflow.

Once you understand more about the work your teammates do and how they do it, you can play your role in way that helps others be even more effective. Even if your goal isn’t to slay a giant monster, you’ll still make better use of everyone’s abilities!

For more on role clarification, you might like these resources: