UX case study and portfolio terms, from your first case to a signed offer. Portfolio and resume reviews are the most booked mentor topic on ADPList (30% of tagged US sessions), so these are the words worth getting right.
A UX portfolio is a curated collection of case studies that shows how you solve problems: the context, your process, the decisions you made and what changed. Hiring managers read it for thinking, while the screens support the story.
Example. A strong junior portfolio holds two or three deep case studies, each opening with one line about the result, rather than ten galleries of screens.
Also called: design portfolio, product designer portfolio, ux designer portfolio
A UX case study is the story of one project told as a chain of decisions: problem, constraints, research, options, the choice you made, and the result. It proves how you think, which screens alone cannot.
Example. "Clinic staff missed shift changes; we tested three notification patterns with eight nurses and shipped the one that cut missed handovers in the pilot ward."
Also called: ux case study, design case study, portfolio case study
Case study structure, in its most common form: summary with the result, context and your role, problem statement, constraints, research and insights, options and decisions, final design, impact, and what you learned. The result sits at the top, so a fast reader still sees it.
Example. A recruiter who reads for thirty seconds gets the one-line summary; a hiring manager who reads every word sees the full chain from problem to result.
Also called: portfolio case study structure, ux case study template
A problem statement describes, in one or two sentences, who has the problem, what the problem is and why it matters, without naming a solution. It keeps the team, and the case study reader, focused on the right thing.
Example. "New freelancers can't tell whether a client has paid, so they chase payments by email and lose about an hour a week."
Also called: design problem statement, how might we
Constraints are the limits a design has to work within: time, budget, technology, legal rules, brand and existing users. Showing them in a case study explains your decisions and signals senior judgment.
Example. "The payment provider allowed only one redirect, so the confirmation had to happen inside their page."
Also called: design constraints, constraints and trade-offs
The impact section is the part of a case study that proves the design worked. Metrics are best; without them, observed behaviour in tests, a decision that changed, adoption by the team, quotes from users or stakeholders, and a before and after all count as evidence.
Example. "In testing, five of six people completed the task that two of six completed before, and the PM adopted the pattern for three other screens."
Also called: impact in a ux case study, show design impact
A before and after places the old and new design side by side, with the reason for each change written next to it. It is one of the clearest forms of impact evidence when numbers are missing.
Example. Two checkout screens side by side, with three labelled changes: price moved up, one field removed, button text clarified.
Also called: before after redesign
A case study under NDA (non-disclosure agreement) describes the problem in general terms, blurs or redraws the screens and keeps the reasoning and evidence. When in doubt, ask your former manager which details you can share.
Example. "A B2B scheduling tool for clinics" replaces the client's name, and redrawn wireframes replace the real screens.
Also called: nda portfolio, how to write a case study under nda
A portfolio review is feedback on your portfolio from a mentor, peer, recruiter or hiring manager. A good review tells you what reads as your level, what is missing and what to fix first.
Example. A mentor says: "Your process is clear, but I can't find the result. Move the outcome to the first line of each case."
Also called: portfolio feedback, portfolio critique
Personal branding for designers is how you are known professionally: your focus, your point of view and the work people associate with you, across your portfolio, LinkedIn and community. A clear brand makes the right opportunities find you.
Example. A designer who writes monthly about accessible forms becomes the person recruiters contact for accessibility roles.
Also called: designer personal brand, personal brand for designers
Job matching is lining up a role with what you can actually show: your level, your real strengths and the kind of team you want. Matching well beats applying everywhere, because it puts your best evidence in front of the right reader.
Example. A mid-level designer strong in research and lighter on visual work targets product roles on research-led teams instead of brand studios.
Also called: job matching for designers, find the right design job
A recruiter screen is the first short call in a hiring process, checking your experience, motivation, salary expectations and availability. It decides whether you move on to the design interviews.
Example. In 20 minutes the recruiter asks why this company, what kind of products you have designed and your expected range.
Also called: phone screen, recruiter call
A portfolio presentation is an interview round where you walk a panel through one or two case studies, usually in 30 to 45 minutes, and answer questions about your decisions. Panels look for clear reasoning, trade-offs and your personal contribution.
Example. A candidate presents one case in ten slides: problem, three options, the chosen one with its trade-off, and the result.
Also called: portfolio walkthrough, presenting a case study in an interview
A design challenge is an interview task where you solve a design problem, either live on a whiteboard or as a take-home assignment. Interviewers watch how you clarify the problem, make assumptions explicit and reach a decision, more than the final screens.
Example. Asked to "design a parking app", a candidate spends the first ten minutes asking who parks, where and what goes wrong today.
Also called: take-home design challenge, whiteboard challenge, design exercise
A job offer states the role, level, salary, bonus, equity, benefits and start date. Before accepting, check the level and scope match what was discussed, and negotiate the parts that matter to you.
Example. An offer says "Product Designer II"; the candidate asks how that maps to the company's career ladder before signing.
Also called: design job offer, offer letter
A UX portfolio should include two or three deep case studies, each with the result at the top, your role, the problem, constraints, decisions and evidence of impact, plus a short intro about you. See UX portfolio.
Hiring managers look for how you think in a UX portfolio: a clear problem, the options you weighed, why you chose one, and what changed after. Screens support that story. See case study.
The best structure for a UX case study: one-line result, context and role, problem statement, constraints, research, options and decisions, final design, impact, and what you learned. See case study structure.
To show impact in a UX case study without metrics, use observed behaviour from a test, a decision that changed, adoption by your team, quotes from users or stakeholders, or a before and after. See impact section.
To turn a project into a case study, write the problem in one sentence, list the constraints, pick the three decisions that mattered most, and back each with evidence. Screenshots taken during the project make this much easier. See problem statement.
Every term on this page connects to a part of DesignPath where you can practise it.
See portfolio case studies