Praise isn't proof

The fastest way to become a better designer is through a tight feedback loop. A mature design team gives you that by default, but having one early is usually a privilege.

I landed my first role working alongside a talented UX team in Cairo, straight out of university. It was something I took completely for granted: meeting daily, criticizing ideas, arguing over small details, and constantly pushing each other. I thought this was just how work happened. Until I talked to people just starting out.

Turns out, most early-career designers don't take solo roles because they want a massive challenge... Just a tough market with very limited options.

My concern with taking a solo path early on is that you haven't seen what good actually looks like in practice. On the job, you have to deliver prototypes, understand the business, convince stakeholders, and handle technical constraints. Simultaneously, you're doing an entire team's worth of background work alone: setting standards, catching edge cases, spotting your own blind spots.

Doing all of that in your first year is exhausting. But the real danger is using external approval as a substitute for quality. It's way too easy to mistake non-design validation for good work.

"The CEO loved the direction this morning."

"The presentation went well, nobody had any questions."

"The client sent a thank-you email for the quick turnaround."

None of those mean the design was good. They just mean it was convenient, easy to digest, or delivered on time. If praise is what tells you a project was successful, you've handed your standards over to people who don't know how to evaluate design.

Still, a solo role can be a huge opportunity. Getting real product experience and handling different responsibilities matures your business sense faster than almost anything else. But if you aren't careful, it pulls down your quality bar without you realizing it.

Taking the job is the easy part. Not stalling your growth is where the real work starts. If you don't have a design team around you, you have to build one yourself. Two engines do that.

The real-world engine, internal

Stop expecting non-designers to critique your typography, layout hierarchy, or micro-interactions. They can't, and expecting them to will only annoy both of you. Use them for what they actually know instead.

Walk engineers through your user flows so they can catch edge cases, missing states, and broken logic you missed. Defend your choices to PMs and founders using business metrics, conversion, and trade-offs, not visual aesthetics. Talk to support and sales regularly. They know exactly where real people get stuck because they deal with the complaints every day.

The craft engine, external

Your day job won't sharpen your execution on its own. You need something outside of work to protect your standards.

Make time for personal work outside of client projects, and delibirately compare your output directly against world-class work. If you don't benchmark yourself against the best, your current job becomes your ceiling.

Find two or three peers, not a massive Discord server, and meet regularly for raw design critiques. Reach out to practitioners you admire with specific questions instead of asking for generic mentorship. And write down your process. Putting your reasoning into words forces you to defend your logic the same way you would in a real design review.