OE1-1.1 Communication: Nature, Process & Technical Communication

What this is and why it exists

Engineers are asked to write more than they expect, and the honest reason is blunt. Work nobody can read is work nobody can use.

This topic sets the model the rest of the course refers back to, and its most useful idea is structural. Most workplace communication failures are not failures of wording. The message went the wrong way through the organisation.

The vocabulary

• Sender and receiver — the two ends of any communication.
• Encoding and decoding — putting a message into words, and taking meaning back out.
• Feedback — the receiver's response, which tells the sender whether it arrived.
• Downward communication — from management towards staff.
• Upward communication — from staff towards management.
• Horizontal communication — between people at the same level.
• Barrier — anything preventing a message arriving as intended.
• Technical communication — writing or speech whose purpose is to let a reader do something.

The mental model

Communication is a loop, not a transmission. Someone encodes an idea into words, sends it, and the receiver decodes it into an idea of their own. The two ideas are never identical. Feedback is what tells you how far apart they are, and communication without feedback is broadcasting and hoping.

The three channels are more useful than they look.

Downward communication usually works, because the people sending it have authority and the people receiving it are paying attention.

Upward communication is the one that fails. Reporting a problem upward means telling someone with power over you that something has gone wrong, often something they approved. So bad news travels upward slowly, incompletely, or not at all. That is a structural problem, not a personal failing, and organisations that fix it do so by building routes that do not depend on courage.

Horizontal communication is the one people forget exists. Two teams that need to coordinate often send everything up to a common manager and back down, which is slow and lossy. Recognising that a message needs to go sideways is often the whole solution.

Barriers are the most immediately useful item here, because you can act on them tomorrow. They include physical ones such as noise, language ones such as jargon the receiver does not share, and organisational ones such as too many layers. The most common is assuming shared context. A message that makes sense to you, because of what you already know, arrives incomplete to someone who does not.

Technical communication is distinguished by purpose, not by subject. It exists so a reader can do something: build the thing, decide about it, repair it, or use it. That purpose is what makes accuracy and clarity outrank elegance. A beautiful sentence that leaves the reader unsure what to do has failed at the only thing it was for.

The properties follow from that. Accuracy, because a wrong number is worse than no number. Brevity, because a reader looking for one fact should not have to read everything. Clarity, because the reader is trying to act rather than to admire. And a defined audience, because you cannot write clearly without knowing who is reading and what they already know.

Four skills are listed, and the ordering is worth noticing. Listening comes first and is the one nobody practises. Reading efficiently is the one that most affects how fast you can work, because engineers read specifications, datasheets and other people's code all day. Speaking and writing get all the attention and are only half of it.

What you should now be able to explain or do

Describe communication as a loop and say what feedback tells you. Name the three channels and explain why upward flow fails structurally. Recognise when a message needs to go sideways. Name the common barriers and the one caused by assumed context. Define technical communication by its purpose and derive its four properties from that purpose.

Check yourself