The sooner you learn this as a designer, the better it will be for you.
Imagine you are an F1 driver.
Your client owns the car and is sitting beside you. They know how to drive, but they have never driven an F1 race car. They want to win, and they have hired you because you understand the track, the machine, and the decisions required to get there.
The race begins.
Then, suddenly, they see another car overtaking you.
“Give me the steering wheel,” they say. “I’ll steer. You just handle the other controls.”
You can probably imagine what happens next.
The problem isn’t that the client doesn’t care about winning. They care deeply. The problem is that they are trying to solve a complex problem by taking control of something they hired an expert to manage.
Now replace car with project, steering wheel with design strategy, and driving with designing.
That’s the steering wheel theory.
The Client Knows the Destination. You Know the Road.
Clients understand their businesses, customers, ambitions, and commercial goals. Designers understand how to translate those goals into effective visual experiences.
Both perspectives matter.
But when a client says, “Make the button red,” the designer’s job isn’t necessarily to make it red.
The better response might be:
“Do you mean you want the button to be more prominent?”
Because prominence is the objective. Red is only one possible solution.
You could improve contrast, increase spacing, change the button size, simplify the surrounding layout, adjust the copy, or reposition the CTA.
There may be ten more effective and elegant ways to achieve the same goal.
The designer’s responsibility is to understand why the client is asking for something not simply execute the first solution they suggest.
Don’t Design for Approval. Design for the Outcome.
This doesn’t mean ignoring clients or treating their opinions as unimportant.
It means remembering who the project is ultimately for.
A website is for its users.
A landing page is for its visitors.
A product experience is for its customers.
A brand is for the people who need to recognize, trust, and remember it.
The client is paying for the project, but the end audience determines whether it works.
So don’t simply work for the client.
Work for the project. Work for the audience. Work for the craft. Work for the conversions.
When those things succeed, the client is far more likely to be happy with the result.
Own Your Decisions
A good designer should be able to explain why a decision exists.
Why this layout?
Why this hierarchy?
Why this CTA?
Why this typography?
Why this interaction?
Not every decision needs a 20-minute presentation, but it should have a reason beyond “I thought it looked nice.”
And when a client suggests something different, don’t immediately become defensive.
Ask what problem they’re trying to solve.
Sometimes they’re right.
Sometimes their suggestion reveals something you missed.
And sometimes you need to explain why another approach may work better.
That’s not resistance.
That’s design leadership.
Keep the Steering Wheel, but Listen to the Passenger
The best client relationships aren’t built on designers saying yes to everything.
They’re built on trust.
The client brings business knowledge. The designer brings expertise. Together, they make better decisions.
You don’t need to win every argument.
You need to help the project win.
And if the client still prefers a different direction, that’s okay. Explain the trade-offs, make the decision collaboratively, and keep moving.
But never stop caring about the outcome.
Because the real value of a designer isn’t simply knowing how to operate the tools.
It’s knowing which direction the project should take and why.
Own your designs. Respect your clients. Design for the people who will actually use what you create.
Because in the end, what sells is what sails.
#DesignThinking #UXDesign #UIDesign #ProductDesign #GraphicDesign #DesignStrategy #CreativeProcess #UserExperience #ClientManagement #DesignLeadership #ConversionDesign #HumanCenteredDesign
