Live data from Hacker News

21 Months In: How to Manage a Remote Team

zapier.com

31–40 of 50 posts

Re: 21 Months In: How to Manage a Remote Team

#31
post #28

Earlier quoted context omitted.

In an office nobody pops in every 8 seconds and takes a picture of you. All this talk about trust is essentially useless if you're under surveillance all the time.

I equate it to Google Talk. Replace "webcam picture" with "online status" and you can say remarkably similar things about the two. Both Google Talk and Sqwiggle are meant to facilitate communication and not to be used as accountability tools, but if you don't trust those you're sharing that info with then it could be used that way. Both give out signals of my online status based on my presence, and both can manually…

However you spin it, I don't think many people would enjoy having a webcam on them as they code. It doesn't sit well. Chatting is one thing, because there's no sense of someone watching you. There's a certain creepy factor about not knowing if someone else is just watching you on their screen.

I've used Campfire, IRC, Skype, GTalk, and most recently Hipchat with various agencies and startups. It's just my personal preference to use that over face to face when we have random questions.

Re: 21 Months In: How to Manage a Remote Team

#32
Another bit that is really important I find as a remote worker: feedback. While it's nice that you can get long, uninterrupted stretches of work it becomes a problem when you can't get a snappy answer to a simple question because everyone has their head down and is ignoring their email, IMs, etc.

You have to be more up-front with your availability and response times. One thing that irks me working on remote teams is the person who leaves their online status as "available," all of the time. It can be infuriating when you send someone a message and not get a reply for hours. I find you have to manage your statuses a little more carefully. However the payoff is nice because you can't always mediate conversations like that in a co-location setup.

Re: 21 Months In: How to Manage a Remote Team

#33

Earlier quoted context omitted.

I equate it to Google Talk. Replace "webcam picture" with "online status" and you can say remarkably similar things about the two. Both Google Talk and Sqwiggle are meant to facilitate communication and not to be used as accountability tools, but if you don't trust those you're sharing that info with then it could be used that way. Both give out signals of my online status based on my presence, and both can manually…

However you spin it, I don't think many people would enjoy having a webcam on them as they code. It doesn't sit well. Chatting is one thing, because there's no sense of someone watching you. There's a certain creepy factor about not knowing if someone else is just watching you on their screen. I've used Campfire, IRC, Skype, GTalk, and most recently Hipchat with various agencies and startups. It's just my personal pr…

It's definitely not a one size fits all situation, there's room for personal preference. Just upthread there's someone lamenting a downside of GTalk and the like. I'm only saying that while the concept definitely sounds a bit invasive, the actual downside is really no different than that of widely accepted alternatives that don't have that stigma.

Re: 21 Months In: How to Manage a Remote Team

#34

Another bit that is really important I find as a remote worker: feedback. While it's nice that you can get long, uninterrupted stretches of work it becomes a problem when you can't get a snappy answer to a simple question because everyone has their head down and is ignoring their email, IMs, etc. You have to be more up-front with your availability and response times. One thing that irks me working on remote teams is…

Sqwiggle from the article sounds like it would make it more obvious when everyone is working.

Re: 21 Months In: How to Manage a Remote Team

#35
post #4

I setup a recurring monthly event with each team member where we both jump on Skype or Google Hangout to chat about three things: what's one thing I can do better to help him with his job, what's one thing he can do better to improve at his job, and what's one thing the company can do better to make everyone's lives easier. I was just talking with a friend of mine about this very topic -- it's critically important fo…

http://en.wikipedia.org/wiki/Kaizen

Re: 21 Months In: How to Manage a Remote Team

#36
post #4

I setup a recurring monthly event with each team member where we both jump on Skype or Google Hangout to chat about three things: what's one thing I can do better to help him with his job, what's one thing he can do better to improve at his job, and what's one thing the company can do better to make everyone's lives easier. I was just talking with a friend of mine about this very topic -- it's critically important fo…

> I'd love to see some statistics on what kind of effect a half hour per employee per month does for overall happiness and employee retention.

I would too, and here's some anecdata for you: one of my old bosses would conduct weekly one on one meetings with all of the developers on his team (anywhere from 4 to 8 of us at different times) and I'd have to say that personally they were some of the best manager-direct experiences I've ever had since.

