Skip to content

Instantly share code, notes, and snippets.

@erikflowers
Last active December 11, 2015 07:28
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save erikflowers/4566691 to your computer and use it in GitHub Desktop.
Save erikflowers/4566691 to your computer and use it in GitHub Desktop.
A good answer to the "don't call yourself a UX designer" debate. It's doing more harm than good.
http://aaronweyenberg.com/1934/why-im-not-a-ux-designer-and-neither-are-you/comment-page-1#comment-2661
"UX Designer as a title seems meant to convey to recruiters
and teammates as an indicator of being evolved in one’s craft;
that you subscribe to Design Thinking. This moves the designer
away from the notion that designs are created in a vacuum,
without real human world context. It may also imply some
capability in UX Research, at least in observation and artifact
collection and generation. Point is, this posture is often
expected in the workplace and so the title is adopted.
Semantics do mean things to some people.
These are shifting times. We are socializing new job roles in
new kinds of work organizations. It is important to make
distinctions about such things as whether a designer is creating
an experience out of whole cloth that will be meaningful
to everyone the same way. The discomfort comes when we find
ourselves being skewed into role expectations differently
than the ways we see ourselves."
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment