TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Collaborate with kindness: Etiquette tips in Slack

99 点作者 sendilkumarn大约 3 年前

23 条评论

kerblang大约 3 年前
&gt; Default to public channels for better workplace communication<p>I have tried so hard to get people to do this, but it seems like a lot of my coworkers are honestly scared of &quot;public&quot; channels, and by &quot;public&quot; I mean a channel with only 15 or so people on it. They insist on DM&#x27;ing most things, and some just refuse to use chat at all; those will only communicate via email.
评论 #30836165 未加载
评论 #30838793 未加载
评论 #30840202 未加载
joseph8th大约 3 年前
At risk of repeating what everyone else has said... My PM does the &quot;Hey&quot; thing. I do not multitask. I&#x27;m a serial tasker.<p>So I turned off all notifications on Slack. The only way I know I have a message is the red dot that appears in the panel icon.<p>Now, it&#x27;s async again. When I even glance up to see if there are new messages... Red dot or no red dot
评论 #30840698 未加载
评论 #30840331 未加载
评论 #30842987 未加载
评论 #30842291 未加载
donatj大约 3 年前
&gt; Use threads for effective team collaboration. Seriously.<p>Threads are where messages go to die. I don’t have time to read every single thread clicking into it individually. You’re just making work for me, having to figure out what threads I have to read. If it’s in a thread and no one @‘d me, assume I missed it. I read very quickly, I just want to be able to scan all messages in a channel chronologically.<p>My team begrudgingly moved over from an IRC server about two years ago to the larger corporations Slack and have actively avoided threads in our spaces.<p>What they should add is an optional unrolled thread view where people can use threads but we can still get the whole thing as a single non-hierarchical timeline I can just scroll, akin to how Signal does replying to specific messages.
评论 #30841220 未加载
评论 #30841158 未加载
评论 #30842994 未加载
ryanschneider大约 3 年前
My number one Slack tip is to use the All Unreads view (which for some reason needs to be enabled in preferences).<p>Bonus tip: it’s not available on mobile which means I now basically never check Slack from my phone. I can’t decide if the Slack devs are hopelessly overworked or genius for _still_ not offering it on mobile. Check the time stamp: <a href="https:&#x2F;&#x2F;twitter.com&#x2F;slackhq&#x2F;status&#x2F;798631873911980032" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;slackhq&#x2F;status&#x2F;798631873911980032</a>
27182818284大约 3 年前
&gt; Never send a direct message that just says “hey” or “hello.”<p>The corner of the page: &quot;Hey friend, got a minute to chat&quot;<p>ha!
评论 #30840353 未加载
commandlinefan大约 3 年前
&gt; Never send a direct message that just says “hey” or “hello.”<p>I first started hearing people suggest this recently (within the past month or so). I never really understood why these message bothered people so much - they never bothered me and always actually seemed a bit more polite than just barreling forward with a question. But I guess if even Slack themselves are saying don&#x27;t do that, it must really get on other people&#x27;s nerves.
评论 #30835609 未加载
评论 #30835552 未加载
评论 #30835576 未加载
评论 #30836053 未加载
评论 #30835652 未加载
评论 #30836172 未加载
评论 #30835919 未加载
评论 #30839446 未加载
评论 #30835600 未加载
评论 #30836081 未加载
评论 #30850990 未加载
评论 #30836712 未加载
评论 #30836292 未加载
评论 #30840357 未加载
评论 #30848419 未加载
评论 #30841525 未加载
评论 #30839876 未加载
multiplegeorges大约 3 年前
&gt; Less messages means more efficient collaboration<p>I think this should be &quot;Fewer messages...&quot;. Good grammar improves communication, as well.
评论 #30839131 未加载
评论 #30840363 未加载
kome大约 3 年前
Collaborate with kindness: Etiquette tips in Slack: use email.<p>- &quot;1. Never send a direct message that just says “hey” or “hello.&quot;, write longer messages -&gt; use email.<p>- &quot;2. &quot;Write longer messages that scan quickly&quot; -&gt; don&#x27;t use a chat app for your messages, use email.<p>- &quot;3. Use threads for effective team collaboration. Seriously.&quot; -&gt; use a mailing list.<p>- &quot;4. Replace short follow-up messages with emoji reactions&quot; -&gt; don&#x27;t do anything when it&#x27;s not needed.<p>- &quot;5. Reduce off-hours pings with Do Not Disturb&quot; -&gt; set up a mail responder.<p>etc etc
评论 #30839734 未加载
评论 #30840253 未加载
maccard大约 3 年前
&gt; Write longer messages that scan quickly<p>I like this one. I&#x27;m an emoji fan, but understand that not everyone else is.<p>It boils down to &quot;spend time crafting a message that contains the correct information&quot; or even more succinctly &quot;respect other people&#x27;s time&quot;.<p>There&#x27;s nothing worse than a giant wall of text with all the pertinent information buried in the middle of it.
评论 #30838937 未加载
ss108大约 3 年前
The suggestion to use emojis gratuitously and frivolously to break up text is a joke right? Meant to go in an April 1 blog post? Those kinds of messages&#x2F;posts strike me as parodic and obnoxious.
评论 #30842620 未加载
hamolton大约 3 年前
Agree with these takes. My company&#x27;s system having the channel #eng-&lt;team name&gt;-lobby as a q&#x2F;a forum for all teams has been incredible for spreading information, although I could imagine some cultures where it wouldn&#x27;t work as well. The emojis they have for &quot;Thank you&quot; and &quot;I&#x27;m looking into it&quot; seem a bit ambiguous; my company has several &quot;thank you&quot; emotes, but nothing dedicated to the latter. Not sure what we should add.
评论 #30836004 未加载
kyleblarson大约 3 年前
Another tip that vastly improves mental health as well as efficiency: turn off all notifications from slack, especially that damn broom sound.
评论 #30840903 未加载
jawns大约 3 年前
Most important Slack etiquette ...<p>Don&#x27;t @channel large channels after hours!
评论 #30836264 未加载
评论 #30835557 未加载
评论 #30835633 未加载
评论 #30840649 未加载
评论 #30861109 未加载
abridgett大约 3 年前
Some of these are pasting over product weaknesses: - inability to change private channels to public &quot;as you might accidentally reveal secret info&quot;. Yes, but that&#x27;s _my_ decision, not Slacks. - more than 1 or 2 active threads&#x2F;channels is extremely painful and very easy to lose your way - whilst search is good, finding a thread from just a day or so ago can be very difficult (especially when there are many channels) - abuse of @here, @channel - this only seems controllable at a workspace or org level, not a per-channel level.<p>Yes, email and ticket systems have drawbacks, however slack is almost an anti-knowledge base in it&#x27;s current state.
评论 #30840955 未加载
nxpnsv大约 3 年前
It sure would be nice if I could drag replies that went out of thread into a thread...
_moof大约 3 年前
<i>&gt; …the recipient gets a notification on that first “hey” that contains no information and potentially causes distraction. The person might see the indicator that you’re typing but is still left waiting for your full message.</i><p>I would turn this around and call this a product design problem. Maybe Slack shouldn&#x27;t send a notification when all you&#x27;ve said is &quot;hey&quot; and you&#x27;re typing a follow-up message.<p>Really, if you have to publish a blog post explaining to people that they&#x27;re using your product wrong, I&#x27;d say your product needs work.
评论 #30839764 未加载
评论 #30836271 未加载
npunt大约 3 年前
Rather than just tell &#x2F; hope people follow some etiquette, I&#x27;d love Slack to build more etiquette enforcing features that operators could enable.<p>This isn&#x27;t the 19th century where the best we can do is tell people to read a book on etiquette and hope for the best. Slack is in a unique position in the history of interpersonal communication where they have complete insight into (and design of) user&#x27;s and organization&#x27;s preferences as well as the messages themselves. And the medium is text, which is the easiest to analyze and provide feedback on.<p>Some examples of what they could do, broadly captured in a &#x27;Etiquette Features&#x27; preference set by the organization:<p>1. Never say &#x27;hey&#x27; - if a user writes this, explain the etiquette and rationale for it and suggest they write a whole ass message instead, but optionally let the user just send it.<p>2. Make long messages scan easily - not too difficult for a computer to tell a long block of unformatted text. Great time to introduce the etiquette scaffold.<p>3. Use threads - a trickier one to suggest when people are typing, but likely some obvious response patterns (who &amp; when messages are sent) that could trigger a etiquette scaffold asking to put this message in the thread if messages are similar enough to the thread&#x27;s contents.<p>4. Short followups as emojis - orgs should be able to define clear meaning of response emojis that are visualized to everyone in the UI when selecting them (check means complete, question mark means need more info, etc). Short responses also likely have a pattern that could trigger a &#x27;do you mean &#x27;this is done&#x27;?&#x27; kind of scaffold, which would fill in emoji instead<p>6. Channel response expectations - a tiny text label is insufficient to set expectations, as are pinned messages. At the very least visualize timezones of participants, and when writing an @message to someone in a channel, if they&#x27;re off-hours let the sender know that up front.<p>All our communications tools favor low friction to send and devalue the recipients time (the phenomenon mentioned in Cal Newport&#x27;s Deep Work), and Slack is a serious offender. There&#x27;s a need for a higher friction, higher awareness path to send messages that better accounts for the full cost of such messages. Not every org would want&#x2F;need this but it should absolutely be something a service like Slack offers.
评论 #30835989 未加载
评论 #30836284 未加载
Dave3of5大约 3 年前
<a href="https:&#x2F;&#x2F;nohello.net&#x2F;en&#x2F;" rel="nofollow">https:&#x2F;&#x2F;nohello.net&#x2F;en&#x2F;</a>
renewiltord大约 3 年前
Great tips. I think a reference is good for people who won&#x27;t do things unless they have an authority to tell them.
Qem大约 3 年前
The etiquette tip I&#x27;d like to see adopted for most collaboration software is: &quot;Don&#x27;t be the cam psychopath!&quot;. By cam psychopath I mean, people that are constantly pestering and complaining about their subordinates&#x2F;colleagues that don&#x27;t like to keep their cam open in meetings.
orf大约 3 年前
hi, can I leave a comment?
enriquto大约 3 年前
Basic etiquette would be to not force co-workers to use Slack at all. And for that matter, any other proprietary network based on closed standards that do not admit connections from third-party clients. I&#x27;m forced to use Slack and Zoom from time to time for important work stuff, and it is extremely annoying and humiliating.
评论 #30835543 未加载
评论 #30835731 未加载
kkfx大约 3 年前
Being polite and cooperative it&#x27;s a good thing, self-censorship is not and the least one who can write an &quot;etiquette&quot; is a proprietary platform. Sorry that&#x27;s just a pathetic bland and casual push toward Chinese social score homogenization.<p>Usenet netiquette, mail netiquette etc are not wrote by someone up front but slowly formed by a community of users out of their experience. My own personal etiquette for Slack is: &quot;sorry I do not use proprietary platforms, seen no reason for them, we have emails, chats, etc choosing a deliberate security risk is not a good policy for a company, as a sysadmin I can&#x27;t take responsibility for it and so I can&#x27;t even use it&quot;.
评论 #30851060 未加载