In a previous workshop, we talked about what's necessary to call yourself a UX. Part of the problem is that UX is the evolution of the original "web designer"

In a previous workshop, we talked about what's necessary to call yourself a UX. Part of the problem is that UX is the evolution of the original "web designer" catch-all role, and many designers with a current title of Senior UX or IA or some such are really "grandfathered" into the role; they wouldn't be able to get hired for it today, because they didn't keep up. http://vi.to/workshop/20100621/2dlevels.png http://vi.to/workshop/20100621/2dlevels.png is an illustration that came out of the workshop, indicating at what experience level you should have various types of knowledge to be able to call yourself a UX: theoretical marketing knowledge, commercial concepting knowledge, etc. The 1-6 levels are the range of knowledge from beginner-to-expert, which come out of the "levels of knowledge" discussions from a few years ago: http://particletree.com/notebook/levels-of-web-development-knowledge/ http://particletree.com/notebook/levels-of-web-development-k... The (sorely incomplete) skills matrix, that provides the 1-6 definitions for each component is here: http://spreadsheets.google.com/pub?key=0Aqp_zIiwlin7dGN5QnBLY0MydlpYZlQybXVmWUYtZ1E&hl=en&output=html http://spreadsheets.google.com/pub?key=0Aqp_zIiwlin7dGN5QnBL... The illustration pegs everything at level 2, but it should actually be around where the green items are. I am totally open to additional input; we won't be revisiting this in the workshops for a while.