Remote work is on the rise, with more and more companies adopting it at the point of becoming the new normal.
It seems a great market to target, but at the same time the main issues seems to have been already solved by Slack/Twist, Hangouts/Zoom, Basecamp, GitHub, Asana, Jira, Trello, Todoist, Harvest, etc (and other thousands of alternatives).
My question is: What is still unsolved? What are the annoyances/difficulties you've had as a remote worker? What did you notice that could be improved in your remote team?
Please share your thoughts and ideas about this. π
There are tons! That being said, as a new remote worker, I'd really love to collaborate on any of these:
On the company side:
As an employee or remote worker:
There are more.
I agree with you. Do you have any thought on how a distributed team could help with loneliness of their team members?
On the team side, regular check-ins, face-to-face time and possibly more creative solutions - maybe introducing virtual breaks where everyone joins Google Hangouts? I dunno.
Personally, just making sure you have a stable social environment. Going to dinner with friend 1-2x per week. Having a girlfriend. Talking to the parents more often.
Completely agree with face-to-face time. This is remarkably important and almost always overlooked in favor of Slack / text-updates. I recently worked with a team that had weekly video group chat and the project managers all did 1-on-1 video chats on a regular schedule ... Not only that, but they encouraged team members to video chat rather than make a phone call even if it was just for a short chat. It has a profoundly positive effect on culture, identity, cohesion, etc.
It was the first time I actually 'knew' my team on a distributed project. I can't believe this is not standard practice.
This comment was deleted 6 years ago
That is awesome. Following to know how it evolves
This comment was deleted 6 years ago
Just shared your question on Remotive Slack Community to get more answers :)
To me, the core issue is trust.
If remote workers / distributed team trust each other, the rest flows. Then, all software and tools become enablers.
As you wrote, thousands of alternatives exist. Slack is sexier than HipChat, both address the same need. Of course, UI/UX is sexier and integrations are smarter - yet it's the same spirit.
Two examples on how trust makes or breaks remote teams:
(1) If trust levels are low, no software will make up for the anxiety of someone wondering if their boss is about to fire them or if "folks back at HQ are gossiping about me".
(2) Also, in low trust environments, folks tend to over-work (risk of burn out) and use software as crutches and testimonial of their work ("My Slack dot is green, of course I'm still on at 10pm!")
Few possible reasons (non exhaustive):
(1) Value misalignment. A company may wish well and have friendly values, yet what matters is actions, not words. For example, several remote startups value "work life balance" and are fine with having employees hustle on Slack and join meetings at odd hours. This feels like a value misalignment, what was advertised by the company is not what employees lives - causing stress and low trust.
(2) First timers. Companies, managers or remote workers may mean well yet it takes time to "get it right" so that all 3 are aligned and happy with their set-up. Teams that are still finding their feet are tricky to work with because remote workers may not know "what they will change next!", affecting trust
(3) Mixed teams. It's a biggie. Partially remote team (with an HQ) often try to solve their challenges with software whereas culture may work best. For instance, Trello once had a "one person, one screen" policy for each meeting. That meant that there wouldn't be 10 people sitting in a conference room on one screen facing a bunch of lonely remote workers. Expectations were set by culture, helping to build trust.
--
In my opinion, trust isn't built by being right all the time but by how leaders act when things go wrong.
So, remote teams core issue is trust, all issues @dqmonn listed are valid and painful.
Tools helping to set expectations and shorten feedback loop tend to be sticky(knowyourcompany.com / officevibe.com). Also, Buffer pays for anonymous, chat-based mental health support for all team members.
Helping to build trusted environments feels key, whether it's through software or community. Teams will low trust may gravitate to "tracking tools" where teams with high trust will think about "enabling/support tools"
Hope it helps, keen to hear more thoughts on the topic!
Thanks for sharing in your slack and for your input here π
This is a great insight and got me thinking, thanks.
Fix the timezone issue. That I have to wait on my coworkers (who are great BTW) and they have to wait on me too because we live on opposite ends of the globe.
There's a challenge....
Thanks for the answer! So do you think asynchronous work does not work very well? Or are you talking mainly about meetings?
On the asynchronous note, I'm rooting that our (remote) team switch to Twist. Their approach to asynchronous work just makes sense.
It's kind of like GitHub issues, but for the whole team.
Twist seems great!
The asynchronous work, mostly. example: if I need something done "before the end of the day" but one of my employees will just be waking up at that time. In that case the work falls to me. Doesn't happen often, but sometimes there are fires to put out.
I've worked remotely for almost a decade and recently I was wondering what has changed, so I joined a few Facebook groups for remote workers.
One post that someone shared was this one:
https://open.buffer.com/state-remote-work-2018/#benefits
It highlights several struggles around working remotely, and I started digging some more and saw this report (https://www.tsheets.com/resources/remote-work-survey) and others.
Here are some common challenges for remote workers:
Once I was aware of those, then I started noticing them in different social media channels. I asked about loneliness in one of the Facebook groups, and it was interesting to see the discussion unfold as there were remote professionals that could relate and there were others that said they enjoyed working remotely so they could avoid people.
At some point in my career, I experienced the struggles above and others, and I handled them by creating habits and systems.
Here is what I shared in one conversation about loneliness as a remote worker:
This year I've prioritized my wellness as a remote professional and its one of the best decisions that I've ever made. Before health was on the sidelines and now it is top of mind, so things, like getting enough sleep, exercising regularly, making healthier food choices, and taking time to relax and recharge are essential.
I'm researching sleep and remote workers. Would anyone that works remotely be up for a quick chat?
Thanks π Could you share some of these groups for remote workers that you mentioned?
Hi Bruno,
Sure! Here are a few of them:
I've worked remotely in my last two jobs so am really interested in the topic.
Two resources I'd refer to are:
Remote Only (https://www.remoteonly.org) - they detail a manifesto for remote work and explain some practical tips, benefits, disadvantages, and affects on the organization.
*Remote: Office not required *(https://basecamp.com/books/remote) - a book by DHH (founder of Ruby on Rails & Basecamp). It has lots of practical tips.
Remote only is a great resource.
Could you share some issue you noticed based on your personal experience?
The two hardest problems for me have been:
Thanks π
Yep it's true, probably because we kinda need to see people faces, emotions and reactions; an avatar is far from enough.
Hey Guys! Sorry for jumping in late.
I think one problem that's yet to be fixed (and fixed right) is, getting the team to keep learning / upgrade their skillsets / stay updated on what's happening in the industry, etc.
Existing solutions, Feedly (essentially, your subscribed feeds), Video Courses, etc. have bad noise to signal ratio, ask for an immersive-long-tenure commitment, too much time is spent on picking the right thing to learn, etc.
I look at the ol' days LMS (Learning Management Systems) approach. It's looked down upon now but it did serve the purpose. I also liked that approach of mapping learning to KPIs.
I think what needs to change is the method of delivery of this "learning modules" from LMS days. I like Google Primer's approach a lot (Tinder-style cards + MCQs). A Google Primer-style app that's designed for your company's training/learning needs - 5-minute lessons, 5-10 MCQs and a score.
If I had to use this app at Springzo, I would love to have the following modules:
The possibilities can be endless. Over a period of time, the app also acts as a repository or internet knowledge portal for the company.
What do you guys think?
Remote work is a massive challenge (and opportunity). I've spent the last couple of years building software to help distributed teams feel more connected (www.fridayfeedback.com).
Specifically, here are a few ideas:
loneliness is a major problem with remote work. I've wanted to build something around helping remote people who live in the same city connect.
Understanding what's going on (this is where I've focused). There's all kinds of task-management tools, but a little bit of abstraction away from the work itself can be helpful.
Agile/scrum processes oftentimes break down with people in different timezones.
This is totally worth pursuing. I've been having a blast helping team leads/companies with this. It's a very real pain.
I've worked with a distributed team the past 18 months and these are the theee points that I'm interested in solving as well.
This comment was deleted 6 years ago
I manage a team spread between a few time zones. We're great with the tools that help with remote work, and have years of experience, but it is still astounding how much more we can accomplish when we get together in person.
it's a challenge to plan our in person gatherings. everyone wants to accomplish everything, talk high level strategy and get our hands dirty in the weeds.
while we are remote, it's hard for the team to know which conversations are best for async on github vs realtime on slack vs face-to-face over video. it's so important to get this right β for efficiency, morale, and effectiveness.
Thanks for your input! What tools do you use besides Slack and GitHub?
Nothing too surprising: Google docs, Vidyo (crappy video tool). We've played with others (Zenhub, Airtable, Roadmunk). The main thing is communication: finding the balance to keep it natural and regularly, while maintaining independence and avoiding disruption.
I've recently been playing with Coda.io and started to get very excited looking at some of their templates. It's a breeze to use. Very flexible. I'm unsure if other members of my team will buy into it.
Just took a look at Coda. Try https://www.notion.so/, I think you are gonna love it.
This comment was deleted 6 years ago
Looks very interesting @keithnerdin!
This comment was deleted 6 years ago
This is of interest to me. Just thoughts below
Peter Thiel in an interview by Maria Bartiromo said, telecommuting and remote working is underrated and something he would love to invest in. I can find the video if interested. Upon some research it seemed he was referring to investing in VR/AR tech for remote employees.
Slack, basecamp, GitHub, asana, internal wiki, jira, Trello, etc. or similar cloud-based productivity tools are useful regardless whether users are remote or not. (Although looking at the signal to meme ratio on private slack channels, it is hard to argue if they are still productivity tools).
Zoom video sharing, Skype, group FaceTime, file sharing, folder sharing, collaborative document editing, screen sharing, and screen-control sharing tools solve a general problem, and can be used for code review, pair programming, root cause analysis, discussions, sales, presentations, telemedicine, training, education, culture-building presentations, support etc.
A team I managed between Seattle, Bay Area, and Amsterdam played online games together and worked well together as a result. We tried to watch God father series together, but I wouldn't call that a huge success.
Managing remote teams is a huge challenge. By this I mean beyond time, task, project, & product management which are handed well by cloud-based productivity tools. Something to delve into further.
I agree that doing non-work things together makes the teammates feel more closer to each other and work better together.
This comment was deleted 6 years ago
I definitely struggle with the overwhelming number of information feeds and the feeling that you need to stay on top of everything. I'm sitting in a dozen or more different Slack channels, but really only ever able to pay attention to a few, probably missing out on a lot of great stuff. There also seems to be this desire to segment everything so no single channel becomes too overwhelming, e.g. public channel, team channel, operations channel, stand up channel, lounge channel. Email is no better.
So I guess i'm saying a lot of remote people could probably use some help staying organized and identifying the really valuable content.
I believe this is one of the things Twist is trying to solve with their slack alternative.
Right, it certainly looks interesting. From what I saw on their site it doesn't really seem all that different though. Direct messaging and threads already exist in Slack. The layout is certainly different and reminiscent of your inbox.
Figuring out a remote company culture is complicated. The lack of face-to-face interaction can be challenging when people never met in person. That's usually solved with company-wide trips where everyone meets for a few days a couple of times per year, but that can be complicated/expensive to coordinate, the bigger the company becomes.
Again, communication is challenging when people are in different timezones. It's easy to get blocked waiting for someone to get back to you but they will only be online again on the next day.
Even when you're in the same timezone, some things are really hard over video chat like whiteboarding for example. You have to keep everything on paper, need discipline and organization to make it work well.
It's also challenging for junior developers when they need a lot of guidance, working remotely if you're new and learning is hard.
Long story short, it's all about communication. You can definitely make it work, but there are real challenges. With that said, wanted to say I'm a big fan of remote work and I'd love to see more companies adopting it.
I wonder if anyone has taken a data-driven approach to figuring out how cultures develop and then productizing that. For example, track the correlation between face-to-face, video-conferencing, slack comments, etc. against attrition, promotion rate, discipline issues.
This comment was deleted 6 years ago
This comment was deleted 6 years ago
This comment was deleted 7 years ago
Yeah I thought about the same idea and also came across this and a couple other existing apps. But I still think the way they implemented is not good for privacy so there's still room for improvement. Have you used it? Does it really helps with loneliness?
This comment was deleted 6 years ago
I am looking for a remote job - UI/UX Design/Development.
Design Skills : Adobe Creative Suite, User Interface (UI), Prototyping,Branding, Wireframing, Responsive Web Design (RWD), Web Design, InVision, Android UI Design, iOS UI Design
Development Skills : HTML/CSS, PHP, WordPress, Laravel, jQuery, Vue JS
Thank you.