The title was never the point
New job titles keep arriving, each with an argument about what it means. I stopped collecting them. What I did not stop doing was getting closer to the business.
UI Designer. UX Designer. Digital Product Designer. User Experience Designer. New titles keep arriving, and each one arrives with a small argument about what it really means. When I started, all of it felt overwhelming, and a little frustrating. I thought I was supposed to pick one and become it.
I settled on Digital Product Designer a long time ago, and I use it because it is the closest honest description of how I work. But the longer I do this, the less the label matters to me. I came up through graphic design. Branding, brand identity, packaging. I loved it, and I assumed for a while that design was mostly about how things look. It is not. It is about making something that works and actually reaches its goal.
I cannot look at UI and UX separately
Over the years I have sat in a lot of discussions and workshops about business needs, usually asking more questions than people expected. Sometimes the questions are uncomfortable. Sometimes a stakeholder assumes I am just curious. But the more I ask, and the more I read around the problem, the better the solution I can offer, for the company and for the person using the product.
A product designer is most useful at the very start, when things are still soft. That is when you can shape the options, feed into the strategy, keep the design honest against the roadmap. Get involved then, and everything that comes after is easier to scale.
Testing is not gambling
Continuous learning, experimentation, testing ideas early. None of that is optional in this job. You have to be willing to be challenged, and willing to challenge yourself. People sometimes treat testing an idea as a gamble. It is the opposite. It is how you replace an assumption with something you actually know, before it costs you.
Why I read about strategy
I started designing because I loved to illustrate. What I did not expect was how much I would enjoy being there from the birth of a project. Learning about product strategy, roadmapping, even a little product management, changed how I work. It let me make decisions with reasons behind them, prioritize honestly, ask better questions in research, and build information architecture that serves both the user and the business.
Digital product design was never only about the visuals. It is understanding what people need, understanding what the business needs, and staying curious enough to keep learning where those two meet. That is the part I keep.
So if I could pass one thing along: get close to the other teams. Learn a bit of their job. Study the business, the strategy, the way things get built. Most of the time you can turn that knowledge straight back into an experience that fits the person you are designing for.