Designing the experience (not defining it)
Over and over again, it seems, practitioners within the User Experience world stir up flame wars and heated debates about what it is exactly that we do and what it should be called. From Interaction Design to User Experience Design to Information Architecture to UI Design, titles and job specifications vary as frequently as Sean Combs’ stage names.
Here’s a suggestion: stop trying to define the damn thing and, instead, design the damn thing.
Design it. Get your hands dirty. Make sketches, push pixels, build prototypes and create experiences. Just do it. Forget your title. Forget your job description. Focus on the business problem you’re solving. Then figure out what you’re best capable of doing that will lead to a successful solution for that problem. Work within your organizational constraints or break new ground. Regardless, solve the problem. Understand your user. Understand the business goals. Do the right research and apply that learning to the solution.
Instead of using titles and job specs to describe the value you bring, show it. If you spend your time designing the experience and solving problems instead of defining where your cog fits in the machine, your true value will become obvious. The more your value becomes obvious, the less the need for specific job titles and descriptions.
Pretty please, let’s stop defining the name, boundaries and specifications of our profession. Instead, let’s solve problems, innovate and simply design good experiences.
[Jeff]
