A Typical UX Team of One Job Description

Jared Spool

September 21st, 2016

This week, we revisit Leah Buley’s book, The User Experience Team of One – A Research and Design Survival Guide.

Here’s an excerpt from the article:

If you happen to be in the job market, it can be helpful to know how to spot a UX team-of-one situation. Few UX jobs are advertised as a team-of-one gig, but there are usually telltale signs that give them away. This job description shows an employer who is looking for someone who can drastically improve the quality of the user experience. The product will be “elegant,” reduced to the “bare essentials,” and “beautiful.” People may not say it directly, but there’s usually an expectation that having someone who will focus on UX will result in changes to the product that will immediately wow everyone. This can be a tricky expectation to manage, since design improvements often happen gradually, over time. The design methods in Chapter 7 show you how you can improve the quality of the product and bring people along with you in the process.

Read the article: A Typical UX Team of One Job Description

Leah presents Strategic Storytelling at the September 22 UX Virtual Symposium: Storytelling in Design.

How have you identified Team of One jobs? Let us know below.

One Response to “A Typical UX Team of One Job Description”

  1. Mark Pawson Says:

    I needed this book ten years ago when I was at best a team of two but most times a team of one. I even remember posting on IXDA.org if such a book existed because I needed help. I was a lone wolf in a company of over 3000 employees spread around the globe with multiple projects. Best I could do was expert reviews and act as a facilitator for teams in UK and US who were designing similar interfaces and had no idea that each team was reinventing the wheel.
    Then I moved to a small company with offices in North America and China with a research scientist bent where UX was seen as Excel spreadsheets of right click menu function described in elaborate detail of when a function was active or not. Both of these places talked UX but did not walk it.
    The one thing I learned from ads such as the one in the article is the company is asking for work that would require a team to do effectively. However, the company does not understand UX effort so they write this really exciting sounding ad. They do not intend to give the lone wolf any support because they think its magic. As the article states, they clearly do not understand UX but have read some article on user experience, or been to a talk and thought we should do this. From my two experiences I learned that both companies wanted a developer who could just make their interfaces look really cool. Icing without the cake. The cake was too costly.

Add a Comment