Most problems at work start not with a lack of knowledge but with misunderstanding: someone read a task differently, someone missed an important message among a dozen chats, someone mentioned a delay on the very last day. Communicating well is not an innate talent but a soft skill you can learn. In this guide we look at which channel to choose for which situation, how to write clearly and briefly, work chat etiquette, talking to your manager and colleagues, active listening, spoken communication and forms of address, working in a bilingual environment, confirming agreements in writing and handling difficult conversations. Each section has “bad” and “good” message examples, and at the end you will find common mistakes, a practice exercise and a checklist.
Choosing the right channel
You can deliver the same message in different ways, but each channel has its own job. Pick the wrong one and even a simple question becomes a problem: an urgent matter sits in someone’s inbox all day, or a sensitive topic gets discussed in the group chat in front of everyone.
- Face-to-face conversation. For complex, sensitive or emotional matters: a disagreement, explaining a mistake, discussing a new task in detail. Tone of voice and facial expression reduce the risk of misunderstanding.
- Phone call. An urgent issue, or a situation that needs several rounds of questions and answers. Something that takes half an hour in writing can be settled in two minutes on the phone. If it is not urgent, it is polite to message first: “Is it a good time for a quick call?”
- Telegram or a work chat. Short questions, quick agreements, status updates. Chat is fast, but information in it quickly gets buried.
- Email. Formal messages, external partners, documents and reports, agreements you will need a record of later. How to write such emails is covered in detail in our article on email etiquette.
- Meeting. When you need the views of several people and a joint decision. If one message would settle the matter, do not call a meeting. For online meeting etiquette, read our guide to online meetings.
When choosing, ask yourself three questions: how urgent is it? How complex or sensitive is it? Will a written record be needed later? Urgent means a call, sensitive means face to face, formal and on the record means email, short and simple means chat.
Example. Dilshod, an administrator at a training centre in Karshi, discovers one morning that the projector is not working, and the class starts in half an hour. He does not post in the chat and hope the technician sees it; he calls. Once the problem is fixed, he leaves a short message in the chat: “Projector cable replaced, it’s working. We’re out of spare cables, so we need to order more.”
Writing clearly and briefly
The whole thought in one message
The most common chat habit is to write “Hi” and wait for a reply. The recipient does not know what you need, replies, and then waits in turn. Two people’s time is wasted. Put the greeting, the question and the necessary details into a single message.
Bad:
Hello
Are you there?
I wanted to ask something
Good:
Hello Nodira Rustamovna. For table 3 in the October report, should I use September’s figures or the whole quarter? I need to submit it today by 15:00.
Give context
The recipient cannot see inside your head. Instead of “Is the file ready?”, write “Is the draft contract for the Tashkent branch ready?”. A good message answers three questions: what it is about, what you need and by when.
Rules for brevity
- Main point first. Say what you need first and add the details afterwards.
- One message, one topic. If you have three questions, number them: “1) … 2) … 3) …”. The other person can then reply to each by number.
- Precise words. Not “as soon as possible” but “today by 16:00”; not “early” but “Monday morning”.
- Reread before sending. Put yourself in the recipient’s place: knowing nothing else, would you understand the message?
Work chat etiquette
In groups and in private messages
A group chat is read by everyone. Only post there what concerns many people. A question for one colleague or a detailed discussion belongs in a private message. Criticism, reminders about someone’s shortcomings and talk about mistakes never go in the group.
Useful group habits:
- when addressing a specific person, tag them (@name) so they do not miss the message;
- when answering an older message, use Reply so it is clear which question you are responding to;
- pin an important agreement or schedule with Pin Message;
- there is no need to write “OK” or “Thanks” in a group of thirty people; a reaction is enough.
Messaging outside working hours
A message sent late at night or at the weekend makes people feel they must answer straight away. If it is not urgent, leave it until the morning. In Telegram you can press and hold the send button and choose Schedule Message to set a sending time, or Send Without Sound to send it silently. If it really is urgent, say so: “Sorry for writing so late; I urgently need a document for tomorrow’s inspection.”
Voice messages
Voice messages are easy to record but awkward to receive: you cannot play them in a meeting or on public transport, it is hard to find a number or address inside them, and long ones take up time. A voice message is not appropriate:
- in a group chat;
- to your manager or someone you do not know;
- when it contains numbers, dates, addresses or lists;
- when it is longer than a minute.
If typing is difficult (say, you are driving or on site), a short voice message to a close colleague is fine, but send the key numbers and dates as text afterwards.
Stickers and emoji
In a close-knit team a small reaction makes a message warmer. But do not send stickers to your manager, a client or an external partner, and do not use them at all in messages on serious topics such as a mistake, a delay or a complaint.
How long to wait for a reply
Chat does not demand an instant answer. Agree on a norm with your team: for example, replying within a few hours during working time. If you cannot give a full answer straight away, send a short acknowledgement: “Seen it, I’ll reply after lunch.” If you are the one waiting, do not send ”???” a few minutes later; once the agreed time has passed, send a polite reminder.
Communicating with your manager
Reporting progress
Do not wait for your manager to ask how things are going. On a long task, give short interim updates: what is done, what remains, whether there are any risks. The structure is simple:
Bobur Akmalovich, a quick update on the exhibition preparations:
Done: stands ordered, participant list ready.
In progress: handouts, due Thursday.
Risk: the banner supplier isn’t responding; I’ll find an alternative tomorrow.
Bring a problem together with a proposed solution
Instead of “There’s a problem, what should I do?”, think it through first and suggest one or two options. The decision is still your manager’s, but you save their time and show responsibility.
Bad:
The printer’s broken, I can’t print the documents.
Good:
The printer’s broken. I’ve called the technician, who is coming tomorrow. I’ve arranged to print today’s 40 contracts (an illustrative number) in the department next door. Is that all right?
”I’ll find out” instead of “I don’t know”
If your manager asks something and you do not know the answer, do not guess, and do not stop at “I don’t know”. “I can’t say for certain right now; I’ll check with accounts and let you know by 14:00” is an honest and reliable answer. Make sure you come back by the time you promised.
When you are given a task, ask about anything unclear straight away: the deadline, what the result should look like and what takes priority. A minute spent asking is better than two days spent working in the wrong direction.
With colleagues: asking, declining and offering help
Asking for something
A good request is specific and respectful: what you need, why and by when. Acknowledge that your colleague has their own work too.
Bad:
Send me the client database.
Good:
Jasur, could you please send me the list of Samarkand clients? I’m putting together Friday’s call plan. If I have it by tomorrow lunchtime, I’ll be on track. I know you’re busy, so just tell me if it’s difficult.
Declining politely
If you say yes to every request, your own work will slip. Declining is not rude as long as you give a reason and, where possible, offer an alternative: “I can’t today, I have to hand in a report by the evening. I could set aside an hour tomorrow morning; would that work?” Even if your colleague is older than you, you can say it just as respectfully.
Offering help
If you see a colleague struggling, offer specific help. “Let me know if you need anything” is kind, but “Shall I check the second half of the list?” is more useful. Just make sure you have looked at the state of your own tasks first. For other aspects of working together, see our article on teamwork skills.
Spoken communication and active listening
Active listening
Listening is not the same as waiting for your turn to speak. Active listening means giving the other person your full attention, not interrupting and checking that you have understood. It has two main techniques:
- Clarifying questions. “What format do you need the result in, a spreadsheet or a presentation?”, “Which matters more here: speed or completeness?”
- Repeating back to confirm. At the end of the conversation, restate the main point in your own words: “So I’ll prepare the table for the three branches by Wednesday and email it to you, is that right?” If something has been misunderstood, it comes out immediately.
During a conversation, do not look at your phone or do other work on your computer; it signals to the other person that they do not matter.
Tone of voice and body language
The same words can sound completely different in a different tone. Speak calmly, clearly and at a moderate pace. Eye contact, an open posture (arms not folded) and turning towards the other person all show attention. When you feel agitated, do not rush to reply; it is fine to say, “May I think it over and get back to you?”
Forms of address
In Uzbekistan’s workplace culture, the way you address someone is a sign of respect, and people notice it:
- The formal “you”. Both Uzbek and Russian have a formal “you” (“siz” and “vy”), and at work it is used with colleagues, especially older ones or people you have just met. Switching to the informal form with a close colleague of the same age happens only when both sides are happy with it.
- First name and patronymic. Managers and senior colleagues are often addressed by their first name and patronymic: “Bobur Akmalovich”, “Nodira Rustamovna”. See what is customary in your organisation and follow that.
- “Aka” and “opa”. In many teams, adding “aka” (elder brother) or “opa” (elder sister) after a name is a warm and respectful form of address: “Rustam aka”, “Dilfuza opa”. In a formal meeting or in front of a client or external partner, though, the name and patronymic is more appropriate.
- Getting names right. If you are not sure how to pronounce or spell a new colleague’s name, ask. It is not rude; it shows you care.
A bilingual environment
In many workplaces Uzbek and Russian are used side by side. Some helpful rules:
- ask the other person which language they prefer and continue in it;
- write each message in one language, as mixing languages within a sentence makes it harder to follow;
- an important announcement in a group chat can be given in both languages so that everyone understands it;
- agree on terms: are the Uzbek and Russian words for “report” in your team the same document or different ones?
- if someone does not speak the language well, do not laugh at their mistakes; speak more slowly and simply.
Preventing misunderstandings and handling difficult conversations
Confirming agreements in writing
A week after a verbal agreement, everyone remembers it slightly differently. After an important conversation or call, send a short written summary:
Gulnora opa, a quick note of what we agreed today:\
- Parents’ meeting on 18 October at 17:00 (illustrative date).\
- I’ll draft the announcement and you’ll approve it, by Thursday.\
- Sardor will check whether the hall is free.
If I’ve misunderstood anything, please let me know.
That last line gives everyone a chance to spot a misunderstanding early.
Reporting a delay
If you sense you will miss a deadline, say so as soon as you know, not on the last day. The message should give the reason, a new realistic deadline and what you can do right now.
Bad (on the evening of the deadline):
Sorry, I didn’t make it.
Good (two days before):
Bobur Akmalovich, I won’t be able to hand in the analysis report on Friday: the data from the branches arrived late. I’ll send the full version by Monday lunchtime. If I send a short version with the key figures on Friday, would that be enough for you?
Admitting a mistake
Everyone makes mistakes; hiding them is what damages trust. Three steps: briefly say what happened, explain what you are doing to fix the consequences, and say how you will prevent it in future. There is no need for long excuses or blaming others.
Malika, in yesterday’s message I gave the wrong meeting time: it’s 11:00, not 10:00. I’ve also posted a correction in the group. From now on I’ll copy times straight from the calendar.
Talking to a colleague about a mistake in their work is a separate skill. It is covered in detail in our article on giving and receiving feedback.
Common mistakes
- “Hi” and waiting. Write your question straight away, in one message.
- Messages without context. “When will it be ready?” What will, and which project?
- The wrong channel. Urgent matters by email, sensitive ones in the group chat.
- Criticism in the group. Remarks and criticism belong in one-to-one conversations only.
- Long voice messages. Especially with numbers, addresses and lists.
- Leaving messages unanswered. Even if you cannot reply properly yet, write “seen it”.
- Guessing. If you do not know, say “I’ll find out”.
- Reporting a delay on the last day. There is no time left to change plans.
- Not writing down verbal agreements. Later comes the “I never said that” argument.
- Bringing only problems. Go to your manager with at least one possible solution.
Practice exercise and checklist
Try this exercise over the course of one week. It works at a job, on a course or in a volunteer project.
- Reread the last ten work messages on your phone. Which were a lone “Hi”, and which lacked context? Rewrite two of them.
- Before sending each new message, check the three questions: what it is about, what is needed and by when.
- At least once this week, send a written summary after a conversation or call and end it with “If I’ve misunderstood anything, please let me know.”
- When given a task, ask at least one clarifying question and repeat the task back in your own words.
- Take one problem to your manager together with two possible solutions.
- Use Schedule Message to delay until morning a message you were about to send in the evening or at the weekend.
- At the end of the week, write down which habit was hard and which one paid off.
Checklist before sending a message
- The channel is right: urgent means a call, sensitive means face to face, formal means email.
- Greeting, question and context are in one message.
- The deadline is precise: date and time.
- The form of address suits the person.
- Only things that concern everyone go in the group.
- Text instead of a voice message, especially when there are numbers.
- Important agreements are confirmed in writing.
- Delays and mistakes are reported straight away, with a proposed solution.
Workplace communication is made up of small habits repeated every day. One clear message, one timely “I’m running late” and one written-down agreement go a long way towards building trust in a team.
If you would like to develop your professional skills systematically, take a look at our association’s free training programmes. When you are ready, submit an application and our specialists will get in touch.