7.2 Business A2 communication
- Syllabus
- 9609–2026–2027
- Topic
- 7.2
- Level
- A2
Business communication is the transfer and interpretation of information or meaning between people/groups so that decisions, behaviour and relationships can be coordinated. Sending data is not enough: the intended receiver must receive, understand and—where required—act or respond.
| Situation in which communication is essential | Purpose | Failure consequence |
|---|---|---|
| Objectives, plans, roles and instructions | Coordinate work and clarify expectations | Duplication, omission, delay and inconsistent priorities |
| Safety, quality, legal or ethical requirement | Protect people/standards and create accountability | Injury, defects, penalties and reputation loss |
| Decisions and problem solving | Supply evidence, specialist/local knowledge and challenge | Poor decisions and missed operational ideas |
| Change, crisis or urgent disruption | Explain why/what/when, allocate action and update rapidly | Rumours, resistance, panic and service interruption |
| Employee feedback/conflict/motivation | Listen, involve, resolve and build trust | Demotivation, turnover, industrial conflict and silence |
| Customers, suppliers, investors and other stakeholders | Inform, persuade, negotiate and maintain relationships | Lost sales/supply/finance and damaged credibility |
Before communicating, specify purpose, audience/stakeholders, necessary content and confidentiality, required action, timing, suitable method/channel, accessibility/language, owner and evidence of understanding. Urgency, complexity and risk determine how much feedback and record are needed.
Clear two-way operational communication can surface employee ideas and prevent misunderstanding, improving coordination and productivity; lower unit cost may raise profit. It may also increase commitment and reduce turnover/recruitment cost. These outcomes depend on managers responding credibly and information arriving in time.
More messages can create overload and contradiction. Effectiveness means the right meaning reaches the right people at the right time through a usable route—not maximum volume.
| Standard method | Strengths | Weaknesses / poor fit |
|---|---|---|
| Spoken: face-to-face, meeting, phone, briefing | Fast, rich tone/non-verbal cues, questions and relationship building | No automatic record, inconsistency/ambiguity, scheduling and large-group inhibition; weak for dense technical detail alone |
| Written: report, letter, memo, notice, manual | Permanent/precise record, detail, consistency, legal/accountability evidence and asynchronous reach | Slow to draft/read/update, literacy/language and overload; delayed/no feedback |
| Electronic: email, intranet, messaging, video/app/portal | Rapid, scalable, searchable, multimedia and remote reach | Access/training, distraction/overload, security/privacy, impersonality and system failure; speed spreads error |
| Visual: chart, diagram, dashboard, sign, video demonstration | Makes pattern/process/spatial or multilingual warning easier to grasp and recall | Oversimplification/misleading scale, accessibility/design skill and context still needed |
Choose using purpose/action, audience size/location/access, urgency, complexity/sensitivity, need for dialogue, durable record/confidentiality, cost, reliability and receiver preference/capability. Then test whether understanding can be confirmed.
Methods are often complementary: announce restructuring in a live meeting for tone/questions, issue written terms/timeline for accuracy and record, use a visual organisation chart, and provide a secure electronic Q&A/feedback route. Avoid contradictory versions by naming the authoritative source.
Weekly two-way meetings can reveal production problems and make employees feel heard, improving ideas, motivation and productivity; but a large meeting may suppress questions. A written report provides evidence but cannot give immediate clarification. Analyse the actual method in its context rather than repeating generic advantages.
Fastest is not always effective; written is not automatically understood; electronic is not automatically cheap once systems, security and training are counted. Judge the complete communication job.
Communication process: sender defines purpose and encodes meaning → selects method/channel → message travels through possible noise/filtering → receiver accesses and decodes it using language/context → receiver acts and/or feeds back → sender checks understanding/outcome and corrects. Failure can occur at every stage.
| Dimension | Meaning | Example and issue |
|---|---|---|
| One-way | Sender transmits without built-in feedback | Notice/video is consistent and fast, but misunderstanding or employee ideas remain hidden |
| Two-way | Receiver can question, confirm and contribute | Meeting/chat supports clarification and commitment, but takes time and may be dominated/suppressed |
| Downward vertical | Higher to lower levels | Objectives/instructions; layers may filter, delay or distort |
| Upward vertical | Lower to higher levels | Performance data, concerns and ideas; status/fear may silence bad news |
| Horizontal | Between people/functions at similar levels | Operations-marketing coordination; silos, incompatible systems or unclear ownership may block it |
A channel is the route/network through which communication passes—direct manager, team meeting, hierarchy, cross-functional team, intranet/email, formal report or informal network. A method is the form (spoken/written/electronic/visual); one method can travel through different channels.
| Channel problem | Likely effect | Design response |
|---|---|---|
| Too many layers/gatekeepers | Delay, omission and distortion | Shorten route, direct escalation and shared source |
| One-way or weak feedback | Hidden misunderstanding/resistance | Questions, acknowledgement, teach-back and response owner |
| Overload/competing versions | Important message missed or inconsistent action | Prioritise, segment, summarise and version-control |
| Poor access/reliability/security | Exclusion, downtime or confidentiality breach | Accessible alternatives, redundancy, permissions and training |
| Functional/status boundaries | Slow coordination and filtered bad news | Cross-functional forums, psychological safety and clear ownership |
One/two-way describes feedback; vertical/horizontal describes organisational direction. A two-way exchange can be vertical or horizontal, formal or informal, spoken or electronic.
A communication barrier is any factor that prevents, delays or distorts a message or shared understanding between sender and receiver, or prevents appropriate feedback/action.
| Barrier/mechanism | Possible business impact | Targeted response |
|---|---|---|
| Jargon, ambiguity, language/literacy or cultural meaning | Wrong action, customer mismatch, conflict | Plain/translated language, examples/visuals, interpreter and teach-back |
| Physical distance, time zones, noise or poor timing | Delay, missed urgent change, weak participation | Planned overlap/escalation, quiet setting, recording and asynchronous summary |
| Technology/access/security failure | Booking/order/instruction lost; downtime or breach | Tested systems, access training, backup channel, support, permissions and recovery |
| Too many layers/filtering/status/fear | Bad news/ideas withheld or distorted | Direct safe feedback, fewer handoffs, anonymous/escalation routes and no-retaliation response |
| Overload, excessive detail or conflicting versions | Priority hidden and inconsistent action | Segment audience, prioritise, concise action summary and single source/version |
| Poor listening, assumptions or no feedback | False belief that meaning was shared | Questions, paraphrase, acknowledgement, observation and follow-up measure |
Diagnose before prescribing: identify intended meaning/action → locate whether failure arose in encoding, route/access, decoding, feedback or follow-through → gather receiver evidence → remove or bypass the cause → resend using suitable method/channel → confirm understanding and monitor the business outcome.
For an online international tour platform, language/culture mismatch can misstate customer needs, causing poor experience, bad reviews, reputation damage and lower future sales. Internet failure can prevent bookings or last-minute updates, losing revenue. Translation, verified listings, redundant systems and clear emergency contacts target different mechanisms.
Repeating the same message louder/faster does not repair inaccessible technology, fear, conflicting incentives or cultural interpretation. Match remedy to cause and check that the remedy worked.
| Informal communication | Potential contribution | Potential risk / management response |
|---|---|---|
| Unofficial social conversations/networks across or outside formal reporting routes | Fast local knowledge, relationships, belonging, problem warning and cross-silo coordination | Rumour, exclusion, distortion or confidentiality breach; provide timely credible facts, inclusive routes and verification—not blanket suppression |
| Communication quality | Efficiency mechanism |
|---|---|
| Clear priorities, roles, standards and deadlines | Less duplication, rework, waiting and supervision |
| Accurate timely upward/customer/operational evidence | Earlier correction and better resource decisions |
| Horizontal coordination | Matches demand, capacity, inventory, finance and people; fewer bottlenecks |
| Two-way involvement and credible response | More ideas, commitment and lower resistance/turnover |
| Poor, excessive, delayed or interrupted communication | Meetings/messages consume time; errors, conflict, downtime and missed opportunities raise cost |
Management method: define purpose/action and audience → choose accountable sender and suitable combination of methods/channels → make content concise, accessible, consistent and appropriately confidential → explain reason/context → create safe feedback and listen → check understanding → decide/respond visibly → assign action/resources/deadline → measure result and improve the route.
In a given situation, improvements may include fewer hierarchy handoffs, cross-functional meetings, shared intranet/dashboard, employee contribution channels, translated/visual summaries, communication training, reliable/secure IT with backup, version control, open-door/anonymous escalation and regular feedback. Select only measures that address the diagnosed cause.
A coordinated order/distribution system can reduce delay and improve tracking, but implementation cost, training, employee resistance, cyber/access risk and failure downtime may reduce short-run efficiency or sales. Pilot, train, support, protect data, retain fallback and monitor adoption; technology does not replace managerial communication.
Informal communication is neither automatically harmful nor fully controllable. Consultation is not enough: employees need to know what changed, why, who acts and how the outcome will be reviewed.