Foundations of Clear Communication

That happens often enough to plan around. A good idea argued badly loses to a weaker idea argued well, and no amount of craft in the file protects you from it.

Designers resist this. We want the work to speak for itself, and to believe that a better solution will be recognized as one. But your design gets judged by busy people who each care about a different thing, and who are deciding whether to spend money and weeks of engineering on it. Communication is what carries the work through those people intact.

This module is the groundwork underneath every room you'll walk into later. Before you can argue a decision or pitch an investor, you need the parts a message is built from. You also need a way to test whether it's clear, and the habit of hearing what somebody actually meant.

Anatomy of a Work Message

A designer posts in the team channel: "hey, can someone take a look at the checkout thing when you get a chance?" Three days pass and nobody has looked at it.

The message was polite and grammatical. It was also missing almost everything a reader needs. Nobody knew which of the four checkout screens was meant. Nobody knew whether "take a look" meant review, redesign, or debug. And "when you get a chance" gave the request no place in anybody's week, so it took no place at all.

Requests like that go nowhere because a part is missing, not because the writing is bad. A work message has named parts, and you can check for them one by one.

The Six Parts of an Ask

Any message that wants something from somebody carries the same six pieces. Some are a sentence, some are three words.

• The ask: the one thing you want to happen, written as a verb. Review, approve, decide, build, answer.
• The owner: the person who does it, by name. "Someone" and "the team" are not owners.
• The deadline: a date, or the event that makes it urgent. "Before Thursday's planning" beats "soon".
• The context: the minimum background the owner needs to act, and no more. Two sentences is usually the ceiling.
• The options: where you want a decision, the choices you have already narrowed to, with your recommendation named.
• The subject line: the ask compressed to about six words, so the message is findable a month later.

Two of the six carry the entire schedule, and they are the easiest to leave out: the owner and the deadline. That's because the writer already knows both and forgets that nobody else does. A request with no owner belongs to everyone, which in a team of six means it belongs to no one.

Where the Message Lives

The four channels a designer works in differ in how long they last and how fast they expect an answer. Picking the wrong one is what turns a good message into a lost one.

• Chat: minutes to hours, scrolls away, small audience. Good for unblocking, poor for anything you will need to find again.
• Email: hours to days, permanent, crosses company boundaries. The default for clients and anyone outside your team.
• A document: permanent, has a URL, outlives every thread that points at it. The only channel where a decision can still be read next year.
• A meeting: immediate, expensive, and gone the moment it ends unless somebody writes it down.

Amazon treats that last point as a rule. Jeff Bezos banned slide presentations from executive meetings in 2004 and replaced them with six-page narrative memos. Those meetings still open with twenty to thirty minutes of silence while everyone reads. The reasoning is that a narrative forces the writer to connect their claims, and slides let a weak argument hide behind bullet points.

The Register Ladder

Formality is a scale rather than a switch, and the linguist Martin Joos named its five levels in The Five Clocks in 1961. Four of them appear at work.

• Frozen: fixed wording nobody rewrites. Contracts, privacy policies, legal disclaimers.
• Formal: one direction, no interruption expected, full sentences and no shorthand. A proposal, or a written report to a client's VP.
• Consultative: the working default. You explain your background because the reader may not share it, and you expect questions back. Most work email sits here.
• Casual: shared background assumed, shorthand allowed, sentences left unfinished. Your team channel.
• Intimate: private shorthand between two people, and not a work register at all.

Because the levels are a ladder, a mismatch is felt as distance in one direction or the other. "Hey, can you take another look at the checkout thing? 👀" is casual, which fits a teammate and reads as careless to a client's VP. "I have flagged an issue in the checkout flow and would value your review before we proceed" is consultative, and dropped into your team channel it reads as cold. So match the register to the reader, then check the six parts are still all there underneath it.

Pro tip: Write the subject line last, once you know what the message actually asks for. If you cannot compress the ask into about six words, the message is carrying two asks and should be two messages.