One on one meetings are one of the most important tools out there for helping organizations build relationships with their people, helping them produce more results, as well as increase retention.

Anybody interested in starting them at their organizations should check out the manager tools website. They produce several weekly free podcasts as well as offer other products and services.

https://www.manager-tools.com/docs/Manager-Tools_One_on_One_...

http://www.manager-tools.com/2005/07/the-single-most-effecti...

Re: 21 Months In: How to Manage a Remote Team

#37
communicate communicate communicate

I've worked in several jobs with remote teams (as the team and managing the team) and the difference between the ones that worked like clockwork and the ones that didn't almost inevitably came down to communication.

The amount of time and energy sorting out problems because of a lack of communication will absolutely dwarf the amount of time you should have been communicating.

- Have at least 1 weekly roundup, guaranteed, no exceptions. Even if it's just for everybody to get together and say they have nothing to report, that is even in and of itself a communication. Some places did daily end of the days, some did Mon & Friday mornings, it doesn't matter. Do it.

- Use more efficient communication proxies when possible: trello, jira, salesforce, whatever. Enforce it with an iron fist. Don't let people get away with not using the tools, they're easy to use and if you get in the habit, saves hours upon hours of time. I love love love Trello for this.

- Have constant ad hoc communications. IM, phone, email. Schedule times so you don't interrupt somebody's work day. Missing a scheduled time should be a shocking breach of protocol.

- Please try not to use speakerphone or conference room speaker phone, it makes the meeting unpleasant on the other end and much harder to undertand.

- Google docs, really great for drafting up things and early collaboration. Switch to Office for the final work.

- if you can afford it, have as many face-to-face meetings as possible, be it once a week, or once a quarter, or once a year. Try and make the effort. I've found that learning people in-person helps smooth over digital communications.

- document document document - everything. Have a centralized and constantly organized document repository. People leave, sometimes without doing a good handoff. Not having good documentation will kill a company for months or years.

I agree with most everything else here: especially "5. Hire people who are ok without a social workplace."

Amazingly, most people don't actually realize what it means to work alone every day, all day. I've had a couple people go a bit loony and flake out after a few months on their own. The environment was discussed, and they felt confident about it, but simply couldn't handle the reality of it. If this is a requirement, prepare for issues no matter what. Try and hire people with a track record for this kind of work.

One guy ended up hitting bottle pretty hard (bars can be chatty places), his wife filed for divorce, and he simply stopped showing up to work. Working remotely it took a couple of weeks of no shows on the weekly all together to figure it out. He ended up quitting and moving to the desert to sort his life out. Working alone simply shattered him.

And finally, "4. Hire people who can write"

You wouldn't believe how many emails I've received from certain remote workers that are utterly indecipherable. You think most native speakers of a language with some college in them can write an intelligible email. It turns out many can't. And you waste lots of time clarifying, making phone calls, etc. And the worst case is you go off on the wrong direction.

Re: 21 Months In: How to Manage a Remote Team

#38
post #37

communicate communicate communicate I've worked in several jobs with remote teams (as the team and managing the team) and the difference between the ones that worked like clockwork and the ones that didn't almost inevitably came down to communication. The amount of time and energy sorting out problems because of a lack of communication will absolutely dwarf the amount of time you should have been communicating. - Hav…

[deleted]

Re: 21 Months In: How to Manage a Remote Team

#39
post #28
post #26

Earlier quoted context omitted.

Interesting. Versus having to sit in an office?

In an office nobody pops in every 8 seconds and takes a picture of you. All this talk about trust is essentially useless if you're under surveillance all the time.

They don't have to. You're sitting right there.

Re: 21 Months In: How to Manage a Remote Team

#40
> Everyone does support

I once worked at a company who did this. It was terrible on the developers. It destroyed productivity. It destroyed flow. And it was really just a way to plaster over not having clearly defined software goals and processes. If you develop software in a _professional_ manner, you can really do amazing things for the customer without making your 6 figure salaried senior programmers answer phones and tell people to try rebooting their windows machine.

The developer doesn't need to 'hear the voice of the customer' if the customers needs are being accurately transformed into proper specifications and plans by competent technical leads. The developer will meet the needs of the customer through creating excellent, testable, modular and clean code that excels at meeting the specifications.

Post reply on HN