Clear Communication Is a Creative Act

The work doesn't speak for itself

Designers love to believe the work speaks for itself. It doesn't. It never has. The most beautiful solution in the world dies in a feedback thread if you can't help the room understand what they're looking at and why it's right.

This is part two of three on shipping the brief beyond pretty pixels. Part one was about how you show up. This one is about how you explain, because the ability to communicate an idea with clarity, and a little creativity, is what separates work that ships from work that gets 'circled back to.'

Clear communication isn't the thing you do after the design. For anyone building inside an org, or building the org, it is the design.

“Your idea is only as strong as your ability to make someone else see it.”

Communicate the why before the what

When I present a homepage, I don't open with the homepage. I open with the one sentence a new user has to believe, the business reason it matters, and only then show how the layout earns it. By the time the design appears on screen, the room is already rooting for it, because they helped define the problem it solves.

Most design feedback goes sideways for a single reason: the designer led with the what, the color, the layout, the type, and left the stakeholder to reverse-engineer the why. So the stakeholder fills the silence with taste. 'I don't love the blue.' Now you're defending a hue instead of a decision.

Lead with the why and the conversation changes shape. The moment you connect a choice to something the stakeholder already cares about, the metric, the user, the deadline, you stop debating opinions and start debating outcomes.

“Stakeholders don't reject good design. They reject design they can't connect to something they already care about.”

Creativity is how the message lands

Here's where the craft comes in. Communicating well isn't just being clear, it's being memorable. The format of your message deserves the same creative attention as the artifact it describes.

A ten-second prototype beats a ten-line paragraph. A tight before-and-after beats a wall of rationale. A good name for a pattern travels through an org faster than any spec. At vCluster, the design system didn't spread because of the documentation. It spread because we gave things names people actually enjoyed saying. 'Tier-one surface.' 'Technical callout.' Language people repeat is language that wins.

Find the one image, demo, metaphor, or phrase that makes the idea click, and lead with it. You are not just shipping the work. You are shipping other people's ability to repeat it when you're not in the room.

“The format of the message is part of the message. Treat how you communicate with the same craft as what you ship.”

Write it down, then say it simply

Clarity is a writing problem before it's a speaking problem. Before any real review, I write the argument out in full, every reason, every objection, every tradeoff, and then I delete half of it. What survives is the version worth saying out loud.

The discipline is the same one you use on a layout: find what's essential, cut what's decorative, and respect the audience's attention. If you can't explain the decision in two sentences, you either don't understand it yet or it isn't the right one.

In part three, I'll get into momentum: why shipping a clear, imperfect thing beats perfecting a thing nobody has seen. For now: say less, mean more, and never make the room work to understand you. The clearest person in the meeting is usually the one who ends up leading it.