Content
@
1 reply
0 recast
2 reactions
Jack Miller
@jackm
My engineers all want to WFH but only like 10% of them are any good at it The rest get lost or create friction that slows down other people How do you navigate this?
3 replies
0 recast
2 reactions
kbc
@kbc
1. How much overlap is there in time zone between people? 2. Do people need to see other people to work? 3. Do people expect an answer as soon as they post in your comms platform? 4. Are people able to express themselves clearly in writing 5. Does most conversations happen in public channels or DMs?
1 reply
0 recast
1 reaction
Jack Miller
@jackm
1) Everyone is local 2) Pretty often 3) I do lol 4) Mostly yes but I often have to call them because chatting isn't cutting it (complex or technical stuff etc) 5) DMs
1 reply
0 recast
0 reaction
kbc
@kbc
lol your team isn’t ready for remote work. Most important to fix 1. People need to be able to motivate themselves to get stuff done 2. People need to be excellent at written communication Move most communication to public channels. Unless you are sharing a lot of sensitive information Begin with a meeting free day on Monday, Wednesday or Friday where coming to the office is optional. People need to do a async checkin (write a thread at the end of the day what they accomplished. If they fail they have to bring cookies/pizza/cake to the office the next day) https://async.twist.com/asynchronous-communication/ And check out gitlab’s handbook. Or the guy from Timedoctor. He’s running the running remote conference
1 reply
0 recast
1 reaction
Jack Miller
@jackm
This is great stuff, thanks!
0 reply
0 recast
1 reaction
