Monthly Archives: December 2013

UX Links for the week ahead (Week 3)

Every week i will feature a few UX links to get you set for the coming week.

This week i’m posting: an idea for desktop browser loading bars that is borrowed from mobile browsers, an article by Robert Fabricant about scaling your UX strategy, a look at the psychology behind dashboards,  an interview with the UX Explorers at Ford and finally a good read about the intersection of UX, CX and corporate strategy. Enjoy!

  1. New UI Pattern : Website Loading Bars http://www.usabilitypost.com/2013/08/19/new-ui-pattern-website-loading-bars/
  2. Scaling your UX Strategy http://blogs.hbr.org/2013/01/scaling-your-ux-strategy/
  3. The Psychology Behind Information Dashbaords: http://uxmag.com/articles/the-psychology-behind-information-dashboards
  4. The UX Explorers at Ford: http://uxmag.com/articles/the-ux-explorers-at-ford
  5. The Intersection of UX, CX & Corporate Strategy http://connect.humanfactors.com/profiles/blogs/the-intersection-of-user-experience-customer-experience-and-corpo

An interaction that bugs me (Part 1)

There’s an interaction I perform at least once every couple of days. It annoys me how inconsistent the design and interactions are.

I’m talking about cash machines or ATMs.

I believe this is a global phoenomenon.

It’s incredible to think that in this day and age of such advanced technology and interaction procceses, the advancement of most cash machine interactions around the world, seem to have stood still.

One could assume a couple of factors have lead to the current state of affairs: • Each banks appears to have thier own individual approach and power
• There is not a global or even localised institution leading, testing and improving

As a result of this, users need to think and learn new interfaces. Thinking takes, and wastes time.

In Manila i havn’t found 2 bank machines that follow the same design patterns or flows. There are inconsistencies in flow, button layout and even terminology across different banks. Some banks even have differing interfaces between their own machines.

I like to think i’m very efficient at using cash machines, infact it annoys me when the people in front of me takes their time to withdraw money.

I have a mental note of approximately how much money i have in my account, so i dont need to do a balance inquiry before withdrawing. I have observed that lots of people don’t do the same, they need to check their balance before selecting how much to withdraw.

For starters, this begs the question, why on earth are these two interactions treated separetly? Why not display the available balance on the cash withdrawal screen as a visual reference?

It occured to me that maybe i’m strange, because i opt to use any machine that is available (regardless of charges incurred) rather than sticking to my own bank. I’m pretty sure i’m not the only one, but even if i was there is surely a much better way to design such a commonly used set of actions.

Do you experience this in the countries you live in?

Is there a way to standardise cash machine interactions?

Join the discussion on the friends of the intercation design foundation linkedin group

UX Links for the week ahead (Week 2)

Every week i will feature a few UX related links to get your set for the coming week.  This week i’m posting some best practises for creating cross platform mobile apps, a link to the design & thinking official trailer (which looks great), Richard Branson’s take on knowing when to give up on your idea, an interview with Victor Lombardi and a blog post about why responsive design won’t fix your content problem. Enjoy!

  1. Best practises – creating cross platform mobile apps: http://thenextweb.com/dd/2013/11/26/best-practices-building-cross-platform-mobile-apps/
  2. Design & thinking official trailer: http://www.youtube.com/watch?v=uilcaXYnluU
  3. Knowing when to give up on your idea: http://www.entrepreneur.com/article/230093
  4. Fail Fast, Fail Often: http://www.uxbooth.com/articles/fail-fast-fail-often-an-interview-with-victor-lombardi/
  5. Responsive Design won’t fix your content problem: http://alistapart.com/column/responsive-design-wont-fix-your-content-problem