In many product teams, key decisions are made between a business analyst and a developer. The designer joins later — once everything has already been defined and it’s time to “make the interface look good.”
The problem is: from the user’s perspective, that’s already too late.

Designing without designing

At first glance, this may seem like efficient collaboration. In reality, the designer is reduced to an executor — someone who simply visualizes decisions that have already been made.
No brief. No context. No insight into how users will actually interact with the product.

But real design isn’t about drawing screens.
It’s about making decisions that directly shape how people use — or abandon — a tool.

The cost of bypassing UX

When UX is excluded, it’s not just the designer who loses.
The user pays the price:

– Because no one asked whether the solution is intuitive.
– Because the system logic was created without considering the real-world workflow.
– Because there was no moment of validation before development.
– Because the interface was designed to be built — not to be used.

All of this leads to frustration, mistakes, excessive onboarding, or worse: users avoiding the tool entirely.

Design isn’t aesthetics. It’s a structure of decisions.

Design doesn’t start with colors.
It starts with questions like:
– What does the user want to accomplish?
– What do they need to understand before they can act?
– Where are the risks for error — and how can we prevent them?

UX is a decision-making layer.
It designs the way a system works, not just how it looks.
When introduced too late, it can only minimize damage.
When invited early, it can prevent problems before they arise.

How to tell when UX has been left out

1. The designer is tasked with something without knowing who the user is.
2. Functional decisions were already made — without UX involved.
3. A mockup is expected, but no one has time to answer design-related questions.

What you can do differently — starting now

– Invite the designer to analyst–developer meetings — even just to listen in.
– Share a simple brief: goal, target user, constraints, and technical limits.
– Leave room for questions — before jumping into screens.

Good interface decisions don’t happen by accident

UI decisions are made whether or not there’s a designer in the room.
But when UX is missing, those decisions tend to be inconsistent, unvalidated, or random.
And it’s the user who ends up dealing with the consequences.