• Open Doors
  • Posts
  • Why User Personas Hurt Junior Portfolios (and What to Use Instead) 🙅🏻‍♂️

Why User Personas Hurt Junior Portfolios (and What to Use Instead) 🙅🏻‍♂️

Drop the stock-photo personas. Show real thinking with context, goals, and Jobs to Be Done — and make your case studies stand out.

In partnership with

Hey and welcome back to another week! đź‘‹ 

In this issue:

  • Why To Avoid Personas: When I open a portfolio and see a persona that’s rarely a good sign. Learn why and what to do instead.

  • Join Me For A Lovable Workshop: Tickets are selling FAST for this one and the last time it completely sold out. Learn how to use Lovable to create full apps and prototypes in no time.

  • Kate’s Portfolio: A multidisciplinary designers blending brand, UX and more.

💻️ VIBECODE WITH ME

Learn How To Use Lovable To Create Amazing Prototypes And Apps From Scratch

I already ran this workshop in August—and it sold out in a couple of days. I also learned a lot running it once. Now I’m back with another round. Make sure to book this one and learn how to leverage AI, vibecoding and a builder mindset to stand out.

This is what you get:

  • ​Build without code: Get hands-on with Lovable and turn your ideas into functional, interactive apps — without writing a single line of code.

  • ​Boost your prototyping edge: Master the fastest way to validate ideas, impress stakeholders, and iterate at the speed of creativity.

  • ​Premium tools to keep building: Every attendee gets 1 month Lovable Pro account with 100 credits to continue building after the workshop.

🤝 TODAY’S PARTNER

The Gold standard for AI news

AI keeps coming up at work, but you still don't get it?

That's exactly why 1M+ professionals working at Google, Meta, and OpenAI read Superhuman AI daily.

Here's what you get:

  • Daily AI news that matters for your career - Filtered from 1000s of sources so you know what affects your industry.

  • Step-by-step tutorials you can use immediately - Real prompts and workflows that solve actual business problems.

  • New AI tools tested and reviewed - We try everything to deliver tools that drive real results.

  • All in just 3 minutes a day

Why User Personas Hurt Junior Portfolios (and What to Use Instead) 🙅🏻‍♂️

If there’s one thing that screams “junior” in a portfolio, it’s user personas.

You’ve seen them: the neatly designed slides with stock-photo faces, quirky names, age ranges, favorite hobbies, maybe even a quote. They show up in nearly every bootcamp portfolio. And they add no value.

That may sound harsh, but it’s true. I’ve never once seen a persona in a junior portfolio that helped me understand the work better. At best, they’re filler. At worst, they make the whole project feel less credible.

Why Personas Don’t Work in Portfolios

This doesn’t mean personas are always useless. In large companies with research teams, personas can sometimes play a role. They’re the product of months or years of aggregated insights, built to guide product strategy across teams.

But that’s not what juniors are producing.

Bootcamp projects, fictional case studies, or small freelance gigs don’t have the scope or data to support a persona. Instead of surfacing real insight, these slides usually come across as made up. A stock photo plus a list of assumptions isn’t evidence — it’s theater.

The result: instead of making your case study feel more professional, personas often make it feel more like homework.

What Actually Matters: Context, Goals, and Tasks

If personas don’t add value, what should you show instead? The answer is simpler: context, user goals, and user tasks.

Hiring managers don’t care that “Maria, 32, loves yoga.” They care whether you can explain what real people are trying to do, what’s blocking them, and how your design helps.

Instead of a persona card, write something like:

“Users often struggled to complete a workout plan because the app made it hard to save progress mid-session.”

That single sentence communicates more value than a full persona deck. It’s grounded in actual goals and tasks, and it gives a clear line of sight into your design decisions.

Jobs To Be Done: A Better Framework

A stronger alternative to personas in your portfolio is the Jobs-to-be-Done (JTBD) framework.

The idea is simple: people don’t “buy” or “use” a product because of who they are demographically. They “hire” a product to get a specific job done in their life. The job isn’t just the task — it’s the outcome they’re aiming for.

The classic example: People don’t want a quarter-inch drill. They want a quarter-inch hole.

In design terms, that means instead of writing “Sophie is a 29-year-old teacher who enjoys crafts,” you’d articulate something like:

“Users hire this app to save and organize creative project ideas, so they can reduce time spent searching later and feel more in control.”

This framing is more powerful than personas because it connects directly to the why behind a design decision. It highlights the outcome people care about, not surface traits that don’t matter.

And importantly: JTBD is widely used in real companies — far more than lightweight personas. Using it in your case studies shows that you’re thinking in a way that translates directly to the workplace.

How to Uncover JTBD (Even for Fictional Work)

The best part: you don’t need a big research team to create useful JTBD statements.

If you can run interviews, ask simple questions: “What are you trying to accomplish? What gets in the way? What would make that easier?”

If you don’t have access to users, borrow insights from competitor reviews, app store comments, or Reddit threads. These often contain raw frustrations and desired outcomes in people’s own words.

From that, extract jobs:

  • Situation: the context users are in.

  • Job: what they want to accomplish.

  • Outcome: the benefit they’re really after.

Turn those into JTBD statements and use them as the backbone of your case study. Even in fictional work, this creates a through-line that makes your design decisions feel grounded and credible.

Wrapping Up

User personas in junior portfolios don’t help you. They take up space, they don’t add credibility, and they rarely show how you think.

Jobs To Be Done, on the other hand, do. They highlight real user motivations and outcomes in a way that directly informs design choices. And they show that you’re aware of frameworks companies actually use.

So if you’re working on your portfolio: drop the stock-photo personas. Replace them with clear JTBD statements or descriptions of goals and outcomes. You’ll make your case studies sharper, more grounded, and far more convincing.

đź‘€ Portfolio Showcase

Kate Nikles’ portfolio is a vibrant showcase of multidisciplinary craft with a strong pull toward product design.

An illustrator, animator, brand designer, and UI/UX designer, Kate brings a rare range of skills to the table. While her background and strengths clearly lie in visual design, branding, and illustration, her portfolio makes it equally clear that she’s moving with intent toward UX and UI work. What stands out most is how she carries her sense of style and craft across disciplines — whether in brand-heavy showcases, playful game UI, or more traditional product design projects.

For multidisciplinary designers (especially those moving into UX/UI from graphic, motion, or brand design), Kate’s portfolio is a strong example of how to balance breadth with focus. It’s not just a gallery of skills — it’s a curated surface that communicates personality, polish, and capability.

Let’s take a closer look at what makes this work — and where some tweaks could take it even further.

That’s it for this week—thanks so much for the support! ♥️

If you’d like to support my efforts on Open Doors further you can buy me a coffee. If you ever got any value from my emails consider it so I can keep this newsletter free and available to everyone out there.

Do you want your own portfolio reviewed in-depth with a 30-minute advice-packed video review? Or do you require mentoring to figure out a proper strategy for your job search?

I got you!

Keep kicking doors open and see you next week!
- Florian