Module 1: Communication Foundations

The Communication Loop and Where It Breaks

Most workplace problems that look like performance problems, attitude problems or even technical problems turn out to be communication problems. A supplier delivers the wrong quantity, a colleague misses a deadline they never knew existed, a customer feels ignored. Before you can fix these situations you need a simple model of what communication actually is, so you can see exactly where it went wrong instead of simply blaming the other person.

The basic loop

Every exchange, whether a WhatsApp message or a board presentation, follows the same loop:

1. Intent. You have an idea, need or feeling in your head.
2. Encoding. You turn that intent into words, tone, numbers, images and body language.
3. Channel. The message travels through a medium: face to face, phone, email, chat, a printed notice.
4. Decoding. The receiver interprets what arrived, using their own knowledge, mood, language and assumptions.
5. Feedback. The receiver responds, and you check whether what they understood matches what you intended.

Communication has only succeeded when the meaning in the receiver's head is close enough to the meaning in yours for the purpose at hand. Sending a message is not the same as communicating it.

Where the loop breaks

Each stage has typical failure points. Learning to name them makes it far easier to fix them.

Around the whole loop sits noise: anything that distorts the message. Noise can be physical (a loud matatu stage outside the office, a bad network line), psychological (stress, anger, distrust of the sender) or semantic (a word that means different things to different people, such as "end of month" when one person means the 30th and another means the last working day).

Worked example: the missing stock

Wanjiru manages a small hardware shop in Kitengela. On Monday she tells her assistant, Otieno, while serving a customer: "Remember to order cement, we're running low." On Friday a contractor arrives for 40 bags and the shop has 6. Wanjiru is frustrated; Otieno insists he did order.

Walk the loop. Her intent was "order enough for the contractor's Friday job". Her encoding left out the quantity and the deadline. The channel was a quick remark while she was distracted and serving a customer. Otieno decoded "running low" as "top up the usual 20 bags". There was no feedback step: nobody confirmed quantity or delivery date.

A repaired version: "Otieno, please order 50 bags of cement from our usual supplier today, delivered by Thursday, because Mr Kamau's crew collects 40 on Friday. Send me the order confirmation when you have it." It takes ten more seconds and removes three break points.

Closing the loop deliberately

The single most useful habit from this lesson is to build feedback into important messages. You can do this politely:

• Ask the receiver to summarise: "Just so we're aligned, what will you do first?"
• Ask for a confirmation artefact: an order number, a calendar invite, a reply email.
• When you receive instructions, play them back: "So you need the report by 3 p.m. Thursday, in Excel, covering only the Nairobi branches. Is that right?"

Playing back is not a sign of weakness. It shows you take the task seriously and protects both of you from expensive misunderstandings.

Common mistakes to avoid

• Treating "sent" as "understood". A delivered email or two blue ticks only proves the channel worked.
• Blaming the receiver first. Start by checking your own intent and encoding; they are the parts you control.
• Ignoring noise. Important conversations held in a noisy corridor, or while someone is upset, are likely to fail.
• Skipping feedback because you are in a hurry. The time you save is usually lost several times over fixing the error later.

In the rest of this course you will work on each stage of the loop in turn: clarity of encoding, choice of channel, listening and decoding, and handling feedback when emotions run high.