Designing for users or designers?

I've collaborated with an innumerable quantity of designers in the last couple of years.

Oct 28, 2018 · 2 min read

It’s surprising how many of them try to skip User Research in their processes. Developing features without a clear understanding of what problem this product is solving, it’s more often than not, a mistake. The problem is that they distance themselves from what the users need and what the people would potentially love.

I usually hear people say:

Hey, let me put this button here because other apps have something similar or because I have already made the same in other projects

… And this is a bad approach many designers take.

Instead of developing outermost features, I’ve learned to work directly with the user as a partner. To understand the problem from the user’s point of view. This helps me to evaluate if the solutions I propose will please the user's needs. Then I will be able to create a product they will love.

“For your product to be successful it needs to please everybody, and for that, you need to know your users well enough to make a product they will love”

Someone once said to me that work without users is like making clothes for someone you don’t know the size of. Maybe they’re kids or elders, maybe they are not experts on some topics as you are. For that reason, your job as a designer always will be to make sure you know well enough the users you’re designing for, rather than start designing something that only experts in the design field can understand.

The design doesn’t about take the client brief and start to place some rectangles on the screen. The design is about asking questions, working together with users, and being open to new directions. Be aware of this to create a satisfying experience for the people who will use your product.

"Let’s the user needs driving your process ❤"

Thank you for reading! I hope you find it useful.

Other writing

Dear Designer, Don’t Be Fragile
Working Hand In Hand With Clients