How it differs from talking
In conversation, a question and its answer take a minute. In messages between people who work at different times, a day.
Hence the main rule: every message must stand on its own. The reader can't ask a follow-up immediately, so everything must be there already.
This applies especially to teams where people work evenings after their day job — which is nearly every team project.
Asking so you get an answer in one round
Bad:
Hi, got a minute?
The reply arrives six hours later and says "yes, what's up?". Another six hours to the point.
Bad:
Saving doesn't work, what should I do?
What exactly doesn't work, what you've tried, what the error is — nothing. Your colleague asks three clarifying questions, half a day each.
Good:
Saving an expense gives me this error. I've tried: checked the field is filled in, looked at the log entries and I see this. I suspect it's the date format. Am I right, and if so, where's the best place to convert it?
Your colleague answers once and the question is closed.
The template: what I'm doing → what happens → what I've tried → what I suspect → a specific question.
What belongs in the group chat
Decisions. "We've agreed to store dates in this form." Otherwise nobody remembers in a month.
Readiness. "The form is deployed, take a look."
Obstacles. "Stuck on this, ideas welcome."
Changed plans. "I won't make Saturday, it'll be Tuesday."
What doesn't
Ten-message debates. If a topic needs arguing, get on a fifteen-minute call. An hour of messaging is often replaced by ten minutes of talking.
Personal criticism. Grievances about a person go privately, always.
"Good morning" as its own message. Every message is a notification for everyone. Write it as one block.
About response-time expectations
Agree in advance: within a day is normal, urgent things get flagged.
Without that agreement, half the team frets about two hours of silence and the other half doesn't know what's wanted from them.
And acknowledge the obvious out loud: everyone has a day job or studies. An answer in the evening is a normal answer, not a sign of disinterest.
What helps
Writing up outcomes. After a call, three lines in the chat about what was decided. Otherwise the decision exists only in two people's memories.
Keeping status visible. A task board removes half the "so what's happening with…?" messages.
Replying at least briefly. "Seen it, I'll look tomorrow" beats silence: the sender knows it arrived.
These habits are exactly what remote work demands. They're practised for free, on your own project, and such experience is worth more on a CV than it looks.
Открытые роли по теме статьи
Читать полезно, а делать — ещё полезнее. В эти команды можно написать прямо сейчас:
- iOS-разработчик — MAIBO - MedTech-пилот для клиник
- Контент-маркетолог / комьюнити — CohortX — платформа командных пет-проектовмаркетингtelegramseoконтент
Похожие статьи
- Study Tools Season: two weeks, a team, and a finished projectCohortX launches its first season: September 7–21, teams of 2–4 build one study tool each — from schedules to progress trackers. How to join and what it adds to your portfolio.
- Сезон инструментов для учёбы: две недели, команда и законченный проектCohortX запускает первый сезон: с 7 по 21 сентября команды по 2–4 человека делают по одному инструменту для учёбы — от расписания до трекера прогресса. Как участвовать и что это даёт портфолио.
- Dividing roles in a small teamWhy splitting by layers is risky, three workable ways to divide the work, and what to do when everyone wants the same part.