Building a strong UX portfolio for graduate school starts long before you open Figma. Whether you’re applying to an HCI, Information Science, UX Design, or MDes program, a UX portfolio graduate school reviewers actually notice works differently from what most applicants expect. Choosing the right projects, deciding the order, and figuring out how to present your thinking — it’s an intense process. But the way reviewers evaluate a UX portfolio graduate school applicants submit is more specific than you might think. This guide breaks down exactly what they’re looking for and how to give it to them.
What UX Portfolio Graduate School Reviewers Actually Look For First
The people reviewing UX graduate portfolios are typically design researchers, interaction designers, and HCI faculty. Across programs, they’re looking for the same thing first: how does this applicant define and work through a problem?
The quality of your thinking matters more than the polish of your outcomes. A single case study that clearly shows why you chose a problem, how you moved through the process, and what decisions you made along the way will outperform ten beautifully designed UI screens with no context behind them. This is the most important thing to understand about what makes a UX portfolio graduate school reviewers respond to.
Case Studies Are the Core of Your UX Portfolio for Graduate School
The foundation of a strong UX portfolio graduate school application is the case study — a project presented as a complete story from beginning to end. A well-structured case study follows this flow:
Problem Definition → Research → Insights → Ideation → Prototype → Testing → Conclusion
What matters most isn’t just that you completed each step. It’s that you can explain why each step led to the next. If you ran user interviews, what did you discover? How did those findings shape your next decision? The connective tissue between steps is where reviewers see how you actually think.
How to Order Your UX Portfolio for Graduate School
Once your case studies are ready, order matters more than most applicants realize. Reviewers often form their impression within the first project — sometimes within the first few pages.
First Project — Your Strongest Work
Lead with the project that best demonstrates research depth, clear process, and a well-resolved outcome. If you’re applying to an Information Science program, a data-informed research project works well here. For MDes programs, something that shows systems thinking tends to land stronger.
Second Project — A Different Skill Set
Don’t follow your first project with something too similar. Use this slot to show range — a collaborative project, a research-heavy study, or something that used a different methodology or tool set. Reviewers want to see that you can work across different contexts.
Third Project — Something Personal
This is where your individual perspective comes through. A project rooted in a social issue you care about, a specific user group you’ve worked with, or a problem you experienced firsthand tends to be the most memorable. Personal investment shows in the work.
Supporting Projects — Optional
Short, lightly documented projects or coursework can be included, but only if they hold up next to your main case studies. If they feel significantly weaker, leave them out.
How Many Projects Do You Need in a UX Portfolio for Graduate School?
More isn’t better. Three to five case studies is the standard for a UX portfolio graduate school applications require. Your main projects — two or three of them — should cover the full process from research to final outcome, with enough depth to fill roughly ten to fifteen pages each.
One or two supporting projects can round things out, showing additional range without overwhelming the reviewer. A weak project included just to add volume will drag down the overall impression of your portfolio. When in doubt, cut it.
Finding Your First UX Project Topic
If you’re building your UX portfolio for graduate school from scratch, you don’t need to create a complex app or run a large-scale research study. Reviewers aren’t looking for scope — they’re looking for the quality of your thinking.
The easiest place to start is a problem you’ve personally experienced. Here are a few examples of how small frustrations can become solid UX projects:
“The library seat reservation system is confusing” → University library app UX redesign
“I always get lost during subway transfers” → Transit wayfinding system redesign
“The café kiosk menu is overwhelming” → Kiosk UX improvement study
“My international friend couldn’t figure out how to book a clinic appointment” → Healthcare accessibility for non-native speakers
Projects that start from real frustration tend to produce deeper research and richer stories — and they’re much easier to talk about in interviews.
Match Your UX Portfolio to the Graduate School Program
Not all UX and HCI programs look for the same things, and a UX portfolio graduate school reviewers at one program respond to may not land the same way at another.
CMU’s MHCI leans toward research rigor and data. UW’s HCDE focuses on human-centered design and social context. Parsons values creative systems thinking. Look at faculty research and program curriculum before finalizing your project topics — alignment with a program’s focus makes a real difference.
UX graduate programs also attract applicants from very different backgrounds — information science, communications, psychology, design, fine arts, and beyond. That range of experience is genuinely valued. What matters is translating your background into UX language within your portfolio. If you have experience with spatial design, connect it to user flow and navigation logic. If your background is in communication, lean into your strengths in user interviews and storytelling.
Mistakes That Hurt Strong UX Portfolios for Graduate School
These are the patterns reviewers flag most often when evaluating a UX portfolio graduate school applicants submit:
Showing only the outcome: Screens and wireframes without process context tell reviewers nothing about how you think. The process is the point.
Superficial research: Listing “conducted user interviews” without showing what you learned from them is a missed opportunity. Research only counts if it visibly shaped your decisions.
Imbalanced text and visuals: Too much text becomes exhausting. Too little leaves the work without context. UX portfolios need both working together.
No distinct point of view: Following a textbook UX process without showing your own perspective makes a portfolio easy to forget. Why did you choose this problem? What did you see that someone else might have missed?
Where to Start Building Your UX Portfolio for Graduate School Right Now
If you’re just beginning to build your UX portfolio for graduate school, start by going back through the projects you’ve already done. Design work, coursework, personal projects — any of it is fair game. Find the one where you can most clearly explain why you made it and what you were trying to solve, then restructure it as a UX case study.
That process of reframing is already UX thinking in action. And that’s exactly what graduate programs want to see. Your UX portfolio graduate school reviewers evaluate doesn’t need to be perfect. It needs to show how you think. That’s what gets you in.
Frequently Asked Questions About UX Portfolio for Graduate School
How many projects should a UX portfolio for graduate school have?
Three to five case studies is the standard. Two to three main projects should show the full process in depth. One or two supporting projects can show additional range. More than five projects rarely improves an application — quality and depth matter far more than volume.
What do HCI and UX graduate programs look for in a portfolio?
Reviewers primarily look for evidence of clear thinking — how you define problems, how you move through uncertainty, and how research shapes your decisions. Polished final screens matter less than the process behind them. Programs want to see that you can think like a designer and researcher, not just produce attractive outputs.
Can I include personal or academic projects in my UX portfolio for graduate school?
Yes. Personal projects, coursework, and independent studies are all valid. What matters is that the project has a clear problem, a documented process, and a meaningful outcome. Projects rooted in real frustration or personal experience often produce the most compelling case studies.
Does my UX portfolio need to match the specific program I’m applying to?
Not entirely, but alignment helps significantly. Researching each program’s faculty, curriculum, and values before finalizing your project selection can make your portfolio feel purpose-built rather than generic. A data-focused project lands better at CMU; a socially grounded project tends to resonate more at UW HCDE.
What’s the biggest mistake applicants make with their UX portfolio for graduate school?
The most common mistake is showing only the final outcome without explaining the process. Reviewers want to understand how you think, not just what you made. A portfolio that shows research, iteration, and decision-making — even imperfect decision-making — is far more compelling than one that presents only polished final screens.
Further Reading
If you’re still deciding which UX or HCI program to apply to, this comparison of CMU MHCI vs UW HCDE vs Parsons MDes breaks down the key differences between three of the strongest programs. For a broader overview of options, this guide to the best UX and HCI graduate programs in the US covers the full landscape.