OK, UX designers. Let's talk about your portfolio.
I've been reviewing these lately (mostly for clients who ask us to help build their team, but occasionally for designers who ask nicely).
There are important things that many designers miss, especially early career folks.
#1 No sense of timeline.
When did each project happen and how long did each one take?
Hiring managers need to know when in your career each project takes place. Was it your first project out of school? Is it your most recent work? They shouldn't be left to wonder.
Also, inside each case study, what order did each step happen in? Was it strictly linear, or did you iterate (research, prototype, test, learn some stuff, researched some more, prototyped again, tested again, learned more…)?
Why not use some sort of calendar to help?
How long was each step? When you say you did user research, was that in an afternoon? Or was it throughout the project? How long did you spend talking or observing participants? How did the research change each time you talked to users?
In many case studies, the designers describe important steps with 1 or 2 sentences. That makes it seem like there was virtually no effort put in. There's no indication of the amount of effort.
(The answer isn't longer descriptions. There are other ways to indicate effort.)
Hiring teams want to know if you treat stages like a checklist item, to get through them as quickly as possible, or if you take them seriously and in-depth.
Putting some sense of effort into each case study would give an interviewer an opening to ask more about your efforts.
#2 No sense of your contribution to collaborative efforts.
Design is a team sport. Were you part of a team? If so, what role did you play? Did that role change during the project?
Who else was on the project? We don't need names, but roles and quantity would help.
Which pieces were you solely responsible for? Which did you work in pairs or small groups? What was it like to work in those for you?
Who did you need approval from? How did you present your work for approval?
Did you work with devs? PMs? Other non-designers?
Hiring managers are looking for how well you work in a team environment. They want to know how well you'll work on their team.
Are you a solo gunslinger that repels any notion of collaboration? Or do you thrive in a collaborative environment, helping support the team effort?
#3 No sense of your leadership skills.
If you played any sort of leadership role in any project, what was that role? How did it come about? How did you do?
Who did you lead? How did you support them? How did they thrive under your leadership?
What made that leadership challenging? How did you overcome those challenges?
Designers often find themselves in a leadership position, even if it's only for a meeting where they are leading a workshop to make a decision or review research data. Describe times you led your team.
Hiring managers need to know what kind of leadership skills you have. Without knowing this, they won't know how quickly you'll grow into a more senior role on their team.
They want to know if they can send you off with a client, or if you'll always need someone senior with you.
#4 No sense of challenges or learning.
In many portfolios, every case study is presented as if it didn't have any hitch or speed bumps.
Every project went perfectly.
There were no problems to overcome and no challenges to learn from.
We all know that never happens.
Yet, I rarely see any case study even hint at what the candidate learned from all that hard work. It seems they didn't learn a thing.
How has your previous work informed how you would tackle this project?
How did this project inform your future work?
What was challenging about the work? What process did you use to learn what you needed to overcome that challenge? What resources did you turn to? Where did you make wrong turns?
The best, most interesting stories are not ones where the protagonist sets out on an adventure where everything happens perfectly. That's boring.
The most interesting stories are those where the protagonist runs into a serious, unassailable challenge.
How did you finally assail your unassailable challenge?
Hiring managers want to see how truly resourceful you've been. They want to see that you didn't give up when you ran into something tricky.
They know your case study will have a happy ending. They want to see the journey.
That's the 4 big missing pieces I would like to see in every portfolio I review. I know other hiring managers would desperately like to see them too.
When crafting a portfolio, the hiring team members are your primary users. Are you thinking about what your users need from you?
Oh, a bonus item:
Don't password protect your entire portfolio. If you must, you can put individual cases (or assets) behind password walls. Just not the entire thing.
But ask yourself first, what can I show that nobody else has claim over? What can I say I've done?
You can alway talk about *something* from every project. You can say you worked there. You can describe the nature of the work, even if you must leave out certain specifics. You can describe your process and, in general, what the outcomes were.
In our field, every hiring manager runs into people under NDA and other protections. Smart ones don't actually care about the things you can't talk about.
They have one question you need to answer: Are you capable of doing the work for the hiring org? Answer that question.
When you do have to put something behind a password, don't assume everyone who gets your portfolio link will also get your password. Give them a way to request it from you.
OK. Let's summarize.
#1 What was your project timeline?
#2 What was your contribution to collaborative efforts?
#3 What leadership skills have you employed?
#4 What has challenged you and what have you learned from those challenges?
That's what I want to see in your portfolio.
Thank you to the many UX designers whose portfolios I’ve had a chance to review.
I’ve seen a ton of great work. I think y’all have real talent.
I won’t mention names, because it’s not my place to do so. Just know you’ve done well.
A lot of my work is talking to UX folks about their next job.
Many struggle with "deciding what I want from my next employer."
I've come up with a way to get them past this and to start thinking about where to look first for opportunities.
1/
Thinking about their next job inevitably leads many folks down the path of "what would I like in a place to work."
This gets into lots of touchy-feely attributes about the work environment, but what's almost always missing is what they'll actually do when they get there.
2/
Don't get me wrong: there's a lot to be said about working in a high-quality work environment.
However, that environment isn't going to hire someone out of charity.
The org is hiring someone to get a job done.
That's where the job hunt needs to start. What will you do?
3/
I see the same mistake repeated across many of the UX job ads I review.
The job ad describes the JOB, yet highly-qualified candidates want to learn about the WORK.
These are very different things.
1/
What we hear from candidates:
Tell me what I'll be working on.
Tell me how my work will have an important impact on people.
Tell me what makes the work challenging, especially for someone at my experience level.
Tell me what makes this work unique.
This is the WORK.
2/
UX job ads rarely talk about those things. Or maybe they give 1-2 sentences about it.
Here's one example I just found. They give 1 sentence to what the company does. The rest of the paragraph could be describing any company on the planet.
I spend most of my time these days helping extremely frustrated UX leaders try desperately to push past the “research=validation” boundary with their leadership.
It’s really a dangerous mindset to let grow.
There are better ways to position research. We’re much smarter now.
When every respondent brings their own meaning and context to a question, you can’t aggregate the answers. You’re aggregating apples, oranges, watermelons, and bees. What’s the average of all that mean?
Satisfaction measures are literally garbage measures.