Skip navigation.

Can a bad user interface be the gateway to horrible user behavior?

perspectives
So, I've been thinking about this for quite a bit. It all started on Saturday at the Indianapolis Workshops on Software Testing(IWST) when Mike Kelly showed us a something called a "Blink" test, based on the book of the same name by Malcolm Gladwell, test and phrase by James Bach. And, this led me to think about Malcolm Gladwell and testing. I'm just now getting through "Blink" but I tore through "The Tipping Point" very recently so I started thinking about what in that book might teach us something about testing, the very topic of the ISTW, to come full circle. And then it came to me - GRAFFITI!

In TTP Mr. Gladwell gives a compelling example (and forgive me if I am a bit loose with the details) about an epidemic of very serious crime in NYC and how the police force began to overcome (tip) this behavior, beginning with cleaning up the graffiti in the city, particularly the subway. It seemed quite surprising to most people that cleaning up the graffiti would deter much more violent crimes. However, it seems that the graffiti was in some ways representative of a culture of violence, a very subtle but accessible permission slip for the worst kind of behavior. And this permission slip went out to everyone in the city, available to all, so the behavior became widespread. Thus, the epidemic, the tipping point.

Ok, so what does this mean about testing? Well, graffiti itself is a representation, a type of art. But, art in the way that some sounds are noise and some are music. (I realize that all of this is open to interpretation and opinion but, for the sake of argument, let's consider that this graffiti is "bad" art because it was not commissioned, or wanted or permitted to be where it was, which is a critical part of its message and may have arguably been an important part of the impact it had on people.) Creating graffiti is also an act, which requires a creator, an artist. This artist could make "good" art or "bad" art.

So, and perhaps you will think this is a big leap, it seems to me that we can parallel this to the presentation layer, the user interface of a software application and the developers are the artists. They can make good art or bad art, a mural or graffiti, a comfortable and appealing user interface or a clunky, insensitive one. This much we all know is true. My question is, how does this impact our users? Can the user interface of our application be a tipping point for our users and, if so, what does it tip?

Now, I'm going to throw a few thoughts out there. Could a "graffiti" interface tip a user's sanity? Probably not, hopefully not. But, it is, of course, likely to tip them against the tool or product. Personally, I tip against anything I can't use comfortably, and quickly. That's why I like my cell phone but not my VCR, loooove copiers (one big green button) and hate hate hate fax machines (400 tiny buttons that mean nothing to me)! It's also why people still have lots of paper-based processes...they are more familiar and, therefore, easier for them.

So, back to what tips. I'm mostly thinking that an unusable interface that tips users in a negative direction will tip them into the same (proportionately, of course) bad behavior that the graffiti did in the city. What does that mean? It means, problem #1 They will rebel and not use the product you just spent tons of money on, and it will become a rent free shelf squatter for the rest of its life. #2 They will become angry at the product for being lousy and making their lives miserable, the vendor (or internal development team) for building such a lousy product, and the organization for making them use it.

This is all very bad. But, I think it gets worse. Then they talk about it, often, a lot, with many different people. And I'll throw out another "Tipping Point" thought. Gladwell says good size tipping groups are around 150 folks or less. I think this is a reasonable size for a small company using a new time tracking system, an accounting department using a new invoicing system or a team at an external client using your brand new extranet. What does this mean? This means that software applications are a prime target, or opportunity, for tipping internal or external customers.

Now that I think about it, Gladwell's archtypes - connectors, mavens and salesmen - are ripe for software tipping. This is not new, of course. They are our "evangelists" or "power users" or "product champions".

Ok, I think that's it for now. But, I want to think through this a little more. I realize none of it is really new, per say. But I think Gladwell's concepts and insights might be a useful way to view what we do about building user interfaces, and/or managing user satisfaction, if anything. If anyone has an example of software tipping, please post!

IT Conversations

There are some good talks by Gladwell on IT Conversations:
http://www.itconversations.com/shows/detail230.html

I think your insight is an important one. The fact that you can relate it to examples outside of IT is important. Syncretic thinking is important to our field. I think it makes for more compelling arguments and it certainly allows you to relate better to executive stakeholders.

-Mike

Tipping Point Perspective

Ok, so I need pick up the Tipping Point and Blink, I agree with Neill - books are going to break me. In my time in testing (short that it has been) I have seen a couple of things happen. Initially when I started testing applications were validated via the GUI interface and you had a team of testers who had the responsibility to validate the app via harnesses and the backend. Over the years something shifted the focus shifted to testing with harnesses and not bothering with the interface at all, we needed to make sure the application worked correctly we wanted to make sure the guts worked because that’s all that really mattered right???

I read an article about 2 years ago that in a nut shell stated that even if an application meets every requirement and works correctly, but the user can not utilize it correctly then the application is a failure. We need to find that happy medium and make sure that we keep in mind the fundamentals, You bring to light that while we need make sure we deliver an application that works correctly, we also need to validate and deliver application that have is good enough we need to remember the basics FURPS or “CRUPIC STeMPL” as James Bach once said. Both the acronyms contain Usability. While we are developing, designing and delivering computer software the people that use them software are not computers.

Just my thoughts

GUI Tipping points

There are definate tipping points in gui design and the human computer interface. Useability is important but undervalued and in my humble view often undertested for in the traditional software shop. The bad smell of a poorly designed gui can be found much earlier then the UAT where it is often checked fully for the first time and comments are taken into account.
I wonder if it is the same with new approaches to testing and development too, get 150 of the "right people" talking and thinking about it and we will see a tip in the industry as the new idea gains critical mass.
I will have to pick these books up, this blog portal is costing me a small fortune in books but at least it makes my journey from work a positive wind down time, and see how they apply to the testing I do. A useful and potentially powerful reframing of another idea.
Do not feel bad about not having the original, it is an equal value skill to be able to take and apply some one elses thinking successfully to a different context and here i think you have. That's what Jon Bach keeps telling me everytime I tell him of what I think is my latest break through...
Neill McCarthy
"Agile Testers of the World UNIT !"

Comment viewing options

Select your preferred way to display the comments and click 'Save settings' to activate your changes.