51–60 of 112 posts
Earlier quoted context omitted.
Slack huddles have poor ergonomics what with their use of global keyboard shortcuts. I avoid them whenever possible.
Have you tried async standups via something like Geekbot? https://geekbot.com/
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!"?
You need to establish some rules to make Slack work for most teams without overload. 1) People should avoid DMing each other when talking about work, use threads instead (see 3) to discuss topics in team channels (see 2). 2) Keep channels to a minimum. Every person shouldn't have more than 2/3 channels they need to pay attention to. A private team communication channel (eg #dream-team) and a private work channel (eg…
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…
Or it's being wiped because your leadership team doesn't want anything shady uncovered in discovery or a warrant and "we do it to discourage anyone from using it as a knowledge store" is how it's being sold to everyone else.
Earlier quoted context omitted.
Slack huddles have poor ergonomics what with their use of global keyboard shortcuts. I avoid them whenever possible.
Have you tried async standups via something like Geekbot? https://geekbot.com/
It is great for communicating around an event. Getting quick in-flow queries answered. Asking what people want to do for lunch.
It is not for substantial nuanced in depth communication. When used this way it quickly becomes a conveyor belt of distracting trash.
It is also not a knowledge repository or source of truth. Slack overflow is not a good practice.
Pro tip: have slack history clear after 60 days.
Better alternatives: - Shared Google Doc with comments for analyzing an issue - Meetings with a pre-read period and memo and clear purpose/outcome for the meeting - Pair programming - Live code review
TL;DR Dont use slack.
You need to establish some rules to make Slack work for most teams without overload. 1) People should avoid DMing each other when talking about work, use threads instead (see 3) to discuss topics in team channels (see 2). 2) Keep channels to a minimum. Every person shouldn't have more than 2/3 channels they need to pay attention to. A private team communication channel (eg #dream-team) and a private work channel (eg…
Instead, what's done is done, and it can lead to rapid degradation in communal rooms that have a lot of newcomers.
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!"?
By not having a culture where people need historical records to cover their ass.
If for some reason you need an auditable record of your chats thats fine but decisions should hopefully be documented elsewhere and linked into the thread/convo.