I became a senior designer the slow way — through repetition, feedback, failure, and time. Looking at the current hiring market, I wonder how many of the junior designers working today will have the same opportunity. The conditions that made me are disappearing.
I have been working in design for sixteen years. In that time I have been a junior designer who made expensive mistakes, a mid-level designer who started to understand patterns, and eventually a senior designer who can look at a complex problem and have a reasonable sense of where the real difficulty lives. That progression was not inevitable. It required specific conditions — conditions that I see fewer and fewer organizations creating today.
The conversation about the 'talent shortage' in UX frustrates me because it consistently misdiagnoses the problem. There is no shortage of people who want to work in design. There is a shortage of the investment required to develop them into the experienced practitioners companies say they need. Those are different problems with different solutions, and conflating them lets organizations off the hook for a situation they are actively creating.
I did not become a senior designer because I was talented. I became one because I had enough repetitions on hard problems, with people willing to tell me what I was missing. That combination is rarer than it should be.
— Roy Villasana
What Actually Produced My Seniority
When I think honestly about what made the difference in my development as a designer, it comes down to a small number of conditions that I did not appreciate at the time but recognize clearly in retrospect.
Ownership of end-to-end work. The projects where I grew the most were the ones where I was responsible for the entire experience — from research and problem definition through to design, delivery, and measuring what happened afterward. The projects where I was a supporting contributor on a senior-led initiative taught me less, even when the work was more sophisticated. Ownership is the learning mechanism. Support is not.
Feedback that connected decisions to outcomes. The best mentorship I received was never about what looked better or what followed convention. It was about consequences — 'if you structure the information this way, users will misread the hierarchy, and here is how I know that.' That kind of feedback is only possible from someone who has made similar decisions and can trace their effects. It requires investment from experienced practitioners that many organizations are not structuring into their teams.
Environments where failure had a cost but not a catastrophe. I learned the most from projects that did not go perfectly — where something I designed confused users, where a decision I made created engineering problems, where the research I skipped came back as a support ticket pattern. Those failures were expensive in small ways and priceless in the learning they produced. Environments engineered to prevent all failure also prevent this category of learning.
What the Current Market Is Optimizing For Instead
The contemporary design hiring market has been consistently moving in the opposite direction from these conditions. Junior and mid-level positions are posted less frequently than senior positions. When they do exist, they are often structured as support roles rather than ownership roles — which eliminates the primary learning mechanism. Design mentorship is treated as a nice-to-have rather than a structural part of how teams operate.
The result is a generation of junior and mid-level designers who have impressive portfolios — because the tools for producing good-looking work have never been more accessible — and less practical problem-solving experience than they would have accumulated in an earlier era. The gap between what looks senior and what is senior has widened in ways that create real problems once these designers are in the room with a genuinely complex product challenge.
What I Try to Do Differently With My Own Team
I am not writing this from a position of having solved the problem. But I am aware of it, and awareness shapes choices. A few things I try to do consistently when I have the opportunity to influence how a design team operates:
- Give junior and mid-level designers ownership, then support them. The structure should be: you are responsible for this, and I am here when you need me — not: I am responsible for this, and you are here to help. The first structure produces growth. The second produces skilled assistants.
- Make the reasoning behind feedback explicit. When I tell someone their design has a problem, I try to explain the underlying principle and the evidence behind it, not just the correction. The correction fixes one design. The principle improves every design that comes after it.
- Create space for honest post-mortems. When something does not work — a design that tested poorly, a decision that created problems downstream — I try to treat it as material for learning rather than something to move past quickly. The organizations that improve fastest are the ones that extract the most learning from their failures.
The Long View
Seniority in design is not primarily a function of years. It is a function of accumulated problem contexts — the variety of challenges you have owned, the range of failures you have recovered from, the breadth of feedback you have internalized. Those contexts cannot be acquired by hiring your way to a senior-heavy team. They can only be built by creating the conditions for people to develop them.
The teams that will be genuinely strong five years from now are the ones investing in that development today, accepting the short-term cost of slower output and more frequent iteration in exchange for the long-term asset of practitioners who actually know what they are doing. It is not a complicated trade. It is just a patient one.
Keywords
senior UX designer, UX career path, design mentorship, design talent development, junior designer growth, design leadership, product design career, design team building, UX experience, design management