- Open Doors
- Posts
- Your Case Studies Might Be Losing You Interviews đ¨
Your Case Studies Might Be Losing You Interviews đ¨
Hereâs how to make them scan-friendlyâand what to cut or condense

Together with

Hey and welcome back to another week! đ
Super sorry about last weekâs hiccup. Maybe you didnât notice but the subject of last weeks issue wasnât matching the article in the issue. I was on vacation and might have had one too many Margaritaâs before scheduling the issue.
Iâm back in full swing this week though and actually my workshop is not only fast approaching (June 10) but also starting to run low on spots. Make sure to save your spot today to learn how to properly position yourself. Use the code UXCEL10 to save 10% on your ticket.
In this issue:
Not Getting Any Interviews?: Most of the time itâs your portfolioâor more precisely: your case studies. Letâs have a look at them.
Annabelleâs Portfolio: A designer who shows how to think business-minded.
đ¤ TODAYâS PARTNER
Your UX/UI Career Starts HereâLand Your First Job with the Right Resources
Struggling to break into UX/UI? The path from portfolio to paycheck doesnât have to be lonely. Thousands of designers like you are landing jobs by leveraging the right connections and resources.
Download the free UX/UI Hub app and youâll get:
Easy access to Open Doors handpicked junior UX/UI job opportunities
Direct connections to industry experts and fellow designers
Curated resources from design leaders whoâve shaped the industry
Weekly new events and workshops to boost your career
Exclusive discounts on premium UX tools and courses (up to 50% off)
A thriving community of 3,300+ designers at all career stages
Donât just take our word for it:
âMany events, great way to connect with fellow designers, industry experts inputs and opinions, easy to find and apply for jobs and find incredible resources.â - Prajwal M P
Get free access to the UX/UI Hubâđ 100% free. Start exploring today.
Your Case Studies Might Be Losing You Interviews đ¨

If youâve ever spent days (or weeks) crafting a portfolio case study only to feel like itâs still being ignoredâthis oneâs for you.
Itâs not that your story isnât worth telling. But most junior and early-career designers go too deep, too soon, in ways that overwhelm or confuse readers. And in a world where your portfolio might only get two minutes of attentionâif thatâhow you structure your story is everything.
Letâs fix that.
The Scan Test: How Case Studies Are Actually Read
Before we dive into what to cut, itâs worth stepping into the shoes of a recruiter or hiring manager.
Theyâre not reading your case study. Theyâre skimming itâlooking for signals: Do you understand real-world problems? Can you solve them? And do you make an impact?
Tools like Hotjar or Microsoft Clarity show this behavior in actionâthrough session recordings, cursor heatmaps, and time-on-page tracking. If youâre seeing readers drop off after 10 seconds or barely scroll past the hero section, thatâs a red flag. (I covered how to use these tools to analyze your own portfolio in more depth here.)
But even if youâre not using analytics, thereâs a simple test you can run:
The 1-Minute Scan Test
Ask a friend, mentor, or even a stranger to scroll through your case study for just one minute. Then, ask them two questions:
What was the project about?
What do you remember most?
If they spent the full minute reading and canât recall the core outcome, itâs too dense.
If they scrolled through everything and didnât retain anything meaningful, itâs too vague.
Your case study should pass both tests: engaging visuals + clear, memorable takeaways.
What to IncludeâAnd Where to Stay High-Level
Letâs get practical. Below are the core sections to focus on, with guidance on where to go deep and where to keep things short.
1. The Hook (Go DeepâBut Stay Sharp)
Start with a clear summary: what was the challenge, what did you do, and what changed?
Do:
Lead with measurable outcomes
Include a strong visual or animated preview
Make it obvious why this case study matters
Avoid:
Leading with long backstories or generic project titles
Burying results at the bottom
2. The Problem (High-Level)
Yes, context matters. No, we donât need the entire org chart or every stakeholder pain point.
Do:
Summarize the business problem or user friction clearly
Keep it under a short paragraph or visual
Avoid:
Paragraphs of backstory
Overly detailed personas or interview plans
3. Your Process (Only the Highlights)
Hereâs where many portfolios balloon.
Do:
List out your methodsâbut highlight only 1â2 turning points
Focus on where your thinking moved the project forward
Summarize research takeaways or usability findings
Avoid:
Full test scripts or question sets
Iteration logs that read like journals
Screenshots of entire spreadsheets
4. Visuals (Show, Donât Stack)
Think of visuals as narrative toolsânot decoration.
Do:
Use annotated flows, comparisons, or single standout screens
Add short captions for context
Avoid:
Long rows of UI screens with no explanation
Misaligned or low-res mockups
Using visuals that donât add clarity
đĄ Replace static screen dumps with GIFs or short videos (e.g. using tools like Content Core, Jitter, or Cap) to demonstrate a flow. Itâs more engaging and gives a better sense of what youâve built.
5. Outcomes & Reflection (Go Deep Again)
This section is often overlookedâbut itâs the one people remember.
Do:
Share tangible results (percentages, feedback, validation)
Reflect on what you learned and what youâd do differently next time
Avoid:
Generic learnings (âCommunication mattersâ)
Skipping this section completely
Bonus: Are You Telling the Right Story?
Even if your case study is clean and scannable, it might not be the right story for the roles you want.
Letâs say your ideal roles involve enterprise dashboards and data-heavy workflowsâbut your portfolio is filled with consumer-facing mobile apps like fitness trackers and pet care tools. That mismatch can quietly disqualify you.
Your case studies should reflect the kind of work you want to doâand show youâre thinking at the right level of complexity. If not, itâs worth prioritizing a project that bridges the gap.
TL;DR
Cut the fluff. Keep the flow. Focus on clarity and signal.
Lead with outcome and clarity
Summarize process, donât document it
Show fewer, better visuals
Run the 1-minute scan test
Use tools like Hotjar or Clarity to track drop-off
Great case studies donât just tell the story. They let the viewer absorb itâquickly, confidently, and with zero friction.
Let me know if youâd like to prep visuals or callouts for this oneâIâm happy to help structure the visual examples if you send them my way.
𦾠MY FAVORITE AI NEWSLETTER
Learn how to make AI work for you
AI wonât take your job, but a person using AI might. Thatâs why 1,000,000+ professionals read The Rundown AI â the free newsletter that keeps you updated on the latest AI news and teaches you how to use it in just 5 minutes a day.
đ Portfolio Showcase

Today: Annabelle Wieland
Annabelleâs portfolio is a great example of a junior designer who isnât afraid to go deep â and that alone makes it worth your time.
Based in London, Annabelle brings a strong sense of curiosity and rigour to her work. She doesnât stop at surface-level observations â she digs into how products are used, where user pain points intersect with business impact, and how design can meaningfully address both.
That kind of mindset is already rare at the junior level. With a bit more polish and refinement in how her work is presented, this portfolio could really shine.
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!
Book a mentoring session with me
Book a quick 15 min chat to ask a question and see if we vibe

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