What makes a good UX researcher portfolio? Part 3: Presentation (Project Page)

I’ve finished updating my own portfolio with a few projects I completed over Fall of 2013. I’ve also redone a lot of the project posts for previous work.
To recap my original post on designing a portfolio, there are three essential components:
  1. Organization of the content
  2. Visual presentation of the content
  3. Textual presentation of the content

There are also three qualities or features that each one of these should present

  1. Clarity
  2. Conciseness
  3. Context

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!

Advertisements
Standard

What makes a good UX researcher portfolio? Part 2: Presentation (Home Page)

In my first post about building a portfolio, I focused on the actual creation of a website for displaying your work. Having just finished redoing my own portfolio, I thought it would be appropriate to talk about some of the design choices I made.
To recap my last post, there are three essential components to creating portfolio content:
  1. Organization of the content
  2. Visual presentation of the content
  3. Textual presentation of the content

There are three qualities or features that each one of these should present

  1. Clarity
  2. Conciseness
  3. Context

As an example, I decided to change my home page from a “featured work” slider to the “about me” page for several reason. From my interviews for internships, I found that recruiters and designers do not benefit from sliders. Static sliders require extra clicking effort (why not just display all of the images next to each other?), and dynamic sliders are tricky because different people read at different speeds. It’s hard to time just how long a slide should be shown before advancing.

The main reason why I used the dynamic slider was to showcase my work. I also liked that it was something I had not usually come across in viewing other students’ portfolios. Most of these other portfolios looked similar, especially the landing page: a grid of small boxes with somewhat visually appealing images but no context of what the project is. I’ve already discussed why this design fails for a landing page.

In reflecting upon why a recruiter visits a portfolio in the first place, I realized that they are looking to hire the right talent. Part of that talent evaluation involves reviewing projects, but in the end, they want to learn more about the applicant and his or her design process. Changing the landing page to the “About Me” made my portfolio instantly more personable while highlighting my strengths as a researcher and my passions in and out of work.

Additionally, while I like my name, it is the Spanish equivalent of “John Smith”. There’s a David Muñoz doctor, musician, actor, DJ, teacher, soccer player, you name it. Davidmunoz.com currently costs over $500 to name based on demand. Given these constraints, I need to make sure off the bat that a recruiter knows he/she is at the right page. I added my picture (same one as LinkedIn for consistency) and have my logo on every page as well.

Standard

What makes a good UX researcher portfolio? Part 1: Overview

Before focusing on any one part of building a portfolio, I want to outline the general components needed to make one. These observations were made from viewing both undergraduate and undergraduate portfolios at various colleges, as well as from reading various articles about the expectations hiring managers have for UX researchers and designers.

Building a portfolio is very tough to do. Designing a portfolio website is much easier, yet so many UX researchers and designers fail to spend enough time on this task. I will focus on discussing how to design a portfolio in future posts and will only provide a brief mention of actually building it in this post.

By “building”, I am referring to two components:

  1. Generation of content that can be used in the portfolio
  2. Creation of a medium for the portfolio (in this case, a website)

Generating content through independent or group collaborations is extremely difficult and time consuming. Projects can take a few days (like a hack-a-thon) but will usually take a few weeks, months, or even years.

The good news is that designing a good portfolio to showcase your work will not take this amount of time.

The bad news is that designing a good portfolio requires constant updates of the content. Many great designers simply stop updating their portfolios after finishing their undergraduate or graduate degrees, cheating themselves out of showcasing their work and design process to the public even though this work will often reach more users than a school project will.

Creating the medium for the content is much easier now than in past years. Companies like WordPress, Cargo, Behance, and Dribbble, just to name a few, let designers and researchers host websites for free or for reasonable prices. Knowledge of HTML, CSS, and JavaScript are still great to have but are not necessary for creating a portfolio.

The good news here, of course, is the time saved. UX professionals who intend to focus on building websites may be more inclined to build their own portfolio from scratch to show off their abilities. While I am improving these web development skills, my strength is as a UX researcher and designer, not as a developer. For now, I am thankful that WordPress has allowed me to build a portfolio with my limited knowledge of this field.

The bad news is that too many researchers and designers over-rely on templates that may not be the most effective for conveying information. Templates also may overly constrain a site. Usually templates can be changed as needed (as I did on my own website), but it is tempting to just leave a template as-is rather than diving into code to figure out how to make the slight adjustments that would make a page more ideal in terms of its organization, visual appearance, or textual presentation.

By “designing”, I am referring to three overlapping components:

  1. Organization of the content
  2. Visual presentation of the content
  3. Textual presentation of the content

As I mentioned above, too many portfolios are lazily designed. The image and the textual content is there, but there is little thought put into the actual experience that recruiters and others with hiring power will experience when navigating your portfolio. If you can’t present your projects in a compelling way, recruiters will not browse your site.

For example, as fellow Duke alumni Alex Cornell recently pointed out in his satirical portrayal of common portfolio flaws, some portfolios are overly vague in the way in which they present their work. Certainly, this is an issue since recruiters will not waste their time trying to figure out what your project involved, no matter how great it was, if you can’t clearly articulate your thoughts on the project.

While his list is not meant to be exhaustive, there is one issue I have with his suggestion for improving a portfolio:

This is how you make the worst portfolio ever. Do not do this. If this looks like your website, change your website. It’s very easy to fix: stop stating the obvious and show off your work instead.

Yes, he is right in the sense that you must present your work clearly and concisely, both in terms of the images you choose to display and the text you write. There is definitely a large set of portfolios out there that cannot articulate what exactly the work was about. However, the last sentence in the quote above shows what I have found is wrong with most portfolios and what may arguably be more likely to make a portfolio unimpressive.

From browsing portfolios and reading HR and critiques from senior UX researchers and designers, the most common issues with portfolios seem to be:

  1. Clarity
  2. Conciseness
  3. Context

The first two issues are the ones Cornell criticizes in his post and are certainly things that must be addressed in designing a portfolio. Yet I believe the third point, context, is what is most often neglected in portfolios. Given that recruiters are browsing various portfolios, “describing” a project by displaying a single photo of the final product and a brief description of what the final product does will not accurately portray to the recruiter what you did, much less why the product matters or why you chose to make the product (“for a class project” should not be the answer to either one of these)

Writing a project description in a paragraph and then showing a really cool demo video or a beautiful screenshot of your app is great since you are demonstrating that you can create a quality product. Yet you are still neglecting vital details about why you did the project, how you did it, and who you did it with, just to name a few of the details you’ve overlooked!

Let me pick just one of these pieces of essential information that is often neglected. In such a multidisciplinary and collaborative field, proper credit must be given since you are rarely working on something on your own. If you are, that’s great! Make sure you point that out. Yet since many young UX researchers and designers have limited (if any) work experience, most of their portfolio will be school projects that involved multiple team members.

Don’t try and take all the credit for the project since this will almost never be the case, be it in school projects or in industry. You’re selling your teammates short by claiming their skill set and selling yourself short by failing to emphasize your own skill set and how it helped determine the success of the project.

Standard