Why Over How
A reason behind every choice. The difference between production and direction is the sentence you can say out loud.
The work doesn't speak for itself
Designers love to believe the work speaks for itself. It does not, and it never has. The most considered solution in the world stalls in a feedback thread if you cannot help the room understand what they are looking at and why it is right.
The ability to say why, clearly and early, is what separates work that ships from work that gets circled back to. It is not the thing you do after the design. For anyone leading, it is part of the design.
“Your idea is only as strong as your ability to make someone else see it.”
Lead with the why, not the what
When you present a homepage, don't open with the homepage. Open with the one sentence a new user has to believe, and the business reason it matters, and only then show how the layout earns it. By the time the design appears, the room is already rooting for it, because they helped define the problem it solves.
Most feedback goes sideways for one reason: the designer led with the what, the color, the type, the layout, and left the stakeholder to reverse engineer the why. So they fill the silence with taste. I don't love the blue. Now you are defending a hue instead of a decision.
“Stakeholders don't reject good design. They reject design they can't connect to something they already care about.”
Every choice needs a sentence
Here is a test you can run on any decision in your file. Say the reason for it out loud in one sentence. If you can, it is a decision. If you cannot, it is a preference wearing a decision's clothes, and it will not survive the first hard question.
This is not about defending everything. It is about knowing which choices are load bearing and which are just habit. The ones you can explain are the ones you can hold. The rest you can let go of without losing anything.
“If you can't say why in one sentence, it isn't a decision yet.”
Why is what makes you a director
Production is making the thing. Direction is knowing why the thing should exist and being able to say so in a way other people can carry. The difference is not seniority or a title. It is whether there is a reason behind the choices, and whether you can put it into words.
Execution keeps getting cheaper. The reason behind the work does not. Get good at why, and you stop being the person who makes the screens and start being the person who decides what the screens are for.