This past weekend I had the chance to attend the IDSA (Industrial Design Society of America) Western district conference. I’ve been to several IDSA events in the past, but skipped last years. It was good to get back and hang out with the Industrial Design “tribe”. (The idea of tribes were one of the themes of this years event) I met a lot of nice people, learned a lot of new things, and had the opportunity to participate in a collaborative “design swarm”.
On the flip side, as a UX designer, I was one of a minority. It’s not a huge difference – much of the methodology of the two disciplines is the same, and many Industrial Designers are taking work in UX as of late. Still, I felt like a bit of a representative of the UX side of things, and people were asking me questions.
Two of the most common questions I heard were: “How do I get a job in UX?” and “What goes in a UX portfolio?” These are both particularly salient areas of thought since UX as a field is still relatively new. Trying to come up with answers on the spot got my mind working, and I put together a short list of things that I think should go into a UX portfolio. I think these things are really representative of the work that happens in industry (at least as far as I’ve seen) and also the stuff that really provides value – whether that’s to clients, or development teams or project managers.
Situational Awareness / Presentation skills
This is not as much a portfolio piece as it is a factor in how the portfolio is presented. And this is a tough one to demonstrate. There are two main factors here:
- UX folks should be dealing with people who use, or will use whatever it is that’s being designed. We could pawn that off onto a researcher, but throwing this kind of stuff over the wall is a waste of opportunity. That said, a designer has to be sensitive to those being interviewed/observed and understand their needs; even if it’s just in the context of the interview.
- You have to present your work to someone at the end of the project. If you’re just presenting it to your design director, maybe it doesn’t matter as much how you approach the presentation, but there is real value in being able to talk to a dev team, a PM or even the C suite. You have to know what drives them, and address it as you talk about your work.
I’ve seen a lot of really nice student projects with absolutely no basis in research. (or reality) Make sure you’re showing that you can do the science to prove to your audience that you made the right design decisions.
Sometimes just having research isn’t enough. It has to be structured. What was your plan going into the research? Did you have key questions that you asked all respondents? How did you choose them? What did the results statistically tell you?
Insights are kind of easy. Most designers have these throughout. But as in the above, can you tie the insights to real data and real users?
Industrial design has really provided us a lot of structure in terms of documentation. Any ID process book is a good starting point. It’s important to talk about all of the design activities you did, but maybe more importantly, you should tell why you did them.
Wireframes / Prototyping
This is a gimmie. Everyone should know how to do basic wireframes. But go further – make sure they’re annotated and explain the functionality and the reasons that design decisions were made.
It’s the next step after wireframes. Know how to specify visual style in a “pixel perfect” way, and be able to show and explain design patterns.
As we move further into a “big data” world, it’s important to be able to use visuals to help users make sense of statistical data. It’s one thing to come up with a flashy, novel idea, but another to make something that is easy for a user to get use out of.
Strategy is emerging as an important part of the UX package as more businesses are using UX to drive sales. The idea is to understand the business goals, design for them, and explain why your design helps the company achieve them. You could say that this is designing with an eye to the business, but it should be more holistic – How does this impact the dev team? How can the marketing team make use of your work?
There are surely many other things I could put in here, but these are the things that guide my work. I think it’s easy to get wrapped up in flashy presentation, which is great in it’s own right, but the real value is giving your clients a good return on their investment, and I think the above list does that.