What you'll learn
Communication in a business context is the transfer of information from sender to receiver in a way that produces the intended understanding, and group dynamics is the study of how people behave when working together. The two belong in one topic because most organisational communication happens within and between groups, and because the commonest failures — decisions nobody questions, information that never reaches the people who need it — are group problems rather than individual ones. This guide covers the communication process and its barriers, formal and informal channels, communication networks, the stages of group development, roles within teams, cohesion and conformity, and how meetings and teams are made to work. It sits in Unit 1 Module 2.
Key terms and definitions
Communication — the transfer of information producing the intended understanding in the receiver.
Sender — the person originating a message.
Encoding — putting a message into words, symbols or images.
Channel — the means through which a message travels.
Decoding — the receiver's interpretation of the message.
Feedback — the receiver's response, confirming whether the message was understood.
Noise — any interference with a message.
Formal communication — communication following the organisation's official structure.
Informal communication — communication outside official channels, often called the grapevine.
Vertical communication — communication up or down the chain of command.
Horizontal communication — communication between people at the same level.
Communication network — the pattern through which information flows in a group.
Group — two or more people who interact and see themselves as a unit.
Team — a group working towards a shared objective with complementary roles.
Group cohesion — the strength of the bonds holding a group together.
Conformity — adjusting one's behaviour or opinion to match the group.
Groupthink — the suppression of dissent within a cohesive group, producing poor decisions.
Core concepts
The communication process
A message passes through a sequence, and it can fail at every step.
Sender → encodes → transmits through a channel → receiver decodes → feedback returns
Encoding fails where the sender chooses words the receiver does not share. The channel fails where it is unsuited to the content or subject to interference. Decoding fails where the receiver's knowledge, expectations or emotional state distort what was sent. Feedback is what makes failure visible, and without it the sender assumes success.
Noise is anything interfering at any stage — physical sound, technical failure, ambiguous wording, or the receiver's preconception about the sender.
Direction of communication
Downward communication carries instructions, objectives and policy from managers to staff. It is the most used and the most over-relied on, because managers routinely assume a message sent is a message received.
Upward communication carries reports, suggestions, grievances and results from staff to managers. It is the direction most likely to be blocked, because subordinates filter what they pass up — bad news travels slowly upward, which is why managers are often the last to learn of a problem.
Horizontal communication runs between people at the same level and is essential for coordination between departments. Organisations with strong vertical channels and weak horizontal ones develop departments that each work well and do not work together.
Diagonal communication crosses both level and department, and is faster than routing everything through the hierarchy.
Formal and informal channels
Formal communication follows the official structure: meetings, memoranda, reports, notices, appraisals. It is recorded, traceable and authoritative, and it is slow.
Informal communication — the grapevine — runs through personal relationships and is fast, reaches everyone, and carries the things people actually want to know. Its weaknesses are that it distorts as it travels and cannot be corrected once wrong.
The practical point for management is that the grapevine cannot be abolished and rarely should be. It fills a vacuum, so where formal communication is slow or evasive the grapevine expands to fill it — which means an unwelcome rumour usually indicates that management has not communicated something it should have.
Communication networks
The pattern through which a group communicates affects both speed and satisfaction.
A chain passes information along a line and is accurate for simple messages and slow for anything else. A wheel routes everything through one central person, which is fast for simple tasks and leaves everyone but the centre poorly informed. A circle lets each member communicate with neighbours, which is slower but more satisfying. An all-channel network lets everyone communicate with everyone, which is best for complex problems and for member satisfaction, and slowest to reach a decision.
The lesson is that no network is best: centralised patterns suit simple urgent tasks, and open patterns suit complex problems needing everyone's knowledge.
Groups and teams
A group is two or more people who interact and regard themselves as a unit. A team is a group working towards a shared objective with complementary roles and mutual accountability — every team is a group, and not every group is a team.
Formal groups are created by the organisation: departments, committees, project teams. Informal groups form through personal affinity and shared interest, and they exert real influence over behaviour, standards and how readily change is accepted.
Stages of group development
Groups develop through recognisable stages, and a manager expecting immediate performance from a new team misreads the process.
Forming — members meet, are polite and uncertain, and depend on the leader for direction.
Storming — disagreement surfaces over objectives, roles and influence. It is uncomfortable and is a necessary stage rather than a failure; groups that suppress it tend to carry the disagreement unresolved.
Norming — the group settles its working methods, roles and standards.
Performing — the group works effectively towards the objective with less dependence on the leader.
Adjourning — the group disbands once the task is complete.
Roles within a group
Effective teams need a mix of contributions, not a set of identical people. Broadly these divide into task roles — proposing ideas, seeking and giving information, coordinating, evaluating, driving towards completion — and maintenance roles — encouraging, resolving conflict, ensuring quieter members are heard.
A team of people who all propose ideas and none who complete them will not deliver; a team of implementers with no one generating options will do the wrong thing efficiently. The management implication is that team composition should be deliberate, and that a member whose contribution differs from the majority's is usually valuable rather than difficult.
Cohesion, conformity and groupthink
Cohesion is the strength of the bonds holding a group together. Cohesive groups communicate more, support their members and stick to their agreed standards — but if those standards are low, cohesion enforces low performance just as firmly as high.
Conformity is adjustment to the group's expectations, and it operates more powerfully than people believe of themselves.
Groupthink is the point at which cohesion suppresses dissent: members withhold doubts to preserve agreement, alternatives go unexamined, and the group becomes confident in a decision nobody tested. Its symptoms are an illusion of invulnerability, pressure on doubters, and self-censorship.
Remedies are structural rather than exhortation. Invite dissent explicitly, assign someone the role of arguing against, bring in outside views, have the leader state their own position last so it does not anchor the discussion, and revisit a decision after a pause before committing.
Making meetings and teams work
Meetings are the most visible and most wasted form of organisational communication. They work where there is a stated purpose and an agenda circulated in advance, only the people who need to be there attend, someone chairs so that the discussion stays on the question and quieter members are heard, decisions and actions are recorded with named owners, and the record is circulated promptly.
For teams more generally: a clear shared objective, complementary roles, agreed working methods, a size small enough for everyone to contribute, and a genuine ability to raise disagreement without penalty.
Worked examples
Example 1: Diagnosing a communication failure
Question: "Staff report that they are not told about changes until after they happen. Analyse and recommend." (15 marks)
Outline. Diagnose by direction and channel rather than describing the complaint. The failure is downward communication being too slow, and probably upward communication being blocked, since management appears unaware that staff feel uninformed. Predict the consequence: the grapevine expands to fill the vacuum, so staff learn of changes as rumour, which arrives distorted and cannot be corrected. Then recommend specifically — brief before implementing rather than after, choose channels suited to the content with important changes communicated face to face and confirmed in writing, build in feedback by asking staff to state their understanding, and open an upward channel that does not depend on the immediate manager, since status difference blocks it. Conclude that the objective is not to eliminate the grapevine, which is impossible, but to remove the vacuum it is filling.
Example 2: Group development
Question: "A newly formed project team is arguing and making little progress. Advise the manager." (12 marks)
Outline. Identify the stage: this is storming, which follows forming and is a normal and necessary part of development rather than evidence that the team was badly chosen. Explain what is happening — disagreement over objectives, roles and influence is surfacing, and a group that suppresses it carries the disagreement unresolved into later work. Then advise: clarify the objective so the argument is about method rather than purpose, agree roles explicitly, establish working methods and decision rules, and allow disagreement to be expressed rather than closing it down. Warn against the two wrong responses — disbanding the team, and imposing agreement — since both prevent the group reaching norming. Conclude that the manager's role changes across the stages, being directive early and stepping back as the team reaches performing.
Example 3: Groupthink
Question: "Explain groupthink and how a manager might guard against it." (12 marks)
Outline. Define it as the suppression of dissent within a cohesive group, and be precise that the cause is cohesion rather than incompetence — which is why capable, experienced groups are vulnerable. Give the symptoms: an illusion that the group cannot be wrong, pressure on anyone who raises doubts, and self-censorship by members who assume the silence of others means agreement. Then give structural remedies rather than exhortations to think critically: assign someone to argue the opposing case, invite outside views into the discussion, have the leader withhold their own opinion until others have spoken so it does not anchor the debate, and revisit the decision after a pause. Conclude by noting the trade-off explicitly — cohesion brings real benefits in communication and mutual support, so the objective is to preserve it while protecting dissent, not to weaken the group.
Common mistakes and how to avoid them
Treating a message sent as a message received. Communication succeeds only when understanding is produced.
Omitting feedback from the process. It is what makes failure visible.
Confusing a group with a team. A team has a shared objective, complementary roles and mutual accountability.
Describing the grapevine as purely harmful. It is fast and fills a vacuum management created.
Treating storming as a failure. It is a necessary stage.
Assuming cohesion is always good. Cohesive groups with low standards enforce low performance.
Offering "communicate better" as a remedy. Name the direction, the channel and the mechanism.
Recommending critical thinking as the cure for groupthink. The remedies are structural.
How this links to your Internal Assessment
Communication and group working are accessible project themes because you can observe them directly, but they are also where respondents are least candid.
Expect the barriers you are studying to affect your own data collection. Employees asked about communication with their manager will give the answer they judge safe, and the status difference between a student researcher and a respondent makes this worse. Asking about specific events — how staff learned of the last change, how long it took — produces better evidence than asking whether communication is good.
The productive approach is to compare the formal channels the business believes it has with how information actually travelled in a particular case. Where the grapevine carried something before the formal channel did, you have a concrete finding rather than an impression, and recording honestly that your own access shaped what respondents told you strengthens the limitations section.
Exam technique for communication and group dynamics
Use the process — sender, encoding, channel, decoding, feedback — to locate exactly where a failure occurred.
Name the direction of communication: downward, upward, horizontal or diagonal.
Match the channel to the content; important or sensitive messages need more than a written notice.
Name the stage of group development before advising on a team problem.
Give structural remedies for groupthink rather than telling people to think critically.
Acknowledge that the grapevine cannot be removed and indicates a formal vacuum.
Watch the command word: identify wants the barrier or stage, explain wants the mechanism, analyse wants the relationships, evaluate wants a judgement.
Quick revision summary
Communication succeeds only when the receiver's understanding matches the sender's intention, and it can fail at encoding, channel, decoding or feedback, with noise interfering at any stage. Communication runs downward carrying instructions, upward carrying reports and grievances — the direction most often blocked, since subordinates filter what they pass up — horizontally for coordination between departments, and diagonally across both. Formal channels are recorded and authoritative but slow; the informal grapevine is fast and distorts, cannot be abolished, and expands wherever formal communication leaves a vacuum. Network patterns matter: centralised chains and wheels suit simple urgent tasks while circles and all-channel networks suit complex problems and produce more satisfaction. A team differs from a group in having a shared objective, complementary roles and mutual accountability, and groups develop through forming, storming, norming, performing and adjourning — with storming a necessary stage rather than a failure. Teams need both task and maintenance roles rather than identical members. Cohesion strengthens communication and support but enforces whatever standards the group holds, and at its extreme produces groupthink, where dissent is suppressed and untested decisions are made confidently; the remedies are structural — assigned dissent, outside views, the leader speaking last, and revisiting decisions after a pause.