Communication

Communication is the transfer of information from a sender to a receiver in a way that produces shared understanding, ideally confirmed by feedback. For example, a manager emailing a new target to staff who read, understand and acknowledge it.

Two barriers are information overload (too many messages so important ones are missed) and physical noise (environmental interference such as loud machinery that distorts the message).

Formal communication flows through the official, recognised channels of the organisation — for example a company memo or an appraisal meeting. Informal communication happens outside official channels, such as a corridor chat or the grapevine. The key difference is whether the channel is officially sanctioned by the business.

Information overload occurs when a receiver is sent more messages than they can process. In a large office, staff may receive well over a hundred emails a day plus instant messages and meeting invites. Because they cannot read and act on everything, important messages get buried and missed — for example an urgent change to a client deadline is lost among routine emails, so a task is done wrong or late. In this way the volume of communication itself blocks the key message from being received and understood, which is exactly what a barrier does. It can also demotivate staff who feel overwhelmed and stop checking messages carefully.

In a wheel network the supervisor is the central hub through whom all communication flows, and the agents do not communicate directly with each other. This has clear benefits for a call centre: it is fast and gives the supervisor tight control, so instructions and script changes can be pushed out quickly and consistently, and the supervisor has a full overview to make quick decisions — useful in a fast-moving, standardised environment. However, it also has drawbacks. The agents on the outside have low morale because they only receive information and cannot easily share ideas or problems with each other, which can reduce engagement and creativity. The network also depends heavily on the supervisor: if they are absent or overloaded, communication breaks down and agents are left without direction. Overall the wheel suits the call centre's need for speed and control, but at the cost of agent morale and resilience if the hub fails.

The barrier is technology failure: the digital channel (email) broke down because of a server outage, so the message was never delivered or read, blocking communication entirely. The effect was a two-week delay in responding to a customer, harming service and possibly the relationship. To reduce the risk, TransGlobal should not simply 'use email more' — instead it should build in a backup and confirmation: for example, an automated delivery/read receipt or a ticketing system that flags unanswered messages after 24 hours, plus a secondary channel (such as a phone call or shared dashboard) for urgent customer issues. This is appropriate because it directly addresses the failure of a single digital channel — the confirmation catches undelivered messages and the backup channel keeps communication flowing when the technology fails, tackling the specific barrier rather than communication in general.

PrintPro's problem must first be diagnosed precisely rather than treated as vague 'bad communication'. The stimulus shows a clear barrier: physical noise. Verbal instructions shouted across loud machinery are distorted, so operators decode the wrong message and print jobs incorrectly, wasting materials and time and lowering productivity; the mutual blame suggests morale is also falling.

Because the barrier is physical noise, the targeted improvement must attack that barrier. PrintPro should reduce reliance on shouted verbal instructions on the floor. Options include: issuing job instructions in written or visual form (a printed job sheet or an on-screen work order at each machine) so operators have an unambiguous record; holding short 'toolbox' briefings in a quiet room away from the machines at the start of each shift; and using visual signals or a simple digital display board for changes. Each of these delivers the message through a channel the noise cannot distort.

The options should be evaluated. Written/visual job sheets are cheap, leave a permanent record and remove the mishearing entirely, but rely on operators reading them and may slow very urgent changes. Quiet-room briefings improve understanding and morale (staff can ask questions) but take operators off the machines briefly, a small output cost. A digital display board has a set-up cost and its own risk of technology failure. Choosing among them is a trade-off between cost, speed and reliability.

There is also a wider point: fixing the medium alone may not repair the damaged morale from weeks of blame, so PrintPro should combine the technical fix with rebuilding trust — acknowledging the problem was systemic (the noise), not the operators' fault.

In conclusion, PrintPro should replace shouted floor instructions with clear written/visual job sheets at each machine, supported by short quiet-room shift briefings. This is the strongest option because it directly removes the physical-noise barrier that is causing the misprints — the root cause — at low cost, while the briefings restore two-way communication and morale. A generic 'communicate better' would fail; the fix works precisely because it is matched to the specific barrier evidenced in the case, and PrintPro should judge success by falling reprint rates and recovering productivity.

Moving DataFlow to an all-digital system is a significant change, and its impact on communication has both strong benefits and real risks that must be weighed.

On the positive side, digital methods suit a growing, partly remote firm. Email, chat and video calls are fast, cheap over distance and reach many people at once, so DataFlow can coordinate remote developers, keep a written record of decisions, and communicate across time zones without travel costs. Video calls retain some of the tone and instant feedback of face-to-face contact, softening the loss of in-person meetings. For a software firm whose staff are already comfortable with technology, adoption should be relatively smooth, supporting horizontal communication across teams.

However, the change brings barriers of its own. The most likely is information overload: chat and email can bombard staff with messages, so important ones are missed and employees feel overwhelmed — harming productivity and motivation. There is also a risk of technology failure (an outage cuts off all communication at once, since there is no face-to-face fallback) and a loss of the richer, informal, relationship-building communication that happens in person, which can weaken team cohesion and the healthy grapevine. Sensitive conversations (e.g. performance issues) handled by chat would be a poorly chosen medium.

Whether the impact is net positive depends on how DataFlow manages the change. If it simply switches channels with no rules, overload and impersonal communication will damage morale. If it manages the change well — setting norms (e.g. reserving video for complex or sensitive topics, chat for quick queries), limiting message volume, and keeping a reliable backup — it captures the speed and reach of digital while limiting the barriers.

In conclusion, the switch is likely to improve the speed, reach and record-keeping of DataFlow's communication and is well-suited to remote growth, but only if the firm actively manages the risks of information overload, technology dependence and lost personal contact. The change should therefore be introduced with clear communication protocols and training rather than as a blunt replacement of all face-to-face contact; judged that way, the net impact is likely positive for a tech-literate, growing firm, but it is the management of the change — not the technology itself — that determines the outcome.

InnovateLab's complaint points to a specific weakness of the chain network, so the decision to move to all-channel must be evaluated against the firm's needs as a research company.

The case for moving is strong. In a chain, information passes person to person up and down the hierarchy, so it is slow and distortion grows with each link — exactly the 'slow, distorted communication' the researchers report. For research and innovation, this is damaging: ideas need to flow quickly and be built on collaboratively, and a chain filters and delays them. An all-channel network, where everyone can communicate freely with everyone, would raise the speed of idea-sharing, cut distortion, and lift morale because every researcher can contribute — directly supporting creativity, which is InnovateLab's core purpose.

However, all-channel has drawbacks that must be weighed. It can be slower to reach firm decisions because there is no single controlling point, and without clear leadership discussions can become chaotic or unfocused. For routine, standardised messages it is less efficient than a chain or wheel, and in a large firm a full all-channel network among everyone can itself create information overload. So the benefit depends on the type of work: it is excellent for the creative research teams but may be unnecessary for routine administrative communication.

A balanced judgement is that InnovateLab does not have to choose one network for the whole organisation. It could adopt an all-channel network within the research teams — where creativity and speed of idea-sharing matter most — while retaining more structured (chain or wheel) communication for routine reporting and decisions. This targets the actual problem (stifled ideas among researchers) without losing all control.

In conclusion, InnovateLab should move its research teams to an all-channel network because it directly addresses the slow, distorted, idea-stifling communication the chain is causing and it fits the collaborative, creative nature of research. The main caution is decision-making speed and possible overload, so this should be paired with clear team leadership and kept to the areas where creativity matters, rather than imposed on every process. Judged against InnovateLab's need to generate ideas, the change is justified — but as a targeted move for the research teams, not a blanket replacement.