Business Communication Guide for Email, Meetings, Presentations and Negotiation

Work email gets skimmed. A busy recipient usually reads the subject line and the first two sentences, then decides whether to reply now, reply later or simply file it. That is why email practice begins in exactly those two places. Learners train themselves to fit three things into the first sentence: what the message is about, what they need from the reader, and by when. Background, context and notes about attachments come afterwards, and only as much as the reader needs.

Subject lines are treated as summaries that work on their own. A subject such as Report or Update forces the reader to open the email to find out what it wants. Something like Approval needed for exhibition budget by Thursday already gives the topic, the action and the deadline. Learners also practise keeping to one topic per email. A message carrying three requests tends to get an answer to one of them, while the other two sink somewhere in the thread.

The material comes from the learner's own sent folder. Ten emails that have already gone out are rewritten using the point, request and deadline pattern, and the old and new versions are laid side by side. In most cases more gets cut than added: stacked greetings, apologies nobody needed, and sentences that repeat what the attachment already says. The tidied versions are kept as templates for situations that come round again, such as chasing data, reminding someone of a deadline or confirming a meeting time.

Office chat runs on different rules from email. Messages are short, they arrive in bursts, and they are often read on a phone in the middle of something else. The habit that comes up most is the split message: hello on one line, the person's name on the next, and the actual question a few minutes later. The reader gets four notifications for a single question. Learners practise sending one complete message that holds a brief greeting, the question and whatever context is needed to answer it.

Group chats bring another problem, because important messages get buried under casual conversation. Practice covers tagging the person who needs to act, replying by quoting the message being referred to, and condensing a long discussion into one message that records the decision. Learners also work on choosing the channel. A quick question suits chat, an approval that needs a paper trail is safer by email, and a disagreement that is starting to heat up usually goes better on a short call.

Reply etiquette is part of the work too, including how to signal that a message has arrived and is being handled when the full answer is not ready yet. A single line such as received, I will send the result this afternoon saves the sender from waiting in silence. The practice material comes from the learner's real work conversations, with names and sensitive figures masked first, and is rewritten with the tutor until the new pattern feels natural.

Meetings put workplace communication under pressure, since several people need to talk within limited time. Preparation starts with a written agenda that answers three questions: why the meeting is happening, which points will be covered, and what decision should exist at the end. The agenda goes out beforehand so people arrive having read the material. Learners practise writing short agendas, three to five items with a rough time allowance for each.

When chairing, learners practise opening with the purpose, sharing speaking turns fairly and bringing the conversation back when it wanders. Steering phrases are rehearsed in simulation, for example parking an off-topic issue on a separate list to be picked up in another meeting. Learners who mostly attend as participants train the opposite side: giving their view in two or three sentences, stating their position up front and backing it with the single strongest reason.

A meeting closes by reading back three things: the decisions made, who owns each follow-up and the deadlines. These are written up as brief minutes and sent the same day. Good minutes can be read in one minute by someone who missed the meeting. In sessions, practice uses a real meeting from that week: the learner drafts the agenda beforehand, then brings the minutes to the next session to review with the tutor.

Negotiation happens far more often than people notice: asking for a raise, requesting a deadline extension, agreeing prices with a supplier, or splitting workload between teams. Much of how the conversation goes is settled before it starts. Learners practise writing down three things in advance: the outcome they want, the lowest point they could still accept, and the reasons that support their request.

A fourth element is often forgotten, namely what happens if no deal is reached. Negotiation literature calls this the BATNA, the best alternative to a negotiated agreement. A business owner with two possible suppliers, for instance, can bargain far more calmly than one with a single option. Knowing their own fallback helps learners judge when an offer is worth taking and when it is better to pause. Practice also includes reading the other side's interests, meaning the needs that sit behind the numbers they put on the table.

The conversation itself is rehearsed through role-play built on the learner's own situations. The tutor plays the other party, including the moment they say no. Learners practise stating a request together with its reasons, asking questions before making a counter-offer, and responding calmly to refusal, for example by asking which part of the proposal is the sticking point. Any agreement reached is closed with a written summary of the agreed points, since working relationships usually continue long after the negotiation ends.

Hybrid and remote teams lose many of the cues that help in an office: facial expressions, tone of voice and the chance to ask a quick question in passing. Written messages therefore need to be more explicit. Learners practise giving deadlines with the time zone attached, writing a clear definition of done for a task, and summarising each video call in a written note afterwards so that anyone who missed it works from the same information.

Working with colleagues or partners from other cultures adds another layer. The anthropologist Edward T. Hall distinguished high-context cultures, which carry much of their meaning through relationships and unspoken cues, from low-context cultures, which rely on explicit words. Many Indonesian learners are at home in the first style. A reply such as I will try my best can be read as a commitment by a colleague from a low-context culture, while the speaker meant it as a gentle no.

Practice in this area centres on the habit of checking understanding. After giving instructions, learners ask the colleague to sum them up in their own words, or end a message with one question that confirms what has been agreed. Simulations use the learner's own work, such as a video meeting with head office in another country or a message to an overseas supplier. The skill is settling in when misunderstandings that only surface at the end of a project become uncommon.