“How do I get started creating my UX design portfolio?”
Great question. Here’s how I’ve learned to answer it.
First, a portfolio is a container for stories that answer the hiring manager's primary question: "Do you have what I need for my open designer position?"
Great question. Here’s how I’ve learned to answer it.
First, a portfolio is a container for stories that answer the hiring manager's primary question: "Do you have what I need for my open designer position?"
Thinking of the portfolio as a container of stories means we have to start with the stories themselves. (What good is a nicely designed gift box if we haven't thought about the gift inside?)
What story would tell a hiring manager what you could do for them?
• Does it tell them how you solve hard challenges?
• Does it tell them how you learn new things & apply what you've learned?
Can the hiring manager, after hearing the story, see you in their open position?
• Does it tell them how you solve hard challenges?
• Does it tell them how you learn new things & apply what you've learned?
Can the hiring manager, after hearing the story, see you in their open position?
Crafting stories is the hardest part of creating the portfolio. That's where I think the designers should spend the most time.
Practice telling the stories to others.
See what resonates.
Understand what the key points and messages are.
Practice telling the stories to others.
See what resonates.
Understand what the key points and messages are.
Once you have a story you think does a good job talking about what you'll do for your next manager, what supporting materials help you tell that story?
Do screenshots help tell how you solved hard challenges?
Do artifacts or diagrams communicate what you've learned?
Do screenshots help tell how you solved hard challenges?
Do artifacts or diagrams communicate what you've learned?
Next up: How do you tell the story without being physically present?
Because you now know what the essential elements of the story are, it should be easier to craft a case study that tells the story without you being there.
Usability test that case study. Is it working?
Because you now know what the essential elements of the story are, it should be easier to craft a case study that tells the story without you being there.
Usability test that case study. Is it working?
Once you have a story (or two or three), now you're in a position to think about the portfolio itself.
What's the best way to collect up those stories and display them, such that a hiring manager can home in on the one or two that best helps the learn what you're capable of?
What's the best way to collect up those stories and display them, such that a hiring manager can home in on the one or two that best helps the learn what you're capable of?
The only place I know of talking about this radical approach to thinking about a portfolio is @ifenn's upcoming book. It's story first, instead of container first.
The designer thinks about communicating their story as a design problem. They approach it with design tools.
The designer thinks about communicating their story as a design problem. They approach it with design tools.
