Refuse to Create a UX Portfolio
Timothy Jaeger

I agree with the suggested portfolio content. But I feel this article is a little contradictory. Maybe it was supposed to be? The title advises not to create a UX portfolio, but then provides suggestions on what to include.

I work in a geographic market where there aren’t a ton of UX people or companies that are hiring UX Designers. On more than one occasion I have been asked to interview someone that does not have a UX background. Their education and possibly work experience has been centered around visual design, or even marketing.

Having a UX portfolio clarifies what their focus is. I work as a consultant. On the flip side, a UX portfolio helps to help the client understand what UX design is, since some organizations are still unclear of the activities a UX designer would perform. I would argue that it’s not dumbing down the profession, but enlightening organizations and newbies on what UX is about. I do agree that simply presenting wireframes or other artifacts out there, without any context, is potentially more confusing. I would argue though, that UX is collaborative. I can’t think of a time that I delivered wireframes or other materials for a project without having a discussion with stakeholders, developers, etc, where I explained the work. I agree with providing insight into the problem and other information.

I’m not clear one why a portfolio cannot contain the business case information and samples of the design from sketch to visual design. For a UX Designer, it would seem that including all of the content you suggest, plus design work (including but not limited to wireframes) would give the full picture to a potential client or employer.

Like what you read? Give David McCoy a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.