A little background to start: I’ve had the honor of working as a designer-in-residence for General Assembly’s User Experience Design Immersive Pilot Program (UXDI) from June through July. Our team built, launched, and taught a UX course 5-days a week, 8-hours a day, for 8-weeks straight. It was quite the challenging, yet rewarding experience.
However, learning from our approach, I found something about the way we bring people into the fold that we can stand to improve.
We instructors spent much of our early days teaching techniques by going through truckloads of slides. We sent students home to read more chapters and articles loaded with paragraphs after paragraphs of definitions and use cases.
Yet, when students have trouble with a particular technique or concept during their free practice time, we’ve always had to re-explain to them the crux of these ideas with piercing simplicity.
Why don’t these simple core ideas exist in a simple, more easily referenceable form?
Looking up any UX terminology in Google results in many results: incomplete lists long abandoned, or gigantic lists of terms with accompanying paragraphs–and that’s only if you’re lucky enough to avoid the full blown articles. At a time when Dieter Rams’ As Little Design as Possible is common advocacy, we can present the fundamental impressions of UX’s core capabilities as something much more succinct than a wall of text. I’d argue that we would want the same considerations for our own products and content.
I have a modest proposal. Introduce the essence of your techniques and concepts in a single sentence. Do it in a one-liner. If it goes beyond one sentence, make it shorter.
Understand that these one-liners are NOT meant to explain UX techniques or concepts as well as articles or lengthy discussions can. Likewise, the real substance behind any of these techniques and ideas will expand and change over time, context, usage, and the like.
However, my contention is that there should be a much simpler and more concise way for people to see to the fundamental core of a technique or idea. For any confusion and disagreements that exists within the UX community, one of our common goals is to better communicate our ideas and intents to our teams and colleagues so that we can better create.
Why not then reconsider how we communicate the most basic fundamentals of what and how we work?
UX has always had a rich tradition steeped in academia, which is often somewhat verbose. It’s only relatively recently that its relevance to the consumer world has been realized on a massive scale. As UX adapts to a rapidly shortening cycles of technological–and by proxy, behavioral–change, we need to consider simplicity and conciseness in introducing the rest of our world to not only the products we design, but also the universe in which we create.
There will be another session of UXDI session beginning in September. I’ll be preparing a list for the students to use. Would you do it for a class you taught?
Here’s to an improved UX of UX.
Here are some one-liners I think adequately communicate the focus of their associated techniques and methodologies. This is a start. Add your own in the comments.
|Activity in which users organize a set of data in ways that they think makes sense.
|Ethnographic Interviewing technique where the user is observed using products in their natural usage setting.
|Interviewing techniques combining one-on-one interviewing and extensive observation.
|Preset categories used to filter information/content into more digestible chunks.
|Quick rules of thumb used to streamline design decisions.
|Data used to categorize other data.
|Description of fictional yet realistic persons that represents a target user group/market.
|A story describing a user’s problem situation and how she might use a product to achieve a solution.
|Modular diagram conveying your site’s page inventory and, to a lesser extent, categories.
|A test conducted with end users to see how usable they find a product.
|A path map highlighting what a user has to do within your product to accomplish his goals.