- Organization of the content
- Visual presentation of the content
- Textual presentation of the content
There are also three qualities or features that each one of these should present
Some feedback I received from my original portfolio was that the process I outlined was super detailed. Yet, at the same time, some recruiters, hiring managers, and UX practitioners who interviewed me appreciated the brief but clear outline I provided. This clash is something we all face in building our portfolio. I decided to stick with the brief approach in order to focus recruiters’ attention on my critical thinking and writing skills since I am looking for UX research and UX design jobs rather than positions more focused on visual design or development. This rationale and outline was inspired by a great article in Smashing Magazine
An interesting insight from one conversation during an interview, as well as several conversations during my internship, was that recruiters wished portfolios could be designed in multiple ways for multiple audiences. While at first this idea of a “context-aware” portfolio may seem difficult to actually build, I thought of an appropriate solution. At its core, this trade-off is an issue anyone in UX faces:
- trying to summarize months or years of work into an outline with tangible and actionable items
- trying to detail the journey and the process of solving a design problem without being overly detailed
Based off of these conversations, I rethought the next iteration of http://www.davidhmunoz.com. Rather than try and solve both problems with a single interface and outline, I decided to have two separate views for eacah project:
- a slightly shorter version of my original “research outline”. I named this view the “Executive Summary”
- a detailed chronological description of the work involved in the project, appropriately titled “Design Process”
The “Executive Summary” focused on brief and concise text with links to relevant materials such as reports, posters, or other deliverables.
The “Design Process” focuses on a linear description of the work involved in a project. However, it starts off with a brief overview to frame the question, stages of the project, and any key deliverables or results (e.g., submitted to a conference). I use writing to explain design decisions and also include pictures of design artifacts where appropriate.
It is extremely difficult to be clear and concise while also providing appropriate amounts of context in a portfolio. This iteration of my website hopes to address both by acknowledging the difficulty through the creation of two separate views for each project. We’ll see what recruiters and UX professionals think!