3 ms·
I manage a fully remote team with staff in time zones from Sydney to LA. In fact I've just messaged people in both zones. Culture is key: - People have to be
by lordnacho 8y ago
I manage a fully remote team with staff in time zones from Sydney to LA. In fact I've just messaged people in both zones.
Culture is key:
- People have to be of the mindset that meetings are short and purposeful. Nobody is in the meeting because they are the boss, or forced to join in order to soak up the atmosphere. (Both of those are real things, somehow).
- People exercise judgement in deciding how many people to write to: either DM, or 3-way, or dump it in a public channel.
- Most work is async by far. People post what they're up to, and other people will go and bother them if they're doing something relevant.
There's good and bad things about this:
- We can hire people who are highly experienced, and offer them totally flexible work. Some people like working at 3am. Others like to pick up the kids from school.
- We tend to only hire highly experienced people. There's nobody with under 8 years of work on the team. Juniors will have to somehow convince us they can do it; it's somehow more believable that an older person will be able to work independently than a younger one.
- Work blends in with not-work. Some people like having a division, other people like being flexible and moving their work time around.
- mcny 8y ago» People exercise judgement in deciding how many people to write to: either DM, or 3-way, or dump it in a public channel. I still haven't figured this one out. Unless it is a criticism or "hey you broke this", my thought is the default should be a public channel, no?
- sokoloff 8y agoThat's my default as well, because I value the durable, searchable record. (In Slack [and presumably others],) You can set notifications per channel and turn some channels into "pull" type consumption.
- toast0 8y agoIt depends on how many people are in the channel and the expected purpose of the channel. There is certainly some amount of information dissemination by having discussions in a public forum, but you have to weigh that against the information processing burden it adds to the people in the group. Also, it may become searchable, but it's only findable if you and your communication partners use consistent, appropriate, and relatively unique keywords. There are likely better ways to document things; although, documentation is one of my worry areas, and I understand the desire to have something rather than nothing.
- izacus 8y ago> - We tend to only hire highly experienced people. There's nobody with under 8 years of work on the team. Juniors will have to somehow convince us they can do it; it's somehow more believable that an older person will be able to work independently than a younger one. Hm, does that imply that you don't have any process or provisions to train up juniors / begineers?
- mikemcquaid 8y ago> does that imply that you don't have any process or provisions to train up juniors If they don't: that's fine. It's better to not hire juniors if you aren't able to provide the mentorship they require than hire them anyway into an organisation that will fail them.
- planetburgess 8y agoWe worried about this but it has proven unnecessary. Juniors can thrive in remote settings if they have the right personality. E.g. Someone who was very disciplined with their University study and assignments I think shows a good base for working remotely. But take time with onboarding and training. The biggest mistake we made was letting people rush through training. When remote and particularly asynchronous you'll have times you can't ask anyone for immediate help. So basic process and understanding need to be deeply embedded during training.