Two junior designers can have almost the same level of experience.
Both are learning.
Both make mistakes.
Both don’t know everything.
But there’s one important difference:
How they respond when they don’t know what to do.
When a Project Starts
One junior says:
“Tell me what to design.”
Another asks:
“What problem are we trying to solve?”
It sounds like a small difference.
It isn’t.
One is waiting for a solution.
The other is trying to understand the problem first.
When They’re Stuck
Being stuck isn’t the problem.
Staying stuck without investigating is.
Instead of:
“I don’t know what to do.”
Try:
“Here’s what I’ve tried. I’m stuck between these two directions. Can we talk through them?”
This gives your team something to work with.
You’ve already explored the problem.
You’ve identified where you’re uncertain.
Now you’re asking for help with a specific decision.
When You Need Feedback
There’s a big difference between:
“Can you review my design?”
and:
“I’m unsure about these two decisions. Which direction makes more sense given our goal?”
Good feedback becomes easier when you provide:
Context + A specific question + A reason for the decision.
Don’t just ask for feedback.
Make feedback easier to give.
When You Don’t Have Experience
You don’t need to pretend you know everything.
Instead, say:
“I haven’t worked on this before. Here’s what I’ve learned from similar projects. Here’s how I’d approach it.”
Acknowledge the gap.
Show what you know.
Explain your approach.
That demonstrates curiosity and initiative without pretending to have experience you don’t have.
When You Make a Mistake
A mistake isn’t automatically experience.
It becomes experience when you learn from it.
Instead of:
“I got it wrong.”
Try:
“This didn’t work. Here’s what I learned. Here’s what I’d change next time.”
Don’t hide the mistake.
Understand it.
When You Receive Critique
Critique isn’t simply:
“I like it.”
“I don’t like it.”
Instead, try to understand:
- What is the concern?
- What evidence supports it?
- What constraint are we working with?
- What should change?
You don’t need to defend every pixel.
You need to understand the reasoning behind the feedback.
The Real Difference
The difference isn’t:
5 Figma certificates vs. 10 UX courses.
It’s:
PASSIVE → ACTIVE
“Tell me what to do.”
→ “What problem are we solving?”
“I don’t know.”
→ “Here’s what I’ve tried.”
“I need feedback.”
→ “Here’s what I’m unsure about.”
“I don’t have experience.”
→ “Here’s what I’ve learned.”
“They rejected my idea.”
→ “What can I learn from that?”
That’s how experience starts to compound.
The Junior Designer Growth Loop
Don’t just collect knowledge.
ASK
↓
TRY
↓
GET FEEDBACK
↓
REFLECT
↓
IMPROVE
↓
TRY AGAIN
Every project becomes another opportunity to practise thinking.
That’s how knowledge becomes experience.
A Simple Checklist
Before asking for help, try to:
- Understand the problem
- Identify what you already know
- Research what you don’t
- Try a first approach
- Explain your reasoning
- Identify where you’re stuck
- Ask a specific question
- Listen to the feedback
- Apply what you learned
- Document the lesson
You don’t have to have all the answers.
Show how you’re thinking.
You’re Allowed Not to Know
One of the most important things juniors don’t hear enough:
You are allowed to not know.
You’re junior.
You’re supposed to be learning.
The goal isn’t to walk into every project saying:
“I know exactly what to do.”
It’s being able to say:
“I don’t know yet. Here’s what I’ve figured out so far.”
Curiosity + initiative + reflection can take you much further than pretending to know everything.
Become the Designer Who Can Figure Things Out
Don’t try to look like a designer who knows everything.
Become the designer who knows how to figure things out.
Your first job won’t teach you everything.
No course will either.
Projects will.
Questions will.
Feedback will.
Mistakes will.
Reflection will.
You don’t need the whole answer.
Bring your thinking to the table.
Comments