Live data from Hacker News

Ask HN: How do you ensure everyone on the team is heard on Slack?

news.ycombinator.com

31–40 of 112 posts

Re: Ask HN: How do you ensure everyone on the team is heard on Slack?

#31
In my experience (11 years fully remote/distributed growing from 90 to 2000 employees) my first impression is it sounds like you’re doing too much synchronous. Async is so efficient.

My team’s current systems: - Most deep discussions happen on blog posts including project status. We use (and built) https://wordpress.com/p2/. We don’t use email. - Start of week everyone prompted to post what they did last week and what they plan to do this week. Also have a kinda fun ice breaker question that is easy (e.g avoid asking about favorites) and sometimes generates discussion. Last week was “Pick an olympic sport to represent your life.” - Daily Slack prompt to give folks a place to report on yesterday/today. The most important thing is how people feel though. “Pick a red/yellow/green emoji for your status” and “What feels risky or a blocker?”. Create space for feelings. - weekly team meeting is then about discussions and never about status. How do we solve X? How do we feel about Y? - debugging and such does occur in Slack but longer discussions are on blog posts/comments and so can be long. - I do 1-1s weekly for new folks and bi-weekly for longer term folks. Encourage sync 1-1s between the team also.

A lot of the prompts can be automated. I dont consider them mandatory, if you get them right then folks will be happy to do them because they feel the utility of them.

https://ma.tt/2020/04/five-levels-of-autonomy/ Is a good read too.

Iterating is very important though (which you are doing yay!), I’ve tried lots of different cadences/systems but the above is the core of what my team has used for 3-4 years now and I’m pretty happy with it. I still try to make sure we reconsider if we want to experiment with something new every few months. Partly why I wrote this long comment is I’m thinking if there is anything to tweak.

Re: Ask HN: How do you ensure everyone on the team is heard on Slack?

#32
Just spitballing...

I wonder if anyone has tried using a private subreddit for team collaboration? I feel like it has the opportunity to be a great asset. It's free, persistent, searchable (ish), supports threads, images/links/markdown, and even nice mobile app support.

Re: Ask HN: How do you ensure everyone on the team is heard on Slack?

#33
post #32

Just spitballing... I wonder if anyone has tried using a private subreddit for team collaboration? I feel like it has the opportunity to be a great asset. It's free, persistent, searchable (ish), supports threads, images/links/markdown, and even nice mobile app support.

Too easy to get distracted.

Re: Ask HN: How do you ensure everyone on the team is heard on Slack?

#34
We push Fly.io discussions to an internal forum (Discourse for Teams). Slack is an especially bad place to work async. And we want people to work async as much as possible.

Forum posts will frequently include a link to a Slack discussion, but I don't think anyone really clicks to read the chat.

This is not exactly what you asked, but peoples' managers are on the hook for helping them be heard. One-on-ones frequently trigger forum posts. Good one-on-ones are useful for this kind of thing.

Re: Ask HN: How do you ensure everyone on the team is heard on Slack?

#36

What has worked for my (mostly) remote team is a mix of different tools for different communication needs: - Daily standups on Zoom. Each person's standup should be short and to the point. Don't be afraid to tell people they're getting into the weeds. If more open-ended discussion needs to happen, interested parties should either 1) stick around after standup or 2) schedule a new meeting to discuss in greater depth 3…

Why would you do standups on Zoom if you have Slack? Is it because you're running into the 15 person limit and need video (so cannot use huddles)?

Slack huddles have poor ergonomics what with their use of global keyboard shortcuts. I avoid them whenever possible.

Re: Ask HN: How do you ensure everyone on the team is heard on Slack?

#37
post #27

At my place of work, our internal chat rooms (not Slack, but a similar product) are automatically wiped of messages older than two weeks, to actively discourage anyone from using it as a knowledge store. Instead, we have a company-wide BookStack instance that's the primary store of documentation, split into different sections for project information (per project) and rough notes (per employee). Everyone is expected t…

> automatically wiped of messages older than two weeks How do you determine historical truth in a potential conflict scenario, where a manager says "why didn't anybody tell me we'd be running a test at the customer site?" and the engineer says "but I announced it two weeks ago and you even thumbs-upped the post!"?

The same way as 'I've told you that when we ate lunch last week, remember?'. The point is to make sure Slack is treated the same way as a conversation, not as a documentation and project history

Re: Ask HN: How do you ensure everyone on the team is heard on Slack?

#38
post #27

Earlier quoted context omitted.

> automatically wiped of messages older than two weeks How do you determine historical truth in a potential conflict scenario, where a manager says "why didn't anybody tell me we'd be running a test at the customer site?" and the engineer says "but I announced it two weeks ago and you even thumbs-upped the post!"?

The commenter just said slack is not the source of truth in the org. If the post was important, the result should have been documented in the source of truth.

Sure, but the context is that the message wasn't something that the org permanently documents to refer back to, like... an API or a list of deliverables or something. It's just run-of-the-mill workplace interpersonal communications and announcements, like announcing that there's going to be an earthquake drill, or that you're going to be working from home the first week of August. Not documentation. Until a miscommunication occurs and you're suddenly digging for records to piece together how things went wrong.

What communications tool would people use for announcing an earthquake drill? And what does the messaging tool get used for?

Do you send an email to keep the paper trail (with the downsides of email, like that record only being searchable by the people it was sent to at the time)? Or does somebody update the company wiki with records like "2022-07-30: jbay808 absent today due to doctor's appointment"?

Re: Ask HN: How do you ensure everyone on the team is heard on Slack?

#39
post #13

Earlier quoted context omitted.

What's wrong with that? On the real StackOverflow, that's not only allowed but encouraged, and it doesn't seem to cause problems like that.

Perhaps it's a solution that does better at a large scale than at a smaller scale. At a smaller company, it becomes much more evident that the contributions are being made more for self-promotion than for anyone's benefit. Either because you know the person making them and their personality, because the volume:quality is out of alignment, or because the person posting the question/answer wasn't actually having the pr…

Again, what's the issue with that? How is organization suffering from it?

Re: Ask HN: How do you ensure everyone on the team is heard on Slack?

#40
post #13

Earlier quoted context omitted.

What's wrong with that? On the real StackOverflow, that's not only allowed but encouraged, and it doesn't seem to cause problems like that.

Perhaps it's a solution that does better at a large scale than at a smaller scale. At a smaller company, it becomes much more evident that the contributions are being made more for self-promotion than for anyone's benefit. Either because you know the person making them and their personality, because the volume:quality is out of alignment, or because the person posting the question/answer wasn't actually having the pr…

Were their answers wrong, or were the questions completely unnecessary? How do you know it's "not for everyone's benefit"? I don't announce to the world when I consult the documentation. Are you measuring the reach of these answers or is it just a gut feeling?

I really fail to see how this is a negative thing. If anything, it's the people not doing it that caused the whole project to fail.

Post reply on HN