Live data from Hacker News

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

news.ycombinator.com

71–80 of 112 posts

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

#71
A subset of tech community in Japan has established a strange form of "broadcast" yourself in Slack, which is called "minute-updates" channels, that is, each team member creates a channel owned by oneself, posts short updates (or tweets, if you like to think in that way) there, and lets others chime-in freely. So it's a channel for monologues out loud.

This clearly doesn't scale for large orgs, but any communication method doesn't anyway. One clear advantage of this is the low entry barrier: You don't have to worry about interrupting and shutting down the ongoing conversion unintentionally, or spamming others.

Although this barrier lowering seems to be helping a lot in the highly peer-aware environments like Japan. I'm not sure how effective this is in a different context. So take this as a grain of salt.

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

#73

A subset of tech community in Japan has established a strange form of "broadcast" yourself in Slack, which is called "minute-updates" channels, that is, each team member creates a channel owned by oneself, posts short updates (or tweets, if you like to think in that way) there, and lets others chime-in freely. So it's a channel for monologues out loud. This clearly doesn't scale for large orgs, but any communication…

This is interesting, actually. I like it. Thanks for sharing!

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

#74

In previous teams I've worked hard to make sure slack isn't the place for decisions to be made that are any greater than where to go for lunch. Same with bigger questions as well. Slack is great for small insignificant chatter but developers need long uninterrupted periods of quiet to work. That doesn't go well with an IM system that people expect to get big questions answered or key decisions made with. If the team…

> Slack prioritises whoever is first to reply and no one wants to read a 50+ message thread to figure out if they have relevant input. But they want to read a long e-mail thread?

[deleted]

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

#75

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…

Slack stands for Searchable Log of All Conversation and Knowledge - I'm not sure why people don't like to use it to look up information, especially disjointed information not formally recorded elsewhere?

It shouldn't replace tools like BookStack, but nuking it every 2 weeks feels like its losing genuine knowledge too

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

#76

Email is the best method of communication for anything complex. It's asynchronous, long-form, has a historical record, allows threading, you can seamlessly include anyone in the world in the conversation, have shared mailboxes and mailing lists, attach files. But people are afraid of e-mail. Will anyone ever read my e-mail? When will I get a response? What if I mess up my message? It is unknown, immutable, does not p…

Have you ever been CCed into an email thread where 4 people already have been having conversations for days? It's a nightmare. "hello, please check 4 days worth of jibby jabba nonsense and let us include you in this topic with a vague question". And most often, the subject isn't even relevant anymore.

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

#77
My personal opinion is that Slack is a terrible medium for long term info exchange, acronym notwithstanding. I work for a company where we have almost 2 public channels for every full time employee, and that's not counting the private channels, DMs, and so on.

I was on a ski lift last winter with a guy who ran a small company (~20 engineers) who banned Slack and I think he had a strong argument.

Reading through the comments, I see a number of antipatterns emerging from this thread. I'll enumerate some:

* Urgency etiquette: @channel, @here, or just plain message? How about @here with a few personal @ throw in, which is like the gratuitous CC: in email? This depends a lot on your org's topography. I do contract work for a global org, and @channel is almost never appropriate. It's kind of looking at alerts as an SRE: does EVERYONE need to know this?

* Search really is terrible: I know people say "just search Slack". Reminds me of a former colleague who joked about "Google Battleship" (referring to the guessing game of Battleship), where you hunt for the right combination of words. Some questions are just hard to answer via context-free text queries, and this leads to the next point

* Atrophy of other documentation like Wikis and READMEs. The big problem with Wikis is that they have to be gardened - they need dead pages removed, outdated info updated, etc. Slack also needs gardening. The 2 week ban is draconian, but I imagine that in this org, people start moving important information to permanent storage.

* Private channels are unsearchable, as are private conversations. I've personally banned my private conversations. People DM me about comments I've made on a PR, rather than responding in comments or a public channel. I always direct them back to a public comms channel. The idea of Slack is to make communications public and searchable, but people need to enforce that individually. I don't allow DMs except for social BS like lunch plans.

* On the flip side, information-free channels. Some of my channels at work are completely noise - basically all they are is alerts from PagerDuty, or automated build noise, or the #fyi channel for all employees. Anybody who cares about "slack zero" mutes these channels anyway.

* Somewhat related to the last point, the auto-responders. At its simplest, if you have an auto-responder keyed to a single word or phrase, that indicates a problem, not a need for an auto-responder.

