Loading…
Design work is judged on thinking as much as polish. Your site should show both: the problem, the process, and the outcome.
A design portfolio is closer to a set of short stories than a gallery. Whether it's graphic, product, UX, or industrial design, the people reviewing it want to know what the brief was, what you tried, why you chose what you chose, and how it turned out. A final render alone doesn't answer those questions.
That makes structure the hardest part. We help you pick the few projects that best show your range, and shape each one into a clear case study from your own notes.
Brief, research, iterations, and final outcome, in the same order for every project.
Sketches, wireframes, prototypes, testing notes, and model photos that show how you got there.
Logos in use, type and color specifications, and applications across formats.
Embedded prototypes or short screen recordings for apps and websites.
Photographs, technical drawings, and material studies for product and industrial design.
For team projects, a clear note on exactly what you did.

A template decides the layout before it has seen your work. We design the other way round.
Always follow each program's own submission requirements first. Your website complements them.
Fewer than most people think. A handful of well-told projects usually reads better than a dozen thin ones. Check each program's requirements first, then we'll help you choose.
Only with permission. Options include anonymizing the client, showing the process without final assets, or putting the project behind a password.
It needs to look considered. A loud site can distract from your work; a quiet, precise one shows judgment.