A colleague sends a short text: "Please bring the equipment for tomorrow's demo." No reply comes back. The next morning, nothing is brought. No one ignored the message, and it did land — something about how it travelled broke down all the same. Before reading on, name the fault yourself: what actually failed here, if not the words?
Every word in that message was spelled correctly and put together well. It still failed, and it is not a rare case. A correct message fails for almost always one of three reasons. The wrong form for the job. A missing detail the receiver needed in order to act. Or a feedback loop that never closed. Fix all three, and the reply comes back the first time.
This unit follows that one failed message end to end. It moves through the forms the message could have used. It follows the cycle the message moved through. And it ends with the writing habits that would have named the missing detail out loud.
Go back to the equipment message. It was sent as a short text — plain written words, nothing else. Before you are told the three forms that actually exist, guess: could that message have worked better as a phone call? A hand signal on the spot? A photo of the exact equipment needed?
Methods of communication — three forms: (1) Verbal communication: spoken or written words. (2) Non-verbal communication: body language, gestures, facial expressions, tone, eye contact. (3) Visual communication: images, charts, diagrams, posters, videos.
Choose the wrong form, and even a correct idea fails to arrive. The equipment message used only the first form: written words. A photo of the exact equipment, the visual form, might have closed every doubt in one glance.
Split verbal into its spoken and written halves, and each of the four resulting forms carries its own strength, and its own limit, worth knowing before you pick one. Spoken verbal is fast and lets both sides respond at once, but it leaves no record once the words are gone. Written verbal is precise and can be re-read later, but it takes longer to compose than a quick word aloud.
Non-verbal communication carries feeling and emphasis that plain words often miss — a raised eyebrow can say more than a full sentence. Yet it is easy to misread across different cultures and settings. Visual communication works at a single glance and crosses language gaps that words cannot. But a careless chart can mislead just as fast as a careful one can inform.
None of the four forms wins outright. The skill is matching the form to the task, not owning a favourite one. Stack two or three forms together when one alone will not carry the whole message. A manager who only reads the equipment text will miss what one quick photo would have shown at a glance.
The equipment message went out and nothing came back. That silence has a name, and a map that shows exactly where it broke.
Communication cycle — the path a message travels: Sender → Idea → Encoding → Communication Channel → Receiver → Decoding → Feedback → (back to Sender). Communication is complete only when feedback returns to the sender. Without feedback, the cycle is open — the sender does not know if the message was understood.
Trace the equipment message through that map. A colleague was the Sender. The idea was "I need the projector and the cables tomorrow." Encoding turned that idea into words, but it left out exactly which equipment. The channel was a text message. A manager was the Receiver, and decoding happened the moment it was read. What never happened was the return trip. The cycle is not finished until feedback comes back to the sender.
Look at the figure beside this paragraph. The same seven stages sit in the same loop you just read, closed by the same return arrow already drawn in the map two paragraphs back — nothing new there. What this figure is for is the box in the middle: the Channel node.
The Channel node is not one single thing, even though the figure keeps it as a single box. In practice it opens out into the actual choices available at that stage: spoken, written, visual, digital. Three of those — spoken, written, visual — match the forms the last section named; digital is new here, and non-verbal from that section is not itself a channel type.
The return arrow matters most — it marks the gap between sending and being understood. Follow every stage forward without it, and all you have is transmitted. Only the arrow curving back closes the loop into something worth calling communicated.
Test a common belief properly, instead of assuming it: is communication finished the moment the sender stops speaking or writing? A teacher can talk for a full hour, cover the whole topic, and stop exactly on time. By that belief, the job is done.
Now check what actually happened in the room. Not one student answered a question. Not one hand went up. Nothing came back to the teacher at all. Sending proves only that the message left the sender. It proves nothing about whether it arrived, or whether anyone understood it.
Transmitted is not communicated — feedback is the only thing that tells them apart. The teacher who talked for an hour with silence in return has transmitted, not communicated. Exam answers get this wrong often enough that it is worth stating flat: sending never confirms understanding on its own.
"Communication ends the moment the sender finishes speaking or writing."
It does not. Finishing the sentence only completes the sending half of the cycle. The confirming half — feedback returning to the sender — has not happened yet, and until it does, the cycle stays open. A room that stays silent after an hour of talking has been transmitted to, not communicated with. The sender only learns whether the message worked once something comes back.
Send the exact same four words to two different people: "You have five minutes." One person breaks into a grin. Another starts to worry. The words never changed. Something else did.
That something is perspective — the personal lens every receiver reads a message through. Six factors build that lens. Visual perception decides what a person notices first. Language covers word choice, dialect, and mother tongue. Past experience is what someone has already lived through. Prejudices are the ideas already sitting in their head. Feelings are their emotional state at that exact moment. Environment is the physical and social setting they are in. None of these makes a receiver wrong.
Picture the receiver's lens, not only your own intent. Before you send anything, ask what mood, memory, or setting might be shaping how it lands on the other side.
Try this exercise yourself. Two students receive the exact same instruction: "You have five minutes." One is excited about what happens next. The other is worried about not finishing in time.
Each student writes one sentence about what the message means to them. Then the class names which factor shaped each reading — feelings, past experience, or environment. The point is never to decide who read it correctly. Both readings are real.
The words were identical; the reaction was not — that gap is perspective at work. One short line proves it faster than any explanation could. Consider the receiver's lens, not only your own intent, before your next message leaves your hands.
Look again at the equipment message's actual weak point: "the equipment" names nothing specific. Spoken conversation runs fast, with both sides free to respond right away, so a mistake like that gets a second chance to be caught mid-conversation. Written words do not get that second chance automatically. That is exactly why the pieces that build a written message matter so much.
Writing skills — the building blocks of written communication: phrases (groups of words without a verb), kinds of sentences (declarative, interrogative, imperative, exclamatory), parts of a sentence (subject and predicate), parts of speech (noun, verb, adjective, adverb, pronoun, preposition, conjunction, interjection), use of articles (a, an, the), and paragraph construction (topic sentence + supporting sentences + closing sentence).
A phrase without a verb; a sentence with one — the difference decides whether the reader can act. "The equipment" is a phrase. "Bring the projector and the cables" is a sentence — it carries a verb, and gives the reader something to do.
A sentence can be grammatically fine and still fail the reader. Go back to the equipment message one more time. "Please bring the equipment for tomorrow" has a verb, with the subject you understood — nothing wrong there. It has a predicate, too — but a vague one, not yet something the receiver can act on: which equipment, exactly?
A well-built sentence names its subject — or, as in a command, leaves it clearly understood — and gives a clear, actionable predicate, not a vague one. A well-built paragraph works the same way at a larger scale. It leads with a topic sentence that names the main idea. It adds supporting sentences carrying the detail the receiver needs in order to act. It closes with a sentence that confirms exactly what action is expected.
Structure is a service to the reader, not a rule for its own sake. Written words can be re-read and revised before they are sent — exactly the chance the equipment message wasted.
Pick a topic linked to a subject you are studying. For example: "A day I used ICT to solve a problem." Write exactly three sentences.
Sentence one is the topic sentence, naming the main idea. Sentence two is the supporting sentence, adding one real detail. Sentence three is the closing sentence, confirming what happened or what comes next.
One sentence to name the idea, one to add to it, one to close it — three sentences, one job each. Check your own work before anyone else does: does sentence one have a subject and a predicate? Does sentence two add information instead of repeating the first sentence? Then swap with a partner and name the parts of speech for the verbs in sentence two.
Here is the exact question an examiner might set, worth two marks. List the elements of the communication cycle in order, and name the element that makes the cycle complete.
Work it through the way you would in the exam. Sender, Idea, Encoding, Channel, Receiver, Decoding, Feedback, back to Sender: that is the order. Now name the completing element. A tempting answer is Receiver — after all, the message has arrived. But arriving is not the same as being understood.
Receiver ≠ Feedback — only feedback tells the sender it landed. The completing element is Feedback, not Receiver. The reason: without it, the sender has no way of knowing whether the message was understood at all.
"The cycle is complete when the Receiver gets the message."
Arrival and understanding are two separate events. The Receiver stage only confirms the message got there. Confirmation that it was understood is Feedback's job, two stages later, travelling back to the Sender. Write "Receiver" as your completing element, and you have named the wrong stage — the loop is not closed until something returns.