The Global VC

How to Interview a Designer

500 Global Team

500 Global Team

PUBLISHED

2010.11.25

SHARE

FacebookTwitterLinkedinMail

TAGS

Written by Jason Putorti, a 500 Startups SuperMentor, Venture Advisor and Founder of Votizen. The post below is cross-posted from his blog.

These are the tenets I give people when they ask me how to evaluate a user experience designer for their startup. It’s not perfect, it’s not a guarantee, but this is my approach:

  1. Visual portfolio. Gut check ‘yes’ or ‘no’. Either you like it or you don’t. If you’re not sure what good is, my first filters are information priority (are the first through fifth most important things on the page obvious from the visual weight), information organization (are related ideas near each other), intuitiveness (what you’re supposed to do next), and clarity of copy.
  2. Process. “This portfolio looks great, how did you get there? What problem were you given? How did you approach solving it? How did you iterate from idea to final product? How many concepts did you try? How did you decide which one to go with? Who was this designed for?” And so forth. The key here is to derive a rational, thoughtful design process that balances business needs with user needs— and empathy with those users. This separates designers from artists making pretty pictures.
  3. Intellectual curiosity. Nobody knows everything about design, or anything else. “What do you read? Who/what inspires your thinking around user experience? What’s an example of a good user experience and why? How will you improve over the next year?” Granted you need to know some things up front, such as the definitions of user experience, design thinking, and perhaps something about various design philosophies like user-centered, activity-centered, etc. Wikipedia is your friend.
  4. Trial and error. Give him or her a UI component to redesign, or present a problem you’ve been facing and ask for some ideas on how to solve it. I feel a discrete UI component is reasonable, not a redesign of an entire page UI. Deliverables should be low fidelity sketches. Adaptive Path actually teaches that 10-15 minutes is optimum for sketching rough interface elements on a 6-up template, with no more than a few minutes per concept. They haven’t found that significantly more time improves the end-result at all. An exercise like this could even be done on the spot, or you can treat it as a take-home.

This being said, I’m not sure if I would have nailed this test when I was hired at Mint in early 2007. I had the portfolio (but no consumer UIs), I had an engineering background so I could build what I designed, but my process was immature, and my user experience understanding was lacking. However, I grew in the job, learned from everyone around me, from practice, etc. So I think these principles will allow you to compare individuals with a common framework, but if you find someone smart, passionate, a culture fit, and hungry for a win, you might get more than you expect.

P.S. I cross-posted on Quora if you’d rather join the discussion there.

500 Global Team

500 Global Team