I’ve just written an article on Chromostereopsis in UX Design, which you’ll find elsewhere on this site. I posted it as a regular web page (in my “Writings” section) because I felt its length and depth were too much for a blog post. So I’ve created this blog post to provide a place for comments.
I look forward to hearing what you have to say!
Today at 4pm EDT (I’m writing this about 5-6 hours earlier) the White House will have a live chat on improving Federal websites. I plan to be there.
I put in a comment via the form at whitehouse.gov. Here’s essentially* what I said:
The problem is not so much the number of Federal domains (although I agree that it’s probably too large), but the wide variation in information archecture and navigation for similar types of content. I’d like to see some standardization in information structure and navigation for overlapping content, and (even more importantly) in user-centered design processes.
I plan to “tune in” to the live chat this afternoon.
*I say “essentially” because I copied my comment to the clipboard before submitting it, planning to paste it here… but then I absentmindedly copied something else there while logging into my blog. So I had to re-create my comment from memory. Some of the words differ, but the sense is the same.
Yesterday I used a mobile boarding pass for the first time. United Airlines’ checkin didn’t make me choose between mobile and paper, so I chose both — it wasn’t a risk to try mobile because I would have the paper as a backup, just in case.
I clicked “Mobile” and had it sent to my phone via email. I then retrieved the email on my phone and tapped the link. The boarding pass opened just fine in the phone’s browser (see image at right).
The mobile boarding pass worked without a hitch. After saying he hadn’t done one before, the TSA agent led me to the machine, and I put my iPhone to the scanner. I probably held it there too long because I was expecting the scanner to beep, but he told me to remove the phone, and then he said “You pass!”
Using the mobile pass to board was even more straightforward. United’s gate agent was clearly used to them, and everything went smoothly.
So why is it not for me? Well, consider what I had to do to use it:
For me, it’s just more trouble than it’s worth. It’s cool and all that, but there are too many steps. I can tuck the paper pass into my passport (which I use for ID whenever I travel, even domestically) and it’s always right there in front.
Paper is very lightweight. It doesn’t need to be awakened or given a security code. I can check my email without sending it to the background. I can keep it in the same place and bring it out whenever it’s needed, without worrying about what else I might need it for. And I can even write things on it if I need to.
I’ll use mobile again if I am someplace where I can’t print the boarding pass. But when I can use paper, I will.
Do you use mobile boarding passes? What do you think of them?
I recently participated in a Dagstuhl seminar called “Demarcating User eXperience”. This 2.5-day workshop brought together 30 UX researchers and practitioners into an Eighteenth-Century manor house cum computer science conference center, just outside a tiny German village, to define the boundaries of the field of UX and begin writing a white paper about it. The seminar’s organizers described the problem this way:
The concept of user experience (UX) is widely used but understood in many different ways. The multidisciplinary nature of UX has provoked several definitions and perspectives to UX, each approaching the concept from a different viewpoint.
UX is seen as a holistic concept covering all aspects of experiencing a phenomenon, but we are facing the point where UX has become a concept too broad to be useful in practice. Practitioners have difficulties to understand the concept and to improve UX in their work, and researchers rather use some other term to make their research scope clear.
So our job was to “demarcate” UX.
Most of the group was from academia, so I set myself the goal of keeping some level of focus on practitioners’ needs, to maintain a balance. Each participant had to prepare a poster to present at the beginning of the seminar; mine is at http://www.luminanze.com/writings/DagstuhlPosterBuie.pdf (note: PDF). My main point was this:
UX already has a thriving practitioner community.
We must address their needs.
After the introductions were complete, we spent the next few days discussing UX — what it is, how it’s measured, how long it lasts, how to design for it — until finally our time ran out. (We could have gone on a lot longer, I suspect.) Fortunately, I wasn’t the only one urging that we consider design, and we ended up adding to the outline of the white paper a section on design for user experience.
At the end, we talked about next steps, in particular how we could publicize the seminar’s results. Among other things, we decided to submit a panel proposal to the CHI2011 conference. Jofish Kaye agreed to recruit the panelists and prepare the proposal; and two days ago when I asked him how it was going — surprise! — he added me to the panelists. This meant I had to write a position statement.
Now, I’m pretty good at writing short, pithy comments, such as tweets and Facebook statuses. A statement of two paragraphs, however, was much more daunting. But I managed, and here’s what I wrote:
“User experience” abounds and thrives in the practitioner community. Events and organizations identify themselves with the “UX” label — from “UX Magazine” (http://uxmag.com), to Adaptive Path’s “UX Week” conference (http://www.uxweek.com), to the various “UX Book Clubs” (http://uxbookclub.org), to the titles of numerous practitioner books. Nowhere is the label more evident than on Twitter: People and organizations use “ux” in their handles (@lynneux, @uxmike, @inspire_ux, @ux_jobs, @uxfactory, @ux_dc, etc. etc.), in content-related hashtags (#ux, #uxdesignjobs), and even in social hashtags related to the community (#uxsters, #uxlovelies, #uxboots). Even the Usability Professionals Association titles its magazine “User Experience”.
As practitioners, we generally agree that we are not designing experiences per se; “UX design” is just shorthand for designing for experience. We do lack a rigorous definition for “user experience” (we often refer to “DTDT” — “defining the damn thing” — to express the difficulty of agreeing on it), but I suspect we don’t actually need one. To design for experience, we don’t have to decide whether “experience” is immediate (e.g., three seconds) or it lasts from anticipation through memory of use; we need only recognize that it occurs throughout these phases and consider them all as we design. To create products that give users experiences along the lines of what we have in mind, we conduct user research and employ other time-honored as well as innovative design and evaluation techniques. We treat user experience as a focus in everything we do in our practice (see http://explainux.com), and most of us are passionate about giving our users good experiences. Academic research can help by paying attention to the issues of practice and by making sure we know when it has discovered something that can make us more effective in realizing these goals.
Unfortunately, space limitations meant that only a very small part of each panelist’s statement made it into the submitted proposal. I think the proposal turned out well, though, and I’m optimistic that the panel will happen. Stay tuned.
(I will write more about the seminar in a later post. For now you can see our photos on Flickr.)
Rome’s public transportation system, known as ATAC (Azienda Tranvie ed Autobus del Comune di Roma), continues to improve in the 20+ years since my first visit to this wonderful city. For example, some of the bus stops now have signs indicating when the next bus is expected to arrive (see the article in L’Occhio – in Italian). You can get info on your mobile phone about the routes and times, including when the next bus is expected (http://www.atacmobile.it). Some of the buses even have displays inside them that show information about the route.
Unfortunately, it seems that no one thought much about what information ATAC passengers would need and how they would use it.
The buses have two displays. One is at the front, with the line number and final destination scrolling across it (see image at right). About six inches high, this sign spans the aisle and is visible and legible from everywhere in the bus.
Problem is, it tells passengers something they already know. Once you get on the bus, you know which one it is and which direction it’s headed. Instead, what you need to know when you’re on the bus is how soon you will reach your stop.
But wait — there’s good news. These buses do list the next few stops. This information appears on a monitor in the middle of the bus. Unfortunately, there’s also bad news — the monitor’s screen is occupied mostly with advertising, which makes the names of the stops illegible from any reasonable distance. (See photo below, from mobytv.it.)
I suppose the advertising pays for the monitor and the information display — and in this sense it’s valuable — but it shouldn’t make the actual information hard to read. The obvious solution would be to replace the line/destination on the large dot-matrix display at the front with the name of the next stop. I’ve seen other bus systems do this, and it works very well.
I commend ATAC for their efforts to improve customer service by using IT to provide more information, and I’m not necessarily suggesting that they get rid of the mid-bus monitors,. They do, however, need to make the information legible to the majority of passengers.
I’ve read many comments from other user experience folks about listening to music while they work. Most of them express the same as I experience: I can listen to music while I am designing or constructing a site or prototype, but it interferes with my ability to write. For me this is true even for instrumental music, but it is even more true for music that has words.
I have long suspected that it may be a brain hemispheres thing.
For most people (essentially all right-handed people and the majority of left-handers), language is primarily in the left brain. According to an article in the July 2009 Scientific American:
Thus, writing and designing tend to use different parts of the brain.
So how does music fit in?
Well… Until I started doing the research for this post, I had the impression that music is processed primarily in the right brain, and I was thinking that it thus competed with a left-brain activity (writing) and complemented a right-brain activity (designing). This idea is supported by various sources, such as the Encyclopedia of Psychology, which states: “While the left-brain hemisphere performs functions involving logic and language more efficiently, the right-brain hemisphere is more adept in the areas of music, art, and spatial relations.”
But it turns out that things are not that simple, and that piece from the Encyclopedia of Psychology is nine years old. I came across a lot of contradictory research findings, exemplified by the following:
But the kicker is Daniel Levitin’s work, as described in his book “This Is Your Brain on Music: The Science of an Obsession”:
So why do so many of us designers find it difficult to listen to music while we write but helpful while we design? The answer is apparently not as simple as I had imagined.
Oh well, there goes a nice hypothesis. (At least I know better than to call it a theory. 
But here comes a potential research project.
And oh, btw — I would never say that “mathematics” is in the left brain. Having a graduate degree in mathematics, I know all too well that it depends on what kind of mathematics. I would place computation primarily in the left brain, but would suggest that geometry, abstract algebra, and possibly number theory are solidly in the right brain. (I remember that after struggling with multivariate calculus — as left-brained an activity as ever there was — I felt a great sense of relief to get into abstract algebra and find it so fascinating I couldn’t wait to get back to the dorm to do the homework. But most of my classmates didn’t see it that way.)
Every so often, the question comes up among interaction designers and usability professionals regarding whether alphabetical order is a logical order. (See, for example, the February 2009 discussion on the Interaction Design list.) We’ve all seen numerous lists that appear in alphabetical order (and in which it makes sense): country, state, surname, street name, auto manufacturer. We’ve also seen many that do not: month, day of week, browser history, File menu.
Alphabetical order is NOT a logical order. It may be the best order for a group of choices — i.e., it may be logical to use alphabetical order — but that does not make the order itself a “logical” order. It is only a predictable way of ordering a set that has no intrinsic logical order.
Don’t get me wrong; predictable is good. And sometimes — e.g., in the situations mentioned above — alphabetical order is the most predictable order.
But sometimes it is not, and yesterday I ran across a perfect example. Consider the figure at right. This is a list of car sizes in the preferences area of a travel application. Does the list look logical to you? I can never remember whether “economy” is smaller than “compact” or vice versa; and what in the world is “special”? I submit that size is the logical order for a choice of sizes (duh!).
Similarly, sequence is the logical order for a choice of months or days of the week. (Would you suggest putting April first? I didn’t think so.)
The objective is to choose an order that helps people find the option they seek and (if they aren’t sure) to help them identify the right option. Ordering the car size list by size would do both.
Are you listening, Carlson Wagonlit?
I’m delighted to say that, in addition to seasoned CHI-goers, I’ve recruited as CHI 2010 reviewers a number of strong UX practitioners who are new to CHI reviewing. Many of you have asked me what is involved in reviewing for CHI. Rather than answer you all individually, I am posting the information here.
The first round will involve reviewing papers and notes. Within a few days after 28 September, I will send each of you a few titles and ask you to tell me which ones you’d like to review. (You will receive titles targeted to the interests you’ve already communicated to me, to the extent that they match the titles I am asked to manage.) I need to get at least three reviews per paper, so if there are gaps or excessive overlaps in reviewers’ choices, we may have a wee bit of negotiating to do.
Once we have agreed which papers you’ll review, I’ll enter your choices into the CHI reviewer data base, which will take care of sending you the links to download submissions and enter your reviews. (It will also nag you about getting your reviews in.
Reviews of papers and notes will be due to me by 5pm EDT on 25 October.
The CHI review process is described at http://www.chi2010.org/authors/chi-review-process.html.
You’ll review submissions according to the guidelines provided by SIGCHI for the authors of submissions. The various types of papers and notes, and the criteria for each one, are described at http://www.chi2010.org/authors/selecting-contribution-type.html. (Although as of this writing I have not yet seen the papers I’ll be curating, I am confident that they do not include any theory papers.
The most important criterion for CHI papers and notes is that they contribute new knowledge, techniques, or approaches to the field. For practitioner submissions, this often means using established techniques in new ways or in new contexts, or interpreting findings in new ways. It may mean devising a new way of making usability methods more effective or efficient.
Note: The criteria for other submission types are less focused on breaking new ground than are those for papers and notes.
After papers and notes, we will be reviewing submissions for panels and case studies. These are due on October 9, so I expect to have my assignments by about 20 October, which would make your reviews due to me by about 17 November. (I’m just guessing here, as I don’t yet know the exact dates.)
After that, we have alt.chi, SIGs, and works-in-progress. Those submissions are due on 4 January, so I’ll probably be farming them out starting about the 15th and expecting your reviews by about 10 February. Again, just a guess.
If you have signed up to review — or even if you are just thinking about it — please feel free to contact me with questions. You may email me at ebuie [at] luminanze [dot] com or use my Contact Us form.
This workshop will bring together researchers and practitioners of human-computer interaction to explore whether and to what extent difficulties exist between them — and, if so, will endeavor to identify the dimensions of the problems and propose possible solutions. On the one hand, we will work to articulate factors that may render the research literature inaccessible or irrelevant to practitioners and to suggest potential improvements and approaches. On the other hand, we will also strive to learn from researchers how their research could benefit from practitioner input. We invite practitioners and researchers to submit a position statement of up to four pages, plus a short bio, by email to ebuie [at] luminanze [dot] com by 5pm EST on 6 January 2010 (note new date), to participate in this one-day workshop.
Your position paper should attempt to answer one or more of the following (or related) questions:
We will select a variety of viewpoints from participants with diverse experience. Participants will have access to all of the accepted position statements in advance, to facilitate pre-conference discussion and to support the formulation of discussion questions. The organizers will also publish a draft agenda to prepare for the in-depth discussions during the workshop.
Up-to-date information on the workshop will be available on this blog post, which can be reached directly at http://bit.ly/CFP-CHI2010-RPI
Please note that participants must register for the workshop and for at least one day of the CHI 2010 conference. Fees for a one-day workshop at CHI 2010 are estimated to be $175.
Please feel free to contact any of the organizers with questions.
Luminanze Consulting, LLC. 
2909 Collins Avenue Silver Spring MD 20902 USA
tel +1.301.943.4168 or +39.347.394.7022 email info [at] luminanze [dot] com
Copyright © 2007-2010 Luminanze Consulting, LLC. All rights reserved.
"Luminanze", the Luminanze logo, and the phrase "User experience, done bright" are trademarks of Luminanze Consulting, LLC.
These pages contain Access Keys.
2 December 2011
Usability in Government Systems — A Forthcoming Book
Just before US Thanksgiving of 2011, my co-editor and I delivered to our publisher the manuscript of a new book on usability in government systems. Two and a half years after Dianne Murray suggested doing a book and we chose the topic — and six weeks after I began the most intensive period of work in my life (on the book) — we completed the manuscript and sent it off. And so was born Usability in Government Systems: User Experience Design for Citizens and Public Servants.
Bookstores abound with offerings on “usability” and “user experience” (2,352 and 293 search results, respectively, on Amazon.com as of this writing). The number doubles for “government contracting” (4,275 results) and jumps by almost 50 times for “government systems” (106,957 — again, as of this writing). This book, however, is unique. A search on “usability and government” does find 89 titles — books on e-government that mention usability as a success factor; government publications that offer usability information related to a single domain, such as web design or aviation cockpit displays; conference proceedings that include academic research papers on usability in e-government. But not one of these titles covers the topic broadly or focuses on it exclusively.
Yet countless citizens worldwide use government web sites and other systems to obtain information from their government and to do business with it. Tremendous numbers of government employees conduct their nation’s business via desktop computer and intranet sites. It is impossible to say exactly how many people will use a government system themselves during their lifetimes, but it is a safe bet that these systems will touch everyone’s life in some way.
But how usable are these systems? How consistent and predictable are the web sites for those who have to navigate the maze of government information and online services? How well do internal applications support the productivity of government employees? Functionality apart, how well do government systems actually serve the citizenry?
The United States Government is the largest consumer of information technology in the world. In the summer of 2011 the White House reported that the government had a shocking number — more than 24, 000 — of different web sites. President Obama announced the Campaign to Cut Waste, whose charter includes finding ways of presenting the public with Web-based information and services that are better connected and more consistently presented.
Other governments have had similar concerns. In March of 2004 the United Kingdom launched DirectGov to consolidate access to much of its national government information for citizens, and in January of 2007 it announced a decision to eliminate almost 60% of the 951 sites it had at the time. As of this writing, the United Nations has issued two reports on e-government, and the Association for Computing Machinery has held several annual conferences on e-government, in whose 2011 conference Dianne and I participated (along with our colleague Scott Robertson, who wrote the foreword to the book).
Almost every national government in the world has at least one public web site, and we would be surprised to learn of a government that didn’t have computers, at least in its national offices.
And yet no book exists that addresses usability in government systems. Until now.
This is the first book that concentrates on the role of usability in government systems. It covers designing government systems to provide effectiveness, efficiency, and a pleasant and satisfying experience to the people who use them, whether they are interacting with their government from the outside or working for the government on the inside.
The book’s 24 chapters, each written by one or more experts in the topic, cover topics as varied as open government, plain language, accessibility, biometrics, service design, internal vs. public-facing systems, and cross-cultural issues, as well as integrating usability and user-centered design activities into the government procurement process. It speaks to three audiences:
The book takes an international perspective and includes many case studies from government systems around the world.
Usability in Government Systems: User Experience Design for Citizens and Public Servants can help increase government cost effectiveness, operational efficiency, and public engagement. It will be published by Morgan Kaufmann Press in May of 2012. It can be preordered from Amazon here. (I’d greatly appreciate it if you’d use this link, as the royalties are not high and this gives me a small commission as well.)