Why adding more case studies hurts your chances


Why adding more case studies hurts your chances

Adding one more case study often feels productive. It feels safe, like you’re increasing your chances. In practice, it does the opposite.

More work increases surface area. It introduces noise. It gives reviewers more opportunities to hesitate, compare, and second-guess. Hiring decisions don’t improve with volume; they improve when the clarity of your decisions, trade-offs, and constraints is undeniable.

When I review portfolios, resumes, or case studies, I’m not looking for more artifacts, trendy interactions, or a complete log of everything you did during the design process. I’m asking myself a simple question: Can I trust this person’s decisions?

Trust doesn’t come from polish, or even effort. It comes from seeing that someone knows what matters, what doesn’t, and is willing to commit to that judgment.

This is where generic advice starts to break down. Templates help early on because they establish structure, but they don’t teach judgment. And at a certain level, judgment is the differentiator.

Two designers can follow the same advice, apply the same frameworks, and produce work of similar quality. The one who moves forward is almost always the one whose decisions are more clearly conveyed.

They’re explicit about which case study actually leads the story, which artifacts earn attention versus dilute it, and which choices demonstrate ownership rather than quietly weakening trust.

Designers who convert show less, but with clear intent.


If this resonates, and you feel like your work is strong but not converting the way it should, this is exactly the lens I bring into my 1:1 diagnostic sessions. I’m opening a small number of end-of-January sessions focused on clarifying judgment, tightening positioning, and removing ambiguity from how your work is being interpreted across resumes, case studies, and interviews.

You can find more information here.

David Campana
Founder, Level^Up
Head of UX | Ex-Apple, WeWork, Verizon

PS: These sessions are not portfolio redesigns or generic feedback. They’re focused on clarifying judgment, tightening your story, and removing ambiguity from how your work is actually being evaluated.

Elevate your skills. Grow your impact.

Level^Up explores how AI is transforming UX. Each issue dives into how to use AI to improve research, streamline design workflows, and stay ahead of the curve. Learn to design smarter, showcase your value, and grow your impact.

Read more from Elevate your skills. Grow your impact.

There was a time when having solid work was enough. That time is over. Hiring decisions today are made under pressure: more candidates, less time, and far less tolerance for ambiguity. Strong work is still essential.It’s just no longer sufficient. If hiring managers can’t quickly tell: what kind of designer you are what you can be trusted with whether you’re operating at a senior level we move on, even when the work itself is solid. Not because you're unqualified, but because their story...

Strong UX work. Still no interviews? Here’s what to cut. Everyone in my last cohort had strong work.Every single one of them was still stuck. Not because they didn’t know how to write a resume. Not because their case studies were weak. Not because they lacked experience. They were stuck because they hadn’t made a few uncomfortable decisions yet. What kept showing up Across the first two live sessions, the same patterns repeated: Too many artifacts competing for attention Consulting experience...

Vague feedback is why good work stalls Vague feedback feels kind, but it slows everything down. Feedback stops being useful when it avoids a decision. Over the past week, nearly every conversation I’ve had has pointed to the same pattern: work that’s technically strong, but isn’t communicated clearly. Not because the work is weak, but because the feedback around it never forces an action. Direct feedback isn’t harsh. It’s specific. It names what needs to change. And that's what moves work...