I recently commented on an IxDA group post on LinkedIn and got a very positive response, so I figured I’d re-post my thoughts here for those who may not be members of that group (or site).
I’m a usability experience professional who is a generalist (i.e. I do a little bit of everything from user research to interaction design to information architecture to usability testing). And I’ve been thinking about portfolio design for awhile now. To me there are four aspects to having a portfolio: 1) content 2) presentation 3) delivery 4) maintenance.
1. Content
I often see job descriptions go by, and people say “must have strong portfolio” and the like. I’ve taken poor portfolios to job interviews (in a scramble) and gotten the job, and taken what I thought was a great portfolio only to be turned away. Different people want to see different things, so obviously knowing your audience and being able to show them what they want is key. One of the ways I figured out what to include in mine is by talking with hiring managers (often friends) to see what they look for, and by looking through interesting job descriptions as they come by for any meaningful nugget about what kind of content the recruiter or hiring manager is interested in. (I save these in a Google doc to refer to later, as a sanity check.)
2. Presentation
Presentation is another aspect. For my portfolio (because of the audience consideration), I’m working toward modularity. So if someone says “I want to see how you arrived at the final design from the first back-of-the-napkin concept,” I can show them the section that addresses that. If they say, “I want to see how you came up with the information architecture for this,” or, “I want to see an example of a top notch design specification,” I can pull out an example of a project that focused on these. I find that writing up a page or two (max!) that describes the project’s goals, what you did, and the impact you had can be useful — who remembers after years have gone by!? Best to do it right after the project so you can keep track of those useful details and refer back to them when you’ve forgotten.
3. Delivery
Delivery is something I personally struggle with. I’ve collected links over the years for people’s online portfolios, but I never feel comfortable doing mine in this way. (I’ve worked primarily on internal sites / tools or software that is sold to the public, not web sites I can point to easily.) I worry about confidentiality and so I have historically always brought a hard copy portfolio to interviews. Has it cost me some opportunities by not being able to have people browse my portfolio online ahead of time? Probably. But I’d rather have that than get sued by a former employer for publishing something I shouldn’t have. And, to me, any employer I’d want to work for would understand and respect that.
4. Maintenance
Then, how do you keep the portfolio fresh and up to date? If it’s hard copy, it gets large quick. When / what do you purge? My thought is, when I have examples of things that were mentioned in that Google doc, and a good variety of work from all different prior jobs (not just my current one), then I need to look at the quality of the sample, and see if it’s something I can improve on. If I’m missing some aspect, maybe my next project will help me fill in the gap, or I can do something on the side to cover it.
Anyway, those are just my thoughts. My goal for the year is to finish up a draft of a new portfolio at least. I keep slogging through stuff, but other things always get in the way — especially when there’s no (known) urgency for me to be job hunting!