Hi there,

When you’re making plans with friends, do you say: Let’s meet in New York City tomorrow?

Probably not. 

NYC has 5 boroughs. It’s over 300 square miles. It has over 1 million buildings. (Plus you might not live anywhere near NYC.)

Your friends would have no idea where to go – which of the 1 million buildings are we supposed to meet at? 

Kind of sounds like our company’s Slack 😂

P.S. Based on last year’s email engagement metrics, we’ll be slowing down a bit in July + August to an every other week cadence. See you again on Thursday 7/10!

Remote Octopus recommends ensuring you are communicating updates in clearly specified Slack channels or threads.

We wouldn’t just tell our friends to meet us in NYC so we should also avoid telling our colleagues to drop that update in Slack.

The question becomes: BUT WHERE?!

Both NYC and our company’s Slack have what feel like limitless options. It’s so easy to get turned around. Channels, DMs, threads – the same conversation can be going on across multiple locations.

If you are on a team call and need an update from a colleague in Slack, clearly specify which Slack channel or thread they should provide the update. If they’re providing a critical update or unblocking a team, encourage them to over-communicate and post in 2-3 places if needed.

By clearly communicating where to put an update, we’re ensuring everyone on the team stays on the same page. Work moves forward quickly. 

😵‍💫 What happens if we don’t specify? If we say just drop that in Slack? Often that update might end up in a 1:1 DM or a private channel – somewhere the rest of the team has no idea it’s been posted. The team stays blocked. No one realizes the update is resolved. Lost time.

When leading a project, clearly specify where your colleagues should drop their Slack updates. Then clearly specify that your friends should meet you at Radio Bakery in NYC (it’s truly the best).

Ready to level up operational excellence for your team? Check out our resources: