Hi there,

You’re probably doing this and you don’t even realize it…

Clue 1: It has to do with Slack.

Clue 2: It’s likely slowing everyone on your team down.

Clue 3: There’s an easy fix.

Remote Octopus recommends leveraging mirrored language in Slack replies.

Slack is designed to help us work quickly.

But often we end up writing in a stream of consciousness. You’re probably doing this and you don’t even realize it.

While that can theoretically keep us moving faster as we type out our replies, it can dramatically slow down our colleagues. 

Why?

Instead of quickly seeing the answer they requested, they have to slow down and carefully read the stream of consciousness. Somewhere within that stream we’ve likely buried our answer to their question, but it can take time for them to find it especially if we’re using different words than in their original question.

In addition to the slow down, this can lead to unnecessary confusion with back and forth messages to clarify the original question.

Does Jacques answer Mika’s question? Yes technically, but in a confusing way that likely slows down Mika while she is working. Let’s explore why.

Mika references Engineering and Jacques replies about RPET. Mika might or might not know that RPET is a specific team on Engineering. Jacque’s reply also fails to answer her original question on timeline. Mika is trying to figure out if Engineering will return from their off-site tomorrow. Jacques just says they’re in Chicago right now.

This seems like a very specific example – but I guarantee it’s happening all over your Slack threads right now.

🪩 How do you leverage mirrored language to speed up communication?

Simple, use the same words your colleagues use in their question.

It might take you an extra few seconds to ensure you’re incorporating the mirrored language, but it will lead to improved clarity, speed, and accuracy in cross-functional collaboration.

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