How to Structure a Design Portfolio for a Busy Reviewer

Make the home page an orientation, not a biography

Use a concise description of your role or direction, a working contact path, and a small selection of relevant projects. A short introduction can add context, but the first screen should not require a visitor to read a long personal statement before finding work. Avoid a role label that overstates your experience.

Group projects by the decision a reviewer needs to make

A portfolio for several kinds of work can use clear categories or project labels. Choose groupings that help people find evidence—such as product design, brand systems, or illustration—rather than internal team names that visitors will not recognize. If you are applying for one role, make the most relevant work easy to reach first.

Give each project a useful preview

• Project or product name, with confidentiality respected.
• Your role and team context in a short phrase.
• The problem or deliverable the case study explores.
• A truthful project status, such as shipped, in progress, or self-initiated.

Example: a reviewer looking for product design work

A fictional portfolio could put “Product design” above a case study card titled “Reducing missed steps in appointment requests,” followed by “Interaction design · team project · shipped.” That preview gives a reader a reason to open the case study and sets expectations without claiming a measured result. Replace the example with work and status you can substantiate.

UConn Center for Career Readiness: Portfolio Guide

Keep the navigation and links predictable

Make it clear how to return to the project list, move to another project, or contact you. Use descriptive link text and avoid navigation that depends only on hover. Open the site on a phone and test the actual links; a visual prototype or screen capture cannot confirm that navigation works.

Ask someone to find one thing

Give a reviewer a target, such as “find the project where I worked on a design system.” Observe what they click and what they expect to see. If they cannot find it, ask whether labels, grouping, or project previews caused the problem before rearranging everything.