10 Truths Every Product Designer Must Know

10 strong facts in which they will not be included in the posting of the job

I was on the cloud nine when I got my first job as a product designer.

Adobe XD launched. The headphone is playing my reliable spotphone playlist and a folder full of UI inspiration in hand. I was ready to do magic, you know-surprising interface, silk smooth dynamic images, pixel perfect precision precision original user issues.

But within weeks, the dream began to spread.

This was not the work. It was an integration that no one teaches you what to do:
Endless meetings, ambiguous requirements, choice of lost design in translation, and the intestinal blow (sometimes unfairly) seeing your work torn.

And slowly, I noticed that the design is not about to look beautiful.

It’s about working through chaos. Clear explanation compromise with grace. Taking successes. Molding at the speed of electricity. And still – somehow – believe in work.

This post is the interpretation of the 10 strict facts I have learned – sometimes difficult – as a working product designer.

If you are a new noob for all of them or even if you are a few years, I hope it saw you a little more, ready a little more, and just felt too little.

1. In a bad meeting, the great design can die

You can produce the best thinking design in the universe-based on real data, Pixel is configured, Edge cases have been configured…

But suppose that this meeting is being demonstrated that it is facing the direction, it changes an uncontrollable stakeholder, or unexpected scope?

Poof it is gone.

What did I learn? Don’t just make a product – make your work story. Your ability to speak is as strong as you have the ability to make.

2. You’ll spend more time more than making your design reality

I thought the work was: creation, present, ship.

In real life, this is: Make, explain, clarify, modify, explain, align, align, align it again, then ship.

This is not a grip – it’s a reminder. Good design is not just about design. Communication, patience and repetition stories are involved.

3. Developer does not hate designers – they hate vague hands -off

I believed that Davis was “anti -design” because he struggled so hard against it.

As it turns out, they were merely confused, fed up with incomplete edge matters, or ambiguous intentions. When I began to put context comments, leisure guidelines, and better documents – our relationship improved.

Respect is mutual. There is confidence in the clear generation.

4. Users are more concerned than your visual aesthetic solving your problem

We are a combination of fonts and grades.
But your user? They just want to book a taxi, track the order, or fill the form without any trap.

The design is not about happiness. It’s about use.
The user who can give the greatest definition is “It Looks Good” – It “It was easy.”

5. You will design the same screen 10 times – and it’s ok

If I had to do something, I would be angry in my childhood.

Now I realize: Every repetition taught me something.
That dropdown did you work again 4 times? Each repetition reduced the friction. Each repetition made the experience easier.

Repeat is not a failure. This is a breakthrough.

6. You will learn to distinguish between feedback and your identity

The first time someone said, “It doesn’t work,” I didn’t feel like I’ve worked.

But you prepare a good detachment over time. Criticism is not personally about you – it’s about work. And sometimes the most difficult criticism helps you change quickly.

Your job is not your role. Look at your skills, not your ego.

7. Good UI won’t save a damaged UX you cannot lipstick to the pig.

Clean UI can draw attention, but if consumers are lost in the middle or can’t find their needs – they are gone.

The world’s most beautiful button is useless if it doesn’t go anywhere. The form should follow the function.

8. Your product manager will reflect your strength and weaknesses

The Prime Minister is not your enemy. They are your best ally.

If they do not think you can fix things, they will make micro management to Minato. But if you walk with research, reason and design thinking? They will sit behind and let you drive.

How do you work out how you are treated.

9. 80 % Solving problems, 20 % Pixels

This Ravi was the biggest change in attitude.

At first I was convinced that my job was to look good. In fact, my job is to find things. It’s a flow that is disappointing to consumers or the process that is flourished – you are there to fix it.

And this starts long before the first screen appears.

10. The humble degree makes irrelevant

I have worked with “juniors” who asked better questions from “seniors”.

I have faced “leads” who are unable to describe the design intentions and the minds have blown up.

The actual benefits? They are constantly learning, making permanent improvement, constantly listening. Not in the name. It’s in your mind.

The final views

The purpose of this article is not to frighten anyone. The purpose is that a valid picture of this work is really like.

If you currently face any of these obstacles, understand this:

You are not behind, you are growing.

You’re not doing so bad. You are getting better

You are not alone.

And if he talks to you, move it forward. Someone is looking for this thing in a difficult way, just as we did.