A friend who owns a manufacturing business recently decided to hire a remote software developer – his first remote employee. He asked if I had some advice for managing remote employees as he knows I’ve done so. In fact, I’ve managed remote team members in some way, shape or form since 1998. While the folks I work (and worked) with have been a mix of folks close to home and scattered around the globe, he’s starting with a remote developer here in the U.S.
Why remote employees?
Hiring a remote employee might seem like the craziest idea ever. Even so, remote work has been growing steadily since the late ’90s for several reasons: People have roots. Their families have jobs, friends, schools & communities they love, outdoor recreation your community can’t compete with (and vice versa), etc.
In the ’60s-’80s, when a company transferred or hired an employee who lived somewhere else, they generally paid movers to pack and move that employee’s possessions. In some cases, they would buy the employee’s old house if it didn’t sell within a reasonable amount of time. Serious investment. Remote work during those decades was difficult, but it still happened. Companies like IBM (“I’ve Been Moved”), Kodak, Xerox and others had field sales / service reps all over the country – and not always based out of a local company-owned office.
Today, such transfers are far less common. Companies lower their standards, extend their search effort, hire remote people or find another solution.
If an ideally trained, experienced candidate with domain-specific knowledge for your opening lives somewhere else, and cannot (or doesn’t want to) move to your town, do you:
- Do without and settle for someone who isn’t ideal.
- Keep looking and wait until the right (or close enough) local appears.
- Hire no one and leave the opening unfilled.
- Hire a local and invest in the proper training.
- Ask a candidate to move to your town (think about how you might feel about that if the situation were reversed)
Questions to ask new remote employees
“Have you worked remotely before?” should have been discussed during the interview. After the hire is not the time to start this conversation. The first time an employee transitions from in-office work to remote work is a substantial shift – more so than you hiring your first remote team member.
“What’s your schedule?” and “What times do you regularly need to be away?” aren’t probing personal questions. They let both sides discuss expectations and avoid surprises.
For example, I take kids to the bus stop a little after 8:00 am. I pick them up a little after 3:00 pm and a little before 4:00pm. As you might expect, there’s a few minutes of “cat herding” that takes place before the morning bus stop and after the two afternoon bus stops. While no one depends on me to be in a certain place with immediate availability at any specific moment of the day, it’s important to communicate the team’s schedule on both ends.
Likewise, it’s on me to make sure someone understands my schedule when we’re trying to arrange a meeting time. If I am trying to finish up before the bus stop or am rushed to get to a meeting just after a bus stop time, meeting prep (or the meeting itself) isn’t as productive or focused. That isn’t fair to clients or your remote employer. It’s as important to discuss the times where all hands are expected to be available for scrums, meetings, standups, etc.
Lunch is a good example of scheduling, even though you might not give it much thought. Some people eat lunch at their desk. Some like to get out of the house and meet a friend. Some mix it up a bit, often because working at home by yourself can be lonely. Some people need regular interaction, and text chat (like Skype, HipChat, or Slack) doesn’t feed that need. None of these things are wrong, but when your phone rings and you don’t answer, or you answer and a noisy restaurant is what your employer hears – they’ll wonder. It’s natural. You don’t want to make them wonder. You want them to know what to expect.
It’s OK to say “On Thursdays, I meet a few friends for lunch, so I’m not around from 11:30 to 1, and I start early or finish late those days“, as long as you’ve worked that out with people who need to reach you. This isn’t about someone expecting to know your butt is in your seat every minute of the day. It’s about being considerate of both parties. It’s about trust.
“Tell me about your workspace” – also isn’t a probing personal question. An employer or client has an expectation that you aren’t trying to work in a room full of toddlers, barking dogs, or gaming teenagers. Speaking of, summer plans are important. If you have young school-age kids, how will they be cared for while you’re working? Will they be in a different space than you? If the kids are older, it generally isn’t a problem, while two to seven year olds don’t generally manage their day on their own.
If this isn’t the new employee’s first remote rodeo, it’s a good idea to ask them what worked and what didn’t work in previous remote gigs. Take advantage of their experience and perspective – it will almost certainly add nuance to my comments. This gives you the chance to learn from another owner / manager’s efforts at no charge, and it will help you understand the persona, priorities and needs of your new remote worker.
Work out a protocol for communication during travel, weekends, evenings and during emergencies. This is really no different for a local employee than it is for a remote one, other than the fact that a manager can’t easily show up at the front door of a remote employee. If you’ve ever done that for business purposes, your communication plans probably need work. Showing up to pay your respects or attend a BBQ isn’t “business purposes”.
An emergency might be that your biggest client is having a meltdown or that there’s an angry boyfriend at the office. Either way, establish a protocol for getting the word out, conveying its severity, & indicating what action (if any) is necessary.
Keep in mind that every family (thus, every team member) may have different needs. Babies, shift work & roommates impact phone/ringer use.
Mentoring & the “first friend” – No matter how many years of experience they have, they’re new to you. New people need mentoring. Even if they don’t need it with the work you hired them to do, there are plenty of reasons why their “first friend” at work will prove beneficial.
Do you hire someone to stay in the same position “forever”, or do you want them to grow into a position they aren’t yet ready for? Even if you don’t expect a new hire would be ready to run your shop in five years, they’ll almost never get ready without training, mentorship and interim experience to prepare them for that role.
Qualified people still need mentors. They also need to be mentors. Maybe not today, maybe not tomorrow, but sooner than later – and with intention.
Connection – Remote employees need connection to the nest. Bring them on-site early and often. It’s particularly important to make this happen early on. Everyone at the home office needs connection with those remote employees. They need to be able to trust their word, trust their work and think of them as they do any other member of the team. This isn’t just about the line employee. It’s about the managers as well. When the remote employee becomes a black box in a room in another town that no one can see, the unseen person and their work are easy to devalue. This could happen even if their work happens to be strategic. The reverse is also true. They need the opportunity to understand the value of their peers work as well their colleagues do.
Team meals – For a business with on-site employees, team meals (on campus or not) are a commonly-used way to build team harmony and nurture relationships between team members. This may not be easy particularly effective with remote employees, so be sure to have these meals when remote employees are on site.
Video meetings (IE: conference calls with webcam) – Some people really dislike the addition of video to a call. People are fussy about their hair or generally how they look, don’t want to be seen eating during a call, are sensitive to what’s visible in their work space (like that monstrous Siamese cat laying next to the keyboard), and/or the idea of others seeing them appear to be disinterested because they’re multi-tasking during a meeting.
Ease into this. Start with short, less critical meetings to raise the comfort level. You’ll probably need to set the example for a while so people get comfortable with it. It’ll make everyone more aware of the ambient noise and distractions in their (and others’) workspace. In a face-to-face meeting, most people can manage their facial responses to a speaker’s comments. Experienced conference callers have learned to mute early and often, but may not be practiced at managing expressions when video is introduced.
The lesson: Don’t make a big deal out of the expressions you see on video. Use them as a signal to ask for group feedback. It’s natural for facial expressions to change when we hear something we have questions about, don’t like, don’t agree with, or don’t understand. I prefer the Zoom (all faces on screen) way of doing this, mostly because it seems to train everyone that their expressions change while listening to people talk. Most of us don’t want to embarrass a co-worker, much less ourselves. Use it as an advantage and an opportunity to improve, not as a way to create drama.
Does this differ for workers outside the US?
The differences between inside-the-US & outside-the-US team members include (in decreasing order of owner/manager/employee pain & suffering): Culture and values, enterprise experience, time zones, environment, infrastructure, payment & language.
Culture & values – Not everyone thinks like a U.S.-based employee/owner. Start by remembering that and keep remembering it. You’re used to what you’re used to. Others are just as used to their experience and how their work habits were formed.
Remember when asking for help was considered by some to be a sign of weakness? It remains that way among some groups because the pace of change differs among groups, and likewise among cultures. Every country’s culture has its range of work habits, inclination to ask for help, communication styles, etc. If you find yourself frustrated, ask questions that allow new people to unwrap what happened. Cultural learning is difficult to change. Differences in cultural norms should be expected. Both parties need to take steps to help everyone understand one another.
Company cultures and values work the same way. There are things that your company does your way – your culture and values. You should expect employees to take those seriously, regardless of their upbringing, culture, etc. Sometimes this takes training, mentors, etc. Someone who has never experienced a culture like yours will need help (and time) to them learn your culture and values. You may hire someone who is used to being browbeaten over deadlines, or they may have never worked under a deadline. No matter what their experience has been in the past, your experience is probably different. It will take time for your culture and values to become their new normal. Trust takes time and it goes both ways.
Enterprise experience – Enterprise experience is about more than buildings full of servers or time working at large multi-national companies. It’s about having a mindset that goes beyond the current project. It’s about having the ability to look around corners (and knowing that’s important), seeing the big picture, understanding inter-departmental needs, and communicating effectively with others whether they’re C-level execs, your team’s family members, prospects on the trade show floor, or high school kids on a field trip. Enterprise experience can mean more than that, but it starts with mindset, the big picture, and communication.
Time zones – Time zones can be a blessing and a curse. When your team member is seven to ten time zones east of you, you might start your day at 3:00 pm or later in their day. Good, because you have a bunch of work to review. Bad, because you only have an hour or two before the end of their day. Some folks work their normal hours (ie: 8:00am to 5:00pm in their time zone), some work normal hours in yours. You have to figure out what works best for you and for your team member. One thing about having them work your hours is that it may tempt them to take a job in their time zone, then work your job once the other job’s time is done. You need to ask that question. You don’t want your work to be their second job – which could affect your pay scale for them.
Environment -Not everyone lives in a pleasant, treed cul-de-sac in a neighborhood with people they’ve known for a decade, or on five quiet acres on the edge of town. I have had remote team members tell me that their apartment building was hit by gunfire – and they kept working. Culture & experience train you to know when it’s time to take cover, leave, etc.
Infrastructure – People in some countries lose power far more often than U.S. folks are accustomed to. This is not something your remote worker can control, other than by moving to another country. The good news is that a laptop combined with a UPS can easily fuel a full day’s work.
Payment – Five years ago, this was much harder. Paypal, TransferWise, Upwork simplified the process & traditional methods are still available. Some countries are still a bit of a challenge but for the most part, this barrier has all but evaporated.
Language – Most business people I encounter from outside the U.S. speak English fairly well. This has been my experience with both solo consultants and employees of large companies outside the U.S.
One more thing about remote folks. Visit them a couple times a year, if you can. It won’t be cheap. It probably won’t be easy and it will occasionally frustrate – but most of the negatives come from getting there, not from being there. When you visit them, you learn far more about them, their motivations and how they work than you’d ever learn in a video meeting or a phone call.
Links for working with remote employees
A few links that might come in handy: