Good article. Having a lot of experience managing remote teams, I wanted to expand on this point: > Try to focus on the employees who thrive in such environments rather than those few bad apples. You can’t let the bad apples define the work experience for everyone, but you do need to identify them and remove them as fast as possible so they don’t poison the well. One thing I didn’t realize at first was that remote wo…
Well said. There also are websites that are openly encouraging working 2 full time remote jobs concurrently/at the same time. I don't want to name those here but wow.
Building Remote Teams for Startups
31–40 of 91 posts
Re: Building Remote Teams for Startups
#32It is darn hard to build a remote team unless you have a thorough understanding of what needs to be done and how it should be done. My opinion is that if you are hiring people remotely you should be operationally skilled to understand their effort, struggle and deadlines. BE EMPATHATIC. If you are running a remote team and you follow the mantra of "hire slow, fire fast" good luck keeping your employees. Make your decisions by getting a second opinion from the employees mentor.
For the feeling of belonging, I would say send your employees merch or an old laptop or something that shows that they are part of the team. I say give people very small bonuses but that is a whole thing. The "thank you"s you say to the other guy on an hourly basis, maybe give a bonus or something on the 10th Thank You, like a small small bonus. Thank yous over chat sound generic. In a super objective straightforward world of remote work money is the convenient way to show appreciation....here I go ranting again.
For pair programming, use VS Code live share with Google Meets. If you and your team is comfortable with it set up a period of time where all of you guys are working together over a group video chat like streamers do. I personally would love seeing my fellow coworker working on something halfway across the world.
If your work environment is super feature-execution driven, having a "fun" slack channel is meaningless. Office noises almost never happen in remote work environment as the employers is paying by the hour. But it is important IMO. But I don't think anyone out there is any employer out there would say, "let's have a weekly virtual meeting where we exclusively don't talk about work, but I will pay you guys anyway; We can drink and talk about stuff".
Re: Building Remote Teams for Startups
#33> In my opinion, a decentralized, remote workforce is the future of the digital economy. This is based on the wonky assumption that this: > There will always be people who abuse the system, abuse your trust and try to game the mechanics for their benefit. […] A remote gig is not a good fit for these kinds of people. are just some extreme outliers. However, we were just yesterday having a discussion on HN about „how t…
Also, remote just doesn't work for some people. This should be decided on a per-company basis
Re: Building Remote Teams for Startups
#34When I’ve asked friends and coworkers how they like remote work, the answer depends on how comfortable they feel being candid with me. Publicly everyone says they’re more productive being remote. Privately, people admit that their productivity has cratered, being home is very distracting, and the lack of separation between work and home life makes both realms more difficult. I definitely empathize with the answers I’…
Personally I enjoy going to the office most days, even thought I don't have to. And know plenty people that do as well. What I hope comes out of all these pandemic adjustments, is more diversity in work modalities to choose from instead only one or the other. That remote employers and employees get better working that way and that on-site/hybrid employees put more effort into making themselves more attractive. E.g. i…
That is not satisfying to anyone.
Re: Building Remote Teams for Startups
#35Good article. Having a lot of experience managing remote teams, I wanted to expand on this point: > Try to focus on the employees who thrive in such environments rather than those few bad apples. You can’t let the bad apples define the work experience for everyone, but you do need to identify them and remove them as fast as possible so they don’t poison the well. One thing I didn’t realize at first was that remote wo…
Let me expand on that point: "Don't accidentally throw out good apples with the bad ones because you are looking at the wrong metrics." What I mean is: Bad apples are real, but don't ever do time-tracking or fast response testing in an effort to identify them. There are some excellent apples who will get your 8h-day deliverables done in 2-4h. Don't ever establish any system to find them. If you have a problem with th…
Re: Building Remote Teams for Startups
#36When I’ve asked friends and coworkers how they like remote work, the answer depends on how comfortable they feel being candid with me. Publicly everyone says they’re more productive being remote. Privately, people admit that their productivity has cratered, being home is very distracting, and the lack of separation between work and home life makes both realms more difficult. I definitely empathize with the answers I’…
There’s also a difference between working remotely and being thrown into working remotely at the last minute during a pandemic with no prior experience. I’ve been remote for the last 10 years and the vast majority of problems you mentioned get better over time if you work at it.
Re: Building Remote Teams for Startups
#37Good article. Having a lot of experience managing remote teams, I wanted to expand on this point: > Try to focus on the employees who thrive in such environments rather than those few bad apples. You can’t let the bad apples define the work experience for everyone, but you do need to identify them and remove them as fast as possible so they don’t poison the well. One thing I didn’t realize at first was that remote wo…
Re: Building Remote Teams for Startups
#38Good article. Having a lot of experience managing remote teams, I wanted to expand on this point: > Try to focus on the employees who thrive in such environments rather than those few bad apples. You can’t let the bad apples define the work experience for everyone, but you do need to identify them and remove them as fast as possible so they don’t poison the well. One thing I didn’t realize at first was that remote wo…
For software engineering, four hours of actual work per day is probably average even on-site.
Re: Building Remote Teams for Startups
#39> However, they probably need a stricter environment to function correctly, more robust control over their work – meaning they thrive when someone is looking over their shoulder. A remote gig is not a good fit for these kinds of people. There's a lot more of those folks than you might think. We have a fairly "skewed" sample set, with geeks (especially the ones that frequent HN). A lot of us love to work, and we'll do…
How did they teach this?
Re: Building Remote Teams for Startups
#40Good article. Having a lot of experience managing remote teams, I wanted to expand on this point: > Try to focus on the employees who thrive in such environments rather than those few bad apples. You can’t let the bad apples define the work experience for everyone, but you do need to identify them and remove them as fast as possible so they don’t poison the well. One thing I didn’t realize at first was that remote wo…
For software engineering, four hours of actual work per day is probably average even on-site.
https://www.inc.com/melanie-curtin/in-an-8-hour-day-the-aver...
Has held true at all 7 jobs I have ever had.