A Two-Word Slack Message Almost Cost Me a Client
"Sounds good." That's all I wrote. Two words that, in my head, meant "I love this direction, let's do it." What my client read? Cold dismissal. Possibly even sarcasm. She spent the weekend convinced I hated her proposal. We almost lost the project over two words.
This is the thing about remote communication that nobody warns you about. All those little cues we rely on. Facial expressions, tone of voice, the ability to immediately say "wait, that came out wrong". They're gone. What's left is text on a screen, and people fill in the blanks with their own assumptions. Usually the worst ones.
I've watched time zone delays turn small misunderstandings into week-long conflicts. Seen perfectly reasonable feedback interpreted as personal attacks. The good news? Most of this is preventable. Here's what I've learned actually works.
Common Causes
Assumed context. Thinking others know what you know.
Tone ambiguity. Text lacking emotional cues.
Information gaps. Not seeing the full picture.
Async delays. Time between message and response allows misunderstandings to compound.
Cultural differences. Different communication norms and expectations.
Channel confusion. Important messages lost in the wrong medium.
Over-Communicate by Default
In remote work, err on the side of too much information rather than too little. What feels redundant to you might be essential context for the recipient.
Share Context Generously
Don't just share the what. Share the why.
Bad: "We need to change the deadline."
Good: "We need to push the deadline to March 15th because the vendor delayed their API update. This gives us two weeks to integrate and test once it's available."
State the Obvious
What's obvious to you isn't obvious to everyone.
Spell out acronyms the first time. Link to relevant documents. Explain decisions even if they seem self-evident. Provide background even if you think they know it.
Repeat Key Points
Important messages deserve repetition.
Summarize at the end of long messages. Follow up verbal agreements with written confirmation. Reference previous discussions when building on them.
Tone and Intent
Without facial expressions and voice inflection, tone gets lost. What you mean as friendly efficiency might read as cold dismissal.
Add Warmth Indicators
Small additions signal friendly intent. Greetings and sign-offs, even brief ones. Acknowledgment of their work or perspective. Exclamation points used sparingly to show enthusiasm. Emoji where appropriate for your culture.
State Your Intent
When the message could be misread, make your intent explicit.
"I'm asking because I want to help, not criticize."
"This is just a thought, not a criticism of the current approach."
"I'm pushing back here because I think we can do even better."
The Re-Read Test
Before sending important messages, read them as if you're the recipient in a bad mood. Does it sound harsh? Add warmth. Is the ask unclear? Clarify.
Use Video
Text is efficient but low-bandwidth for emotional content. Some conversations need faces and voices.
Use Video For
Complex explanations. When text would require multiple back-and-forths.
Sensitive topics. Feedback, concerns, disagreements.
Relationship building. Getting to know teammates.
Brainstorming. When real-time energy helps creativity.
Clarifying confusion. When async has gone in circles.
Video Messages as Middle Ground
Tools like Loom let you record video messages that recipients watch on their own time. You get the richness of video without requiring simultaneous availability.
Use video messages for detailed explanations with screen sharing. Feedback that needs tone context. Complex updates that would be walls of text.
Confirm Understanding
Assuming understanding is how miscommunication compounds. Build confirmation into your communication habits.
Ask for Summaries
After important discussions, ask the other person to summarize.
"Can you recap your understanding of the next steps?"
"What are you taking away from this conversation?"
"Just to make sure we're aligned, what's your plan from here?"
Provide Summaries
After receiving information, confirm your understanding.
"Let me make sure I understand: you need X by Y, correct?"
"So the decision is to proceed with option B, is that right?"
Document Agreements
After verbal conversations, follow up with written summary.
"Following up on our call, here's what we agreed to..."
Email or Slack summary with key decisions and action items. Shared document for complex multi-part agreements.
Shared Language
Teams develop their own vocabulary and assumptions. Make these explicit so everyone's on the same page.
Define Terms
Create a team glossary for project-specific terminology. Acronyms and abbreviations. Role titles and responsibilities. Status indicators. What does "almost done" actually mean?
Establish Communication Norms
Document team agreements on response times. What's expected for different channels. Urgency signals. How to indicate something needs fast response. Channel purposes. What goes where, Slack versus email versus docs. Meeting culture. Cameras, agendas, note-taking. Availability indicators. Status meanings, calendar etiquette.
Onboard New Members Explicitly
New team members can't absorb culture by osmosis. Document norms and walk through them during onboarding.
When to Call
Sometimes text isn't working. Recognize when to switch to real-time conversation.
Signs You Need a Call
Multiple back-and-forths. If you've gone more than 3-4 exchanges, a quick call often resolves faster.
Rising tension. Messages getting shorter, more pointed, or defensive.
Confusion persisting. Explanations aren't landing.
Emotion involved. Someone seems upset or frustrated.
High stakes. Important decisions where nuance matters.
How to Suggest a Call
Frame it positively.
"This might be easier to hash out on a quick call, do you have 10 minutes?"
"I want to make sure I understand your perspective, can we jump on video?"
"Text is getting tangled, let's talk through this live."
After the Call
Follow up synchronous conversations with written documentation. Summarize what was discussed and decided. Confirm action items and owners. Share with others who need to know.
Frequently Asked Questions
Strategies to confirm understanding. Ask for confirmation: "Can you summarize your understanding of the next steps?" Request acknowledgment: "Please reply to confirm you got this." Check in later. Follow up before deadlines to catch misalignment early. Watch for questions. No questions sometimes means the message wasn't fully read.
For important communications, explicit confirmation beats assumptions.
Critical feedback needs extra care without in-person cues. Use video. Tone and facial expressions prevent misreading. Lead with intent: "I'm sharing this because I want to help you succeed." Be specific. Concrete examples, not general impressions. Focus forward. What to do differently, not just what went wrong. Allow response. Give space for their perspective.
Written feedback works for minor points. Video is better for anything significant.
Before reacting, pause. Wait at least an hour before responding. Assume good intent. Written messages often sound harsher than intended. Seek clarity. Ask what they meant before assuming. Move to video. If confused about tone, suggest a quick call.
Most upsetting messages are unintentional. A quick clarifying conversation usually resolves things.
Techniques for clearer writing. Front-load the point. Key message in the first sentence. Use structure. Bullet points, numbered lists, headers. Define terms. Don't assume shared vocabulary. Include context. Why you're asking, what you'll do with the answer. State the ask explicitly. What you need, from whom, by when. Read it aloud. Catches awkward phrasing and unclear sentences.
Patterns suggest a systemic issue. Check your communication. Are you being as clear as you think? Ask for feedback: "I notice we've had some miscommunications, what could I do differently?" Try different formats. Maybe they process video better than text, or vice versa. Document agreements. Written records of what was decided. More frequent check-ins. Catch misalignments earlier.
Address patterns directly rather than letting frustration build.
Cultural differences affect communication styles. Learn preferences. Some cultures are more direct, others more indirect. Be explicit. Don't rely on hints or implications. Confirm understanding. Especially for important messages. Ask questions: "How would you prefer I communicate this?" Be patient. Non-native speakers may need more time.
When in doubt, over-communicate and verify understanding.
Wrap Up
Remote work demands intentional communication. What happens naturally in an office, reading body language, overhearing context, clarifying in real-time, must be deliberately recreated.
The key principles:
Over-communicate. More context is better than less.
Mind tone. Add warmth to prevent misreading.
Use video strategically. Some conversations need faces.
Confirm understanding. Don't assume alignment.
Build shared norms. Explicit agreements beat implicit assumptions.
Know when to call. Text isn't always the answer.
Miscommunication will still happen. It's inevitable when humans interact. But with these practices, you'll catch misunderstandings earlier, resolve them faster, and build the trust that makes remote collaboration work.
