3 ms·
I've managed multiple remote, distributed, asynchronous teams over my career. When remote teams work well, it's a great experience for everyone. However, I'm m
by PragmaticPulp 7y ago
I've managed multiple remote, distributed, asynchronous teams over my career. When remote teams work well, it's a great experience for everyone.
However, I'm more convinced than ever that these pop-culture articles and thought pieces about remote work are counterproductive for remote workers. Most of the remote work thought pieces that make it to the HN front page are very one-sided; They make remote work sound like a panacea, or a way to boost productivity and happiness with zero downsides. This creates very unrealistic expectations of remote work for job seekers, especially the more junior remote devs that I've worked with in recent years. When it comes to remote work, we want to believe that it's the golden ticket to solving all of the problems of the modern workplace.
In my experience managing remote, on-site, and mixed teams: It's much more difficult to make remote teams work well. Some key things to watch out for with remote employees:
- Communication is everyone's job. Async, text-only communication can be more efficient when done right, but it's much more difficult to foster friendly, accurate, and rapid shared understanding over Slack or e-mail than in a well-run face to face meeting. Successful remote work depends on everyone making an effort to seek out information they need, proactively share understanding via accessible documentation, and develop healthy relationships with their peers and managers.
- Remote employees are not contractors. A common misconception is that remote work equals total freedom about when, where, and how you do your job. Pick your own hours, vacation without taking PTO as long as you respond to e-mails once a day, batch your e-mails to once a day or less, and work on your own terms. This can work in certain situations if everyone agrees to it, but it's not a given. If you're a remote employee, the only guarantee is that your working location is not at the office. Having the team working together during specific core hours is hugely valuable if any collaboration is required. It's not efficient to have two people ping-ponging e-mails back and forth with one response per side per day when they could hash things out with a 5-minute chat during overlapping business hours.
- Some people can't handle remote work. It just doesn't work for everyone. My biggest surprise as a remote manager was how many people's productivity dropped off a cliff after they went remote, yet they were convinced they were being more productive than ever. Some of these employees can be trained to be productive remotely with intense hands-on management, but it's a lot of work. I give new remote employees very explicit instructions about expectations for process, check-ins, and team discipline when we start. Continually update these remote onboarding documents as you learn how your remote team works best.
- Remote job listings attract a lot of bad apples. Remote jobs are synonymous with slacking off in some circles. Watch out for digital nomads who want to collect a paycheck while they travel the world. Avoid startup founders who think they can put in a couple hours of remote work and collect a paycheck and benefits while they focus on building their startup on someone else's dime. Watch out for remote applicants who try to work two jobs at once, doing the bare minimum for whichever of the two companies is paying the least attention to their work. When hiring remote at scale, you'll run into more of these bad actor applicants and employees than you might expect.
- Meetings are still helpful in remote teams. There's another common misconception that remote work == no meetings. Some conversations are still most efficiently handled as an N-way video call for 15-30 minutes, rather than a never-ending Slack conversation where participants are half-distracted as they alt-tab between Slack and their work.
- perishabledave 7y agoAs an EM, these points are quite helpful. Regarding your fourth point, how do you filter out or deal with bad apples?
- PragmaticPulp 7y agoAt the hiring phase: Check their LinkedIn and public social media closely. If they have a recent startup or freelancing business listed on LinkedIn, ask them for details about it and how they ended it. For freelancers, I directly ask if they plan to continue freelancing and how they plan to separate the work. As with all hiring, references are key. There's an art to getting an honest reference out of remote employee referrals, though. Don't neglect to follow up on reference checks. Be polite and professional, but don't hesitate to ask hard questions or ask for more appropriate references if they try to give you softball answers. Also have your hiring department follow up with the previous employer to confirm start and end dates. It's tempting for remote workers to stay on with their old employer for a few extra months, double-dipping both paychecks while they can. Ask people why they want a remote position. There are many valid reasons to work remote, but having other obligations during the day is not one of them. For example, if someone wants a remote job so they can stay home and watch their toddler during the workday to save on daycare costs (actual answer from someone I interviewed) then they aren't going to be very productive. Make sure they can allocate a proper amount of time for focused work. After hiring: Proper performance management is key. The important thing here is to treat on-site and remote employees the same with regards to performance management. Technically, there's no reason an employee down the hall couldn't also be sandbagging their performance while they work on a side hustle for 75% of the work week. The biggest pitfall with remote employee performance management is the idea that people have a finite amount of work that can be finished early. Specifically, it's difficult when people get attached to the idea that the number of hours worked shouldn't matter as long as they get their work done. The flaw in this argument is that if your employees are running out of work before the end of the work week, you're not managing your backlog and roadmap effectively, or you're grossly overstaffed. Set the expectation that if someone finishes their sprint work by day 7 of a 10 day sprint, they need to spend those last 3 days taking on additional tickets or helping coworkers. Watch out for people padding estimates, sandbagging, and playing other games to minimize their hours worked. Your job as an engineering manager is to make sure they're not worked too hard, but also ensure they're not sandbagging. Again, this isn't unique to remote employees, but in my experience remote employees have far more temptations to sandbag a little bit here and there that most people just can't resist. Don't nag, but let them know you're watching closely. Most of all: You need to build mutual trust with the remote employees. Without watercooler conversations, shared lunch breaks, and other office mingling you need to make an effort to get to know people. I've found that the more you build a healthy personal connection with remote employees, the less likely they are to try to abuse the system. Be wary of anyone who insists on purely transactional communication arrangements with odd working hours that suspiciously never line up with anyone else's working hours. Also be wary of anyone who always has excuses for why they couldn't finish their work each week, but always rushes to be the heroic person saving the day when something goes wrong. The remote work abusers are always trying to make themselves look indispensable at key moments while dragging the team down on average. Don't let heroism overshadow underlying problems with someone's performance.