If you need seventeen different skills just to get an entry-level job, maybe the problem isn't you.

A designer DMed me last week. Eight months of "upskilling." Figma masterclasses, design systems bootcamps, user research courses, prototyping workshops. She'd spent more time learning about design than actually practicing it.
"Think I'm ready to apply now?" she asked.
I scrolled through her list. Forty-three completed courses. Zero real projects.
That's when it hit me: we've built an entire fucking industry around convincing designers they're never good enough. There's always one more course, one more tool, one more certification before you're "ready."
Brilliant marketing. Complete bullshit.
Somewhere along the way, UX skills became products to sell instead of abilities to develop.
Every week there's a new "essential" skill you're supposedly missing. A new tool that's "revolutionizing" everything. A new methodology you "must" understand to stay relevant.
Last year it was design systems. This year it's AI prompting. Next year? Who gives a shit—there'll be something else.
The pitch is always the same: you're behind, everyone else knows this thing you don't, and here's a $399 course that'll save your career.
But here's what nobody mentions: most people selling these courses haven't worked on real product teams in years. They figured out teaching design pays better than doing it.
Look at any UX job posting. The requirements read like someone threw a design dictionary at a wall:
User research and usability testing
Information architecture and wireframing
Visual design and prototyping
Design systems and component libraries
HTML/CSS (plus maybe JavaScript)
Data analysis and A/B testing
Workshop facilitation and stakeholder management
Accessibility and inclusive design
Motion design and micro-interactions
Oh, and 3-5 years experience. For a "junior" role.
This isn't a job description. It's a fantasy wish list that would take a decade to master properly.
I know designers who spend more time in courses than actually designing. Their LinkedIn feeds are constant humble-brags: "Just completed Advanced Figma Mastery!" "Certified in Design Thinking!" "Learning Framer now!"
Always learning, never shipping.
Meanwhile, their peers who've been building real shit—even messy, imperfect shit—are getting hired and promoted.
The cruel part? The course-takers often have prettier portfolios. But portfolios aren't skills—they're just proof you can complete homework assignments.
Every few months there's a new design tool that'll "change everything." Remember Sketch? Then Figma? Now it's Framer, Webflow, ProtoPie, and whatever launched while I was typing this sentence.
Each tool spawns its own course ecosystem:
"Master Figma in 30 Days"
"Advanced Prototyping with Principle"
"AI-Powered Design with [Insert Tool Here]"
But tools aren't skills. They're just hammers. You don't become a better carpenter by collecting more hammers—you build more things with the ones you have.
The designers who succeed aren't the ones with the most certificates. They're the ones who can:
Solve real problems. Not textbook design challenges, but messy business problems with political constraints and impossible deadlines.
Communicate with humans. Stakeholders who think your research is "just opinions." Developers who say your design is "impossible." Users who just want the damn thing to work.
Ship imperfect things that get better through iteration, instead of perfect things that never see daylight.
Handle chaos. Because most design problems come with unclear requirements, changing goals, and not enough time to do proper research.
None of this shows up in courses. You learn it by doing real work with real consequences.
Course culture has created designers who make beautiful case studies but can't handle actual product work.
Their portfolios sound like fairy tales:
"I identified problems through extensive user research"
"I synthesized insights into actionable recommendations"
"I iterated based on usability feedback"
"The solution increased satisfaction by 40%"
Real design work sounds like:
"Marketing wanted another button on the homepage"
"Engineering said it would take six months to build"
"Legal flagged seventeen compliance issues"
"We shipped something that worked and fixed it later"
The first version gets you interviews. The second is how products actually get made.
Here's what determines whether you'll survive as a designer:
Political survival. How to get designs approved by people who make decisions based on what looks "more professional." How to pick battles when everyone thinks they're a designer. How to build allies without becoming a corporate sociopath.
Real psychology. Why people lie in user interviews. Why they click the wrong button even when the right one is obvious. Why they abandon forms one field away from completion and then complain the process is "too long."
Business literacy. How companies actually make money. Why great UX gets killed for quarterly metrics. What "technical debt" means and why it's always somehow your problem.
Emotional resilience. How to watch your best work get butchered in implementation and still show up tomorrow. How to present to people who've already decided what they want. How to take criticism of your work without taking it personally.
Want to know why these don't have courses? Because you can't simulate having your research ignored, your wireframes "improved" by committee, or your prototypes called "too complex" by someone who thinks a website should work like a brochure.
These skills are earned through real project work, where deadlines are impossible and requirements change daily.
The skills industry thrives on making you feel perpetually behind:
"AI is changing design forever—are you ready?" "The top 10 skills every designer needs in 2024"
"Why your design process is outdated (and how to fix it)"
This creates constant professional anxiety. No matter what you know, there's always something else you should be learning.
But here's the secret: most of those "essential" skills aren't actually essential. They're just marketing hooks to sell you another course.
Work on real projects. Volunteer for nonprofits. Freelance for small businesses. Redesign something you actually use and hate. The messier and more constrained, the better.
Find a mentor. Someone doing the work you want to do. Someone who'll give you honest feedback about what actually matters and what's just noise.
Start before you're ready. Apply for jobs you're not "qualified" for. Take on projects you don't know how to complete. Figure it out as you go—everyone else is doing the same thing.
Skip the courses. Read actual design system documentation from companies you admire. Join professional communities where people share real challenges, not course completion certificates.
Here's how to know if you actually have design skills: can you make someone's day slightly better through your design decisions?
Not "can you create a beautiful interface" or "can you use the latest prototyping tool."
Can you understand a real person's frustration with a real product and make it less frustrating?
That's the skill that matters. Everything else is just tools and processes in service of that goal.
And you can't learn it from a course. You can only develop it by trying, failing, learning, and trying again.
The UX skills industry wants to keep you in perpetual preparation mode. Always learning, never doing. Always behind, never ready.
But here's the truth: nobody's ever really ready. Everyone's figuring it out as they go.
The difference between designers with successful careers and people stuck in course-taking loops isn't the number of skills they've mastered.
It's that they started before they were ready and learned by doing real work on real problems with real consequences.
Stop buying courses. Start making things.
4
24
1