When I started out in user experience in 1989 — the field was called Ďhuman factorsí back then — there was no concept of the ĎUX portfolioí.
Just before I got my first job in the field, I had been working as a researcher in various psychology departments in various universities. My specialism was colour vision, and colour blindness in particular.
The call came when I was working at New York University. On the telephone was British Telecomís head of Human Factors at Martlesham Heath in Ipswich. He had heard about my work in colour vision and needed someone with precisely that skill set on his team. Back then, there was a real concern that the 8% of men who were colour blind would go to pieces when placed in front of a colour-coded network management display, and I would be BTís insurance against a network catastrophe. (A note to people under 30: colour displays were a rarity in those days. We all used steam-powered cathode ray tubes where the only colours were green on black).
It was the first and only time Iíve ever been head hunted.
I relate this story to illustrate that my new employer didn’t ask me to send over my portfolio.
If he had, Iíd probably still be sitting in the dark in a university psychology department somewhere carrying out colour sensitivity threshold measurements.
So where did the concept of the user experience portfolio come from?
Portfolios are common in visual arts, like design and photography. Picasso, Iím fairly sure, had a portfolio. But they are uncommon to the point of being unheard of in scientific fields, like research and technology. Einstein, Iím fairly sure, didnít have a portfolio.
But at some point over the last decade, a clueless recruiter or employer asked a user experience researcher for their portfolio. In a panic, the job candidate pulled something together and now itís just seen as a given that a UX practitioner will have a portfolio that illustrates their work — even if they don’t create visual designs.
So if your work involves voice recordings from field visits, bits of paper prototype and Excel spreadsheets — these days, youíre still expected to create a portfolio.
The problem with UX research portfolios
Most weeks I receive an email from a prospective employee. The email always has their CV as an attachment; sometimes the prospective employee will also attach their portfolio (or provide a link to it).
Itís rare that I see a portfolio that impresses me. If I was the judging type, most of them would, at best, get a ĎCí grade.
Youíre not going to get an interview if thatís the best you can do. Almost always, I see the same set of problems.
Here are four problems I commonly see along with some suggestions on how to fix them.
1 Stop pretending youíre a visual designer
Visual designers are in the business of creating interfaces that look good. Depending on the research (or lack of it) that went into the designs, the interfaces may actually not be that easy to use — but the first impression will have impact. First impressions do matter and thatís probably why so many researchers try to pad their portfolios with examples of user interfaces.
But this is the worst thing you can do.
If youíre a user experience researcher, you don’t design screens. You design experiences.
Instead of creating amateurish mock-ups in PowerPoint or — even worse — presenting someone elseís design as your own, use your portfolio to showcase the research work that underpins the designs youíve been involved with. What were the business objectives? How did you ensure they were met? At what points in the process did you involve users?
Research projects can still be presented visually. Do a quick search for Ďusability testing infographicí and youíll see what I mean. And there are many deliverables in user experience research that are inherently visual: personas, user journey mapping and expert reviews are three that jump immediately to mind.
2 Show the journey, not just the destination
A second common mistake I see in portfolios is that they focus on the deliverables and not the journey.
For example, a research portfolio case study on personas might show the final personas, perfectly formatted, ready for a magazine.
But that’s not the challenge.
The challenge when developing personas is doing the field research and analysing the data. Creating the personas themselves is the icing on the cake. So although it’s less photogenic, you need to explain the research behind the deliverable. (You can still show the deliverable — just make sure to show your working, as my Maths teacher used to say).
Another reason to show the journey is that it keeps you honest. I saw a portfolio once that described how the candidate had designed a successful iPhone app. What he forgot to mention was that he was part of a team of 8, and his main contribution was to run a usability test of a prototype.
Claiming other peopleís work as your own is a surefire way to lose out at interview.
To make sure you show the journey, tell the story of your involvement:
- Explain the business problem you were trying to solve. Just one or two sentences will do. If you struggle with this, try to remember how the project started: how did your internal or external client articulate the problem? In the context of a story, this is the trigger that starts us off.
- Describe your approach. Of the universe of possible research methods, why did you pick that one? Remember that research takes place in a business context and your approach doesn’t need to be some mythical, ideal approach; it needs to be an approach that offers the best value. In a story, this phase is known as the quest.
- Present your results. Be brief, but show enough detail to make it clear that you know what youíre talking about. Describe one of the major problems you encountered with the study and how you solved it. In any good story, the hero always has to overcome difficulties and this is the place to show you are a problem solver.
- Describe the impact of your work. Relate your findings back to the business problem. Did you solve it? If not, what did you learn that you will apply to your next project? This is the resolution to your story where you, and your client, both became a little wiser.
3 Assume you have 1 minute to land your dream job
You spend hours on your portfolio. Sadly, I will spend one minute looking at it. After one minute, Iíll decide to spend another 5 minutes on it — or send a rejection letter. I know, itís brutal.
But itís not dissimilar to the way you behave when you land on a web page. You scan it and then quickly make a decision to invest more time or hit the back button. You can be brutal too.
But this means you must design your portfolio for skim reading. Not only does this mean itís more likely to get looked at, it also demonstrates your skills in user experience: it shows you know how people read. Itís a great example of the medium being the message.
(And if you don’t know how people read, why not usability test your portfolio with friends and family?)
In terms of overall size, I know this may not be a great help, but you’re after the Goldilocks portfolio: not too long, not too short, but just right. One way to achieve this is to ruthlessly cut out duplicate projects. If you’ve done three card sorting studies and two paper prototyping exercises, I know that it’s tempting to include all of them. But don’t. Instead, show just one case study of each type. Aim for 1-2 pages per project and keep it visual.
4 Focus on the details
This one seems obvious — we all know itís rule number one when youíre putting your CV together.
But hold on: there an interesting twist when youíre applying for a job in user experience. Both UX research and UX design are inherently detail-oriented professions.
Of course your spelling and grammar will be ruthlessly examined. But it goes beyond this.
- What font will you use? (Hint: it won’t be Comic Sans).
- What kind of layout grid will you use for your case studies?
- Where is your call to action?
Once again: the medium is the message.
The history of your working life
One final point. Your user experience portfolio also acts as a scrapbook of your working life. When you update it (and you should be updating it every few months), make sure you keep the earlier versions. This is a powerful way of showing you just how far you've travelled.
I asked a few colleagues to comment on this article before I posted it and one reviewer raised this interesting paradox:
How can I compensate for a lack of experience without lying?
(A variation on this question is: how can I show more breadth when my day-to-day job is recruiting users / running card sorts / acting as an assistant to someone more senior?)
I think this paradox has more than one resolution — here's two.
One approach is to set yourself assignments. Let’s say you’ve never run a usability test and this is the glaring hole in your portfolio. In that case, be your ideal client and run a test. Pretend that you’ve been commissioned by the BBC to run a usability test of the iPlayer installation process. How did you plan and execute the test? How did you recruit users? How did you analyse the data?
In many ways, carrying out self-assignments shows more dedication than simply turning up for work to deliver on a real project — and it also shows it’s all your own work, not someone else’s that you’ve hijacked.
If the idea of self-assignments doesn’t motivate you, a second approach is to volunteer. There are no end of charities and non-profits who could boost donations with the kinds of insight you could provide with a usability test.
About the author
Dr. David Travis (@userfocus on Twitter) holds a BSc and a PhD in Psychology and he is a Chartered Psychologist. He has worked in the fields of human factors, usability and user experience since 1989 and has published two books on usability. David helps both large firms and start ups connect with their customers and bring business ideas to market. If you like his articles, you'll love his online user experience training course.
Love it? Hate it? Join the discussioncomments powered by Disqus
Foundation Certificate in UX
Gain hands-on practice in all the key areas of UX while you prepare for the BCS Foundation Certificate in User Experience. More details
Every month, we share an in-depth article on user experience with over 10,000 newsletter readers. Want in? Sign up now and download a free guide to usability test moderation.
User Experience Articles
Our most popular articles
Our most commented articles
Our most recent articles
- Jul 5: The two questions we answer with user research
- Jun 6: What user researchers ought to know about informed consent
- May 2: Measuring Usability With The System Usability Scale (SUS)
- Apr 4: 5 reasons why your first user research activity should be a usability test
- Mar 7: Keeping Yourself out of the Story: Controlling Experimenter Effects
Search for articles by keyword
- 7 articles tagged accessibility
- 4 articles tagged axure
- 5 articles tagged benefits
- 12 articles tagged careers
- 8 articles tagged case study
- 1 article tagged css
- 8 articles tagged discount usability
- 2 articles tagged ecommerce
- 12 articles tagged ethnography
- 14 articles tagged expert review
- 1 article tagged fitts law
- 4 articles tagged focus groups
- 1 article tagged forms
- 6 articles tagged guidelines
- 10 articles tagged heuristic evaluation
- 7 articles tagged ia
- 14 articles tagged iso 9241
- 9 articles tagged iterative design
- 3 articles tagged layout
- 2 articles tagged legal
- 11 articles tagged metrics
- 3 articles tagged mobile
- 7 articles tagged moderating
- 3 articles tagged morae
- 2 articles tagged navigation
- 9 articles tagged personas
- 15 articles tagged prototyping
- 7 articles tagged questionnaires
- 1 article tagged quotations
- 4 articles tagged roi
- 16 articles tagged selling usability
- 12 articles tagged standards
- 41 articles tagged strategy
- 2 articles tagged style guide
- 4 articles tagged survey design
- 5 articles tagged task scenarios
- 2 articles tagged templates
- 21 articles tagged tools
- 52 articles tagged usability testing
- 3 articles tagged user manual