Make the First Months Count
Once you land that first junior UX role, the work is only beginning. The designers who advance fastest aren't necessarily the most talented — they're the ones who are deliberate about how they spend their early months on the job.
A useful mental model here is the Pareto principle: roughly 20% of your efforts will produce 80% of your growth. The trick is figuring out which activities belong in that 20%. The advice below comes from fifteen years of hiring and working alongside designers, and it's aimed at exactly those first critical months.
Don't Wait to Be Noticed — Go Find Harder Work
The passive approach to career growth is simple: do your assigned tasks well, and eventually a manager will notice and hand you something more complex. In practice, that wait can last a long time, because most people are too focused on their own work to track your development closely.
Instead of waiting, actively seek out challenges. This feels uncomfortable at first, but it's worth remembering that the designers who created the frameworks and patterns you study today were working from intuition before anyone documented those approaches. Pick a skill you want to build, spend a day researching it, find a real problem to apply it to, and practice. Then share what you made and ask for feedback. After a few rounds of this, you'll likely be trusted with real tasks in that area.
Train Yourself to See Interfaces the Way a Designer Does
Every interface you use daily is a lesson in design history. The Amazon homepage, for instance, didn't arrive at its current form overnight — it evolved over many years through countless iterations and user tests. You've been a participant in that evolution all along: you've registered for accounts, reset passwords, filled out forms, and clicked through onboarding flows.
Most of the tasks you'll receive early in your career will rely on established UX patterns. You don't need to invent new ones; you need to consciously study what already works. While using any app or website, ask yourself:
- Why was this element designed this way?
- What's unclear to me as a user?
- What's well thought out, and what falls short?
The best design solutions were built on sound reasoning, then written up so others could reuse that knowledge. You can develop that same reasoning by paying closer attention to every interface you encounter — noting what works, understanding why, and applying those lessons to your own work. A structured resource like the Smart Interface Design Patterns course by Vitaly Friedman is also helpful here: it covers guidelines for common components across modern interfaces, from navigation to forms, so you can rely on proven solutions rather than reinventing the wheel for every project.
Practice Explaining Your Work
Design is only half the job — the other half is communication. Your ability to articulate complex ideas in clear language determines how effectively you collaborate with stakeholders, developers, and other designers. This is a lifelong skill that extends beyond work.
Communication fundamentally comes down to sharing ideas as clearly as possible, and like any skill, it improves with deliberate practice. One exercise: describe a project you're working on to a friend in a way that keeps them engaged. If they're asking follow-up questions instead of changing the subject, you're on the right track.
Ask for Feedback Before You're Told
Annual performance reviews are too infrequent to guide your development meaningfully. Seek feedback proactively, and often. When you ask, make it easy for people to be honest by acknowledging your own weak areas first and inviting their impressions. Push for specifics — ask what they'd recommend to improve, not just whether something was good or bad. And when you act on someone's advice, let them know. There's no better way to show gratitude for honest feedback than demonstrating that it made a difference.
Learn to Speak Business Before You Speak Process
A common frustration among designers is that clients don't want to follow the full UX playbook — personas, information architecture, journey maps. Often that's not because the methods lack value but because the approach doesn't fit the project's real constraints. Clients may not have time or budget, or the designer may simply fail to explain why the process matters.
Either way, it's worth remembering that many successful products were built before these frameworks existed — what came first was common sense and iteration. So before you insist on any particular methodology, ask what the goal actually is and think about the most efficient path to get there. Learn how the underlying business works, and communicate value in terms stakeholders understand, rather than pushing a specific tool or framework. As Jared Spool puts it, good UX is where value enters the picture — when a product shifts from a poor experience to a good one.
Don't Neglect the Visual Layer
User experience matters first, but aesthetics matter too. Clients can't always see the reasoning behind your UX decisions, but they can always judge whether an interface looks good. Learn composition, color theory, typography, and how to work with illustrations and icons — then apply that knowledge relentlessly.
One effective exercise: pick a beautifully designed interface, study a single screen, then recreate it from memory without looking. Compare your version with the original and refine until they're close. The process will force you to notice details you never registered before and understand why the original was constructed the way it was.
Make It Easy for Others to Work With You
Junior designers save everyone time when they're organized from day one. Before starting a new task, prepare questions and don't forget to ask about deadlines. Establish a plan and align on the expected number of iterations so people always know what's coming. When questions arise during the day, search first for answers online — if nothing else, you'll learn how to frame better questions. Then check in with teammates periodically, but don't overwhelm them.
Getting comfortable gathering your own information matters because eventually you'll receive tasks directly from customers, and knowing how to fetch what you need is a fundamental skill.
Structure Your Learning Path
In the early days it's easy to feel like every UX article is essential reading. Trying to consume them all in no particular order will lead to information overload. Instead, find a mentor to help you structure a learning plan. If that isn't possible, find a reputable UX course — whether you pay it or not — and work through its curriculum topic by topic. A structured list, ordered from fundamental to advanced, is also practical for filtering articles as you encounter them.
If you're learning independently, resources like those compiled in these options are worth exploring:
- A selection of free UX design courses, including certification options compiled by Cheshta Dua, covering courses that helped a practicing designer get started.
- A comparison of free UX design courses for 2024 by Cynthia Vinney at the UX Design Institute, covering both online and in-person formats.
- The 10 Best Free UX Design Courses in 2024 by Rachel Meltze at CareerFoundry — covering UX fundamentals, tooling, and career paths.
- HTML/CSS Basics from Geoff Graham — an entry point for front-end fundamentals, ideal for designers wanting to build or refresh coding skills.
The junior years are precious — they're the time when growth compounds fastest. Focus your energy on these high-leverage habits, and the progression you're hoping for will arrive sooner than you think.
Practice Turns Knowledge Into Skill
Reading about new UX approaches is not the same as being able to apply them. The brain continuously clears out information it deems unnecessary, so the only way to signal that newly learned material is essential is to actively use it. Practice is what converts passive knowledge into a skill you can reliably call on.
The popularized “10,000-hour rule” from Malcolm Gladwell’s Outliers suggests that mastery of complex skills requires roughly 10,000 hours of intensive practice. Later research, however, complicates that picture: someone can practice for thousands of hours and still be outperformed by a less experienced peer — if that peer had a teacher who showed them what to focus on at a critical point in their learning.
That reinforces the earlier advice about seeking a mentor. Practicing with a good teacher and a clear plan tends to produce better results than practicing alone without direction.
There Is No Single Correct Process
There is no absolute criterion for what counts as “done properly” in design. You can follow every step of the classical design process and still end up with a product that fails in the market. Conversely, a team can skip standard phases, ship a minimum viable product quickly, and dominate.
The first iPhone is a well-known example. Seventeen years ago it launched without even basic copy-and-paste functionality, yet it reshaped the market. The engineers and designers understood the core product concept well enough to release something incomplete but compelling. Countless other successful MVPs from small startups follow the same pattern.
The lesson is not to abandon process but to stay pragmatic. Read widely, watch tutorials, study design theory, test different approaches, and talk to people using your product — even an early alpha or beta version. But at every step, ask whether the approach is the most efficient way to deliver value and achieve results. If it is not, revise the plan. Things do not happen on their own; people make them happen.
You are responsible for your own trajectory. No one else will care about your success more than you do. Do your best, make corrections, iterate, and keep learning.
Further Reading
- “Why Designers Aren’t Understood,” by Vitaly Friedman (Smashing Magazine)
Practical workarounds for running UX research when access to users is limited or unavailable. - “UXchallenge,” by Yachin You
A resource for learning to solve real customer problems and presenting related case studies. - “Kano analysis: The Kano model explained” (Qualtrics)
An overview of how Kano analysis, also known as the “Customer Delight vs. Implementation Investment” approach, helps improve products based on customer emotions. - “Kano Model: What It Is & How to Use It to Increase Customer Satisfaction,” (Userpilot)
Covers the history of the Kano model, practical explanations of how it works, five categories of customer reactions, and a four-step process for analysis. - “The Pareto Principle,” (Investopedia)
Explains the concept that 80% of consequences come from 20% of causes, also known as the Pareto Rule or the 80/20 Rule. - “Figma Portfolio Templates & Examples,” (UX Crush)
A curated list of portfolio templates for Figma. - “How to Define a User Persona,” by Raven Veal (CareerFoundry)
Guidance on using user personas as a tool during user research to create more human-friendly experiences. - “How to design a customer journey map,” by Emily Stevens (UX Design Institute)
A guide to creating visual representations of user interactions with your product. - “Building Components For Consumption, Not Complexity” (Part 1, Part 2), by Luis Ouriach (Smashing Magazine)
Advice on design systems, including team adoption, naming conventions, auto-layout, and component indexing. - “Effective Communication For Everyday Meetings,” by Andrii Zhdan (Smashing Magazine)
A step-by-step guide to structuring productive meetings and sticking to the original plan. - “The Value of Great UX,” by Jared Spool
Discusses how value emerges when a product moves from delivering a poor experience to a good one. - “How Designers Should Ask For (And Receive) High-Quality Feedback,” by Andy Budd (Smashing Magazine)
Suggests framing the problem clearly rather than presenting a linear case study of every design revision. - “Designing A Better Design Handoff File In Figma,” by Ben Shih (Smashing Magazine)
Tips for improving the design-to-development handoff process with better communication, documentation, and version control. - “The HTML/CSS Basics (.dev),” by Geoff Graham
An online course covering basic front-end development principles focused on HTML and CSS. - “Selection of free UX design courses, including those offering certifications,” by Cheshta Dua
A personal selection of free UX design courses. - “Best free UX design courses — 2024,” by Cynthia Vinney (UX Design Institute)
A comparison of free UX design courses available online and in-person. - “The 10 Best Free UX Design Courses in 2024,” by Rachel Meltze (CareerFoundry)
A range of free courses from micro-tutorials to full UX/UI programs. - “Researcher Behind ‘10,000-Hour Rule’ Says Good Teaching Matters, Not Just Practice,” by Jeffrey Young (EdSurge Magazine)
A study finding that the quality of a student’s teacher is a critical variable Gladwell originally overlooked. - “An Apple engineer details why the first iPhone didn’t have copy and paste,” by Filipe Espósito (9to5Mac)
Former Apple software engineer Ken Kocienda explains why the original iPhone shipped without those features. - “Fifteen examples of successful MVPs,” by Ross Krawczyk (RST Software)
Examples of startups that reached the market quickly by shipping the right key features in a minimum viable product.
