Two years ago, I went to the NNG Useability Conference. While I was there, I had the opportunity to see a session with John Pruitt and Tamara Adlin on the Persona Lifecycle. Ever since that session, I’ve been a big fan of Tamara’s, and had followed her blog “Corporate Underpants” (which has since moved here).
Corporate Underpants was a great idea for looking at how website content is organized. Basically, whenever you see content of a site organized in such a way that it reflects the internal structure of a company, you’re seeing the company’s “Corporate Underpants.” No one cares about your “Products Division,” “Service Division,” or “Human Resources.” They want to “buy a product,” “get help”, or “get a job.” Tamara argues, that a site’s content should be organized as to reflect the goals of your audience. Applying Tamara’s concepts to application, we can start thinking of user interfaces in the form of, Developer Underpants.
Developers are inherently lazy when it comes to the user interface design. It’s not their fault, their goals are just different. Developers live and breath logic and algorithms, they deal with absolutes. Developers don’t care where a button needs to go. If a button is needed, they make a button. Where do they put it, wherever there is space. In the end, applications become confusing, bloated with UI elements, and inconsistent experiences. They show their Developer Underpants.
I’m going continually add posts to this category discussing bad UI decisions. I’ll deal with Mobile Platforms. Mainly because I find it the most fun, and mainly because I think this fledgling landscape is ripe with abuse! We have the iPhone, Android, Windows Mobile, Palm WebOS, and Blackberry all competing to become king. As developers scramble to get their applications out to the greatest audience, they will be porting programs from one platform to another with disastrous results.
Time will tell what kind of trouble this category will bring.