Ask HN: How do you communicate in a remote startup?
281–290 of 290 posts
Re: Ask HN: How do you communicate in a remote startup?
#282Re: Ask HN: How do you communicate in a remote startup?
#283While slack seems like popular suggestion, its not made to keep structured information and what happens is that you have some discussion in slack, some discussion in a meeting that was not recorded and then, in a best case scenario, some conclusion in Confluence. This is a bummer because a lot of information was lost, specially the logic behind a decision. It would be far better if the discussion happened in writing within the comments section of the document. Now all the context is in a single place and searchable. Plus its possible to add to it somewhere in the future, so the document base doesn't necessarily grow with time.
Re: Ask HN: How do you communicate in a remote startup?
#284Earlier quoted context omitted.
>Meet in person every quarter What benefit would you see in doing this? The only thing I've heard is some consider it nice to be in close proximity to others, but that doesen't really sound like a business reason
Quarterly would be a gross misuse of budget, imo. I think there’s tremendous value in physically meeting your team—-I can’t quantify it, but I can feel it—-so once a year is good, to me. Maybe twice if one is business and one’s a party or something.
As you said it's hard to quantify the value, but anecdotally I notice it most in 3 (distinct but somewhat overlapping) areas:
(1) Overall morale - everyone enjoys work more when you have a good relationship with your coworkers, so people are willing to do more than the bare minimum. People approaching burnout feel more enthusiastic about work afterwards. (2) Everyone is more inclined to help each other out with tasks outside of their routine but within their skillset, reducing bottlenecks. (3) Similarly, you develop a better sense of each other's personalities and skillsets in a way that's much more difficult when remote, so communication is more efficient, and collaboration more effective due to that increase in understanding and empathy.
Re: Ask HN: How do you communicate in a remote startup?
#285In person collaboration is best, but for a fully remote company and geographically distributed team I think we've built the next best thing.
Many of us are on camera all day, others pop on just for scheduled meetings. But with the mix of working styles we've managed to maintain a pretty healthy culture, where we can have some of the spontaneous interactions that are so important.
Re: Ask HN: How do you communicate in a remote startup?
#286Earlier quoted context omitted.
Yeah there are plenty of things that shouldn’t be said in a public. Problems that haven’t been verified yet, ideas that haven’t been through etc… If your company is big enough there’s bound to be someone above you who will hold you to the first version of an idea you threw out or who will freak out about something that may not really be a problem.
> Yeah there are plenty of things that shouldn’t be said in a public. It is worth pointing that one of the value adds for any company using Slack is that nothing is private . Anyone with an admin role can read any conversation, DM or otherwise, and this is considered a good thing since it allows the company visibility into employee communications in cases of illicit activity. What's odd is very few teams I've been on…
They could also export messages and give anyone they want access to the resulting dump I suppose.
Re: Ask HN: How do you communicate in a remote startup?
#287Re: Ask HN: How do you communicate in a remote startup?
#288Re: Ask HN: How do you communicate in a remote startup?
#289Earlier quoted context omitted.
Nothing team-related should be in email. It's a horrendous place to hide data - worse than even than slack private channels.
Only because we've ruined our email with automated systems that are way too trigger-happy on notifications. I think I've received atleast a thousand-fold amount of mail from JIRA that someone has clicked on something, compared to actually useful, actionable requests.