- We design and build extraordinary applications for companies looking to make the next great idea a reality.
- learn more
What is UxD?
A couple of weeks ago a sales presentation was being prepared in our New York office; it was primarily focussed on the problem at hand, but the presenter wanted to include a single slide as a cue to talk about User Experience Design [UxD]. He emailed me and a couple of the principles asking for a description in a single frame.
I wrote something, designed two slides because I could not shoehorn it into one, various documents were thrown into the air, then we were all consumed by other work as the train moved on.
Now I am rethinking it. UxD is a fairly complex set of activities to describe, and there is no shortage of areas claimed by related disciplines. All of them are occurring in an area of rapid market development that happens to be highly valued by the societies we are in. Which is a recipe to attract passionate debate driven by financial rewards.
So is there a good way to describe it, or state it's value to a potential client in a single powerpoint slide? Assuming that no fly-ins, starbursts or windowshade rolls may be used in place of meaning, we will start with those old standbys - words:
________________________________________
Concise version:
User Experience Designers create structures for understanding and manipulating information, designing consistent contexts which encourage cumulative learning. In doing so they raise the bar from "being able to do something" to "being able to do something easily".
Their solutions go beyond code to model the most efficient and pleasing conceptual space that can be created within the constraints of time, budget & resources.
________________________________________
Verbose version:
User Experience Designers are typically employed on applications or sites with large amounts of features, complexity or information.
They create structures for understanding and manipulating information or parameters, designing consistent contexts which encourage cumulative learning.
They raise the bar from "being able to do something" to "being able to do something easily". As a starting point they conduct research to find:
_Who are the users?
_What are their goals?
_In what context will they use the product?
Then they use any modeling technique available to propose solutions that go beyond code to model the most most efficient and pleasing conceptual space that can be created within the constraints of time, budget & resources.
________________________________________
And this is just a starting point for discussion, and the slide itself is TBD. The concise version is hardly meant to be all encompassing, but it focuses on Pathfinders particular business goals. These are concentrated in application work, either in or out of a browser, and our communications tend to be directed toward fairly tech savvy folks. Interested in your comments.
Charles
Comments: 1 so far
Leave a comment
About Pathfinder
Recent
- Pimp my jQuery: Five plugins to replace the features Prototype and Scriptaculous users expect
- Thanksgiving 2008: What We’re Thankful For (In Rails)
- iPhone SDK: Testing with TextMate & GTM
- GWTQuery - JQuery-like Syntax in GWT
- Ask the readers: How do I fire native browser events in Prototype.js?
- News Rollup for the Week of November 17, 2008
- Rails ThreatDown!
- Automated Deployments Rock
- Bandwidth profiling Flex projects and more with Charles
- iPhone SDK: UIViewController Testing & TDD
Archives
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006


Charles,
UxD is a meaty (or mushy) term to define. You’ve done as well as any, I’d say.
I’ve given it a lot of thought, and while the origins and practical application of the term are quite clear to me now, those tugging at the edges of it, towards the camp their design discipline lives in, do us all a disservice, I think: it is and pretty much always was a user-centric approach to web-based communications/software systems.
I’ve put my name in the ux design definition hat too, after too much thinking about it and finding too little online to my liking:
http://uxdesign.com/ux-defined/
http://www.interaction-design.org/encyclopedia/user_experience_or_ux.html - does a fair job, too, if leaning more the the multidisciplinary side, which I see no point in.
My approach is more casual, as I don’t represent some “serious” professional association, or what have you, with a reputation to protect. But then we shouldn’t take it all too seriously anyway, aside from the actual results, no?
Michael
Comment by uxdesign.com, Saturday, September 8, 2007 @ 9:09 pm