Before I started doing hardware design, I said "software designer". Like Josh I thought it helpful to focus on the product and found that "interface" was too technical.
Now that I do hardware, I'm "stuck" with "interaction designer" and the labor (of love) of explaining to people exactly what I do. In a way, It is actually a great opening ... "I'm an Interaction Designer" "What's that?" "Blah blah blah ... [chance to really teach people]." What I learned from "software designer" is that many people were left thinking I was a developer ... same for UI Designer, etc. This way I get to explain my role more completely. Sometimes a vague opening allows for a strong finish. :) -- dave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=34155 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
