The idea that the work should speak for itself is true in a gallery. In a client meeting it's a liability.

Design education is built around the work. Rightfully so. The portfolio is the primary evidence of what you can do, and developing the ability to produce something worth showing takes years of serious attention. 

But somewhere in that education, a belief takes hold that tends to follow designers into their careers long after it stops serving them. The belief that if the work is good enough, it doesn't need explaining. That the thinking behind it should be self-evident to anyone with the eye to see it.

In practice, that belief costs people work. Here's why.

The person commissioning you was not inside your process.

They didn't sit with the problem the way you did. They didn't work through the alternatives, understand what was rejected and why, or arrive at the solution through the same sequence of thinking that produced it. 

What feels self-evident to you, because you lived it, is opaque to them until you make it legible. The ability to walk someone through your reasoning, clearly and without defensiveness, is not a soft skill sitting alongside the design work. It's part of the design work.

A decision you can't explain is a decision you can't defend.

Clients push back. Art directors challenge. Stakeholders arrive late to a project with opinions formed without context. The designers who hold their ground in those moments aren't the ones with the strongest visual instincts. They're the ones who can articulate why the work is the way it is with enough clarity and conviction that the room understands what's at stake in changing it. 

That ability is built through practice, not talent.

The presentation is testing something different to what you think.

In education, presentations are assessments of the work. In practice, they're assessments of the thinking. A client sitting across from you isn't just evaluating the design on the screen. They're deciding whether they trust the person who made it to make the next decision and the one after that. That trust is built through how you communicate, not just what you produce. 

A designer who can explain their process clearly feels safer to work with than one who can't, regardless of the quality of the output.

Writing is the same muscle as design and it develops both.

The designers who write well, who can produce a clear brief rationale, a considered email, a proposal that makes the thinking behind a recommendation legible, tend to think more clearly about the work itself. The two disciplines develop each other in ways that aren't obvious until you start taking both seriously. If your writing is vague, there's a reasonable chance your design thinking is vaguer than it needs to be too. 

Sharpening one sharpens the other.

The brief is almost never complete enough. Asking the right questions is a communication skill.

The designers who consistently produce work that lands aren't always the ones with the most technical ability. They're the ones who ask better questions at the start of a project, who surface the ambiguity in a brief before it becomes a problem halfway through and who make the client feel understood before a single pixel is placed. That capacity starts with how you listen and how you respond and it's developed deliberately, not by accident.

The work still matters. It always will. But the career is built in the space around it.

Grab yourself a flat white and pull up a seat. The real course is just beginning.

Shot of the good stuff.