Getting to Consistency

I just found slides from the SXSW Interactive Panel I moderated back in 2007. Making software predictable and consistent makes it much easier to use. This session will explain UI consistency and point out examples of failures and their consequences. We’ll discuss when it’s appropriate to break consistency, and how to build tools and process …

SXSW Interactive Panel Proposal: Abort? Retry? Failwhale? Making Error Messages Suck Less

I’ve proposed a panel for SXSW Interactive: Abort? Retry? Failwhale? Making Error Messages Suck Less. Here’s how I described it: An unknown error occurred. Call your system administrator. Abort/retry/fail? Bad errors are everywhere. Sure, complain on twitter. But how do we fix them? Through hilarious examples, we’ll explore the 12 ways errors fail us. Then, …

Design roundup: PC Financial, Canada Post

My favourite Canadian bank, PC Financial added a brilliantly designed feature to their ATMs: No more addition mistakes. Enter checks one at a time, and let the ATM do the math. So smart! Why didn’t anyone think of that before? Wells Fargo does this now, too — they scan the checks and read the amount …

Understanding user needs…in Africa

Jakob Nielsen, look out. Parker Mitchell has a few things to say about the importance of understanding user needs: In particular, we will propose that the efforts of people in this room ensure that technology development efforts better incorporate the functional, economic and social/culture realities of prospective users. In my case the “users” are rural …