4 ms·
> They keep an eye out for anything that Sam or Pat might want to know about, and check in to make sure that Sam or Pat is keeping an eye on it. This is miser
by PragmaticPulp 6y ago
> They keep an eye out for anything that Sam or Pat might want to know about, and check in to make sure that Sam or Pat is keeping an eye on it.
This is miserable for everyone. Don't make Slack the center of your workflow. Don't let spontaneous Slack chats dictate your process.
The manager's job shouldn't be to scour Slack for information and then ping every person who might need to participate in or read each conversation. That just amplifies the noise. It's terrible to be deliberately ignoring Slack for 30 minutes to focus on work, only to have your manager ping you back into Slack to make sure you don't miss something.
Instead, the manager should be forcing important conversations to happen outside of spontaneous Slack conversations. If something important is decided in Slack, the decision needs to be recorded in the tracking ticket, Wiki, or other important location. If it changes anyone's active work, they should be interrupted. Otherwise, they can pick up the information from the single source of record (ticket, wiki, etc.) rather than being expected to follow every detail of Slack all day.
Small groups working on tasks together should have private PMs or channels to discuss implementation details, not giant Slack channels with 10s or 100s of members.
A good manager will avoid design by committee and will stay ahead of the spontaneous Slack firehose by arranging planning sessions and scheduled meetings where necessary.
Don't let the Slack chaos drive your workflow. Don't try to make managing Slack someone's job. Manage the workflow first, deliberately rather than reactively. If important conversations are happening spontaneously in Slack too often, that's a sign that you need to fix your workflow.
- mumblemumble 6y agoSorry, allow me to rephrase. I didn't meant that the manager's job is to dogpile everyone onto every issue. It was to make sure that work is being judiciously assigned to the right people, and everyone else is getting progress updates as needed. My working hypothesis here is that, when there is someone that the team trusts to do that, it will ultimately reduce the level of overcommunication and design-by-committee. Everyone feels more comfortable focusing on their immediate work, and limiting their active participation in things that don't require their active participation, because they know they'll get the memo.
- PragmaticPulp 6y agoIt doesn't matter much if the manager dispatches the pings ASAP or buffers them up for later. You're still letting Slack chaos drive your process instead of leading with process and using Slack as a tool. In some ways, having the manager buffer up the pings is even worse, because then each person has to revive the topic again if they want to have a voice. People don't want to be left out of important conversations, so the only solution is to watch Slack like a hawk all day. The people who spend all day in Slack instead of doing work end up dominating the decision making while the people who focus on work suffer. Instead, don't hesitate to gather people for a scheduled call after lunch, at the end of the day, or first thing tomorrow morning to clear it up. Record important decisions in a single source of truth that isn't Slack, like your Wiki or ticket tracker. Treat Slack almost like you would in-office conversations: If you have a spontaneous watercooler conversation about an important topic in-person, you wouldn't go gather everyone involved to come to the watercooler to continue the conversation. You'd send out an e-mail update to others who need to know. Or you'd scheduled a follow-up call or meeting to discuss it. The in-person rules of communication and avoiding interruption are a good template for how to behave in Slack.
- gadabout 6y agoYou keep assuming that the manager is only delegating via Slack pings, which is not my experience at all and also not what mumblemumble specified. The best managers know what the appropriate communication channel is for their employees and the issue at hand, and I don't think any strong managers are going to point to Slack pings at their preferred method.
- ticmasta 6y ago>> scheduled call after lunch, at the end of the day, or first thing tomorrow morning This sounds great in theory, but one of the key issues with managing remote teams is there is no common time in the day that is "after lunch, end of day or first thing in the morning". The reality is most remote scenarios require you adopt at least some async process; fighting this is a losing battle. Some good news: your manager's job was always facilitate internally and protect externally; how this is accomplished has certainly changed but the core essence of management, if anything, is even more crystallized now.
- lukethomas 6y agoMost workplace communication tools are focused on improving the efficiency of communication. I think of this as laying "pipes". It's never been easier to jump on a video call or ping someone in Slack or email. What happens is that the information/communication doesn't flow on a repeatable or predictable basis. What people really need when remote is a way to help create and automate a series of communication habits/workflows, so instead of hunting around or perusing Slack to understand what's going on, the information flows to you. Like a series of communication pumps. Right now, most managers manually collect this, which is an epic waste of time. Self plug, but after 8 years working remotely and constantly running into the workplace chat firehose, I've built software to help automate any routine update at work (https://www.friday.app https://www.friday.app).
- SkyMarshal 6y agoOr just don't use Slack. Use something like Zulip that is deliberately designed to convert synchronous chat streams into asynchronous communications: https://zulip.com/#tour-carousel https://zulip.com/#tour-carousel
- bfuclusion 6y agoRight. Dispatching work with slack is like trying to command an army via town crier. Not a great experience.
- arbitrary_name 6y ago>A good manager will avoid design by committee and will stay ahead of the spontaneous Slack firehose by arranging planning sessions and scheduled meetings where necessary A great point. They will ideally also have enough context, experience and intuition to 'individualize' comms - providing detail from an earlier briefing to the ux person while omitting the unnecessary technical details that are more relevant to the other team mate who is working on a security feature. As a team lead, I do subject myself to a bit of a firehose outside my immediate team in the hopes of stumbling across little nuggets of useful info and context, but if I orchestrate communications within my org well enough, that's the only time it occurs.
- ViViDboarder 6y agoWell said. It comes down to structuring some type of process for facilitating communication rather than being reactionary. Spontaneous conversations are going to happen and should be encouraged, but Slack is not a platform for documenting a decision or conversation. If for no other reason than it’s not concise. Coming back and trying to parse an hour long slack convo is a waste of time when it can likely be boiled down to a one paragraph summary. If something interesting happens I find it helpful to take that opportunity to get the gist or decision documented in a ticket or wiki page somewhere for easier dissemination and for centralizing further communication and decisions related to the topic.