* Final point is info fragmentation and overload. You don't know what channel to ask a question in, and you can't keep up with it all. I have a personal keyword filter, but basically in Slack, I've created a personal info silo simply to be able to have a chance to focus on my work.

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

#78
I like slack, but as a medium, it's very easy to talk past each other. email is similar, where I was just on another thread where some more senior people were cc'd on a drill-down between parties and email threads can quickly become a power struggle if the seniormost person doesn't intervene and tell them to take it offline. All conflict is caused by power vacuums, which are in turn caused by gaps in leadership, imo.

Coming out of hacker IRC culture, I can keep up with anyone, but that puts some very thoughtful people, and therefore the team, at a disadvantage to what makes "good chat." I've seen it become a source of drama precisely because a normal team has a lead who sets the tone, but the equalizing nature of chat has the effect where it can both elevate dumb stuff and diminish important stuff, there's a mean reversion where the medium itself becomes the message. When it's good, it's very efficient, but when it's obligatory, it creates simmering rot in teams. It's amazing to have ideas stand on their own - but when it doesn't present the full person with them, the best ideas are no longer neutral - but rather assigned to our preconceptions about a person behind them, without providing them the tools to set tone in a way of relating.

We have to assume good intentions, but in an org, that's mostly performative, and the necessary altruism to sustain that doesn't scale. The reality of ostensibly flat organizations is that they are constant power struggles to extract value from each other (manage others), based on the ficton that the result is somehow organic leadership that produces authentic buy in and consensus. It's not. The necessary condition for value in a low-information medium like text or chat is shared purpose and aligned incentives. You need trust above all, as without it, text amplifies mistrust. The question of what facilitates that trust is the big hard problem. Anonymity and distance provides some trust in informal networks, as the consequences are limited. Text chats I'm on with friends that are absolutely private have trust that originates in friendship. Trust in on a team or in an organization is the fundamental problem to solve. Who can you trust, and for what? A single hub-spoke leader everyone trusts is the baseline, and the ideal is a complete mesh pattern of trust. Without something on that spectrum, your team is default dead. Low trust chat is lame and harmful. The best companies and teams have a relatively high degree of mutual trust as the result of aligned incentives.

When it goes to shit is when we're forced to pretend to trust each other, and then you get institutional bureaucracy politics, which async and text just amplify. I'm in a place where it seems to do it right, but I've been in places where they don't. Slack's message stats in the admin panel are a pretty good proxy metric for organizational trust, where if you see lower engagement, I'd bet just from that you have a trust deficit on your teams that is going to be a ceiling on the value they create.

If you gave me a company's outlook and slack admin panels, I would be able to tell you in a few minutes where your culture bottlenecks were. What people trust can be easily codified as well, but that's a tangent. Where I have seen Slack succeed is where the team has a basis for trust, and where I have seen it fail and become radioactive is where that trust was undermined because of a power vacuum and people defecting to where they think will prevail. Those are hard conversations becuase a lot of managers and employees personalize and moralize their position as being the effect of their identity, where they have internalized the status without a lot of examination of the practised skills it takes to do it well. Slack and email are neutral, but they are also extremely sensitive to deviations from alignment, where interpersonal conflict happens within the vast imaginations of the participants, and not in the real moment of dealing with another person.

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

#79
post #76

Email is the best method of communication for anything complex. It's asynchronous, long-form, has a historical record, allows threading, you can seamlessly include anyone in the world in the conversation, have shared mailboxes and mailing lists, attach files. But people are afraid of e-mail. Will anyone ever read my e-mail? When will I get a response? What if I mess up my message? It is unknown, immutable, does not p…

Have you ever been CCed into an email thread where 4 people already have been having conversations for days? It's a nightmare. "hello, please check 4 days worth of jibby jabba nonsense and let us include you in this topic with a vague question". And most often, the subject isn't even relevant anymore.

I know we all hate meetings, but this is a sign you need a meeting.

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

#80

A subset of tech community in Japan has established a strange form of "broadcast" yourself in Slack, which is called "minute-updates" channels, that is, each team member creates a channel owned by oneself, posts short updates (or tweets, if you like to think in that way) there, and lets others chime-in freely. So it's a channel for monologues out loud. This clearly doesn't scale for large orgs, but any communication…

[deleted]
Post reply on HN