Why ask for billing address first?
I’m working on a new checkout flow. I’m wondering why most e-merchants ask for billing address first instead of shipping address ?
People are more likely to understand shipping address than billing address. So why not put sh…
Why ask for billing address first?
I’m working on a new checkout flow. I’m wondering why most e-merchants ask for billing address first instead of shipping address ?
People are more likely to understand shipping address than billing address. So why not put sh…
User Manual vs User Guide vs Documentation vs Quick Reference vs Handbook
I am aware this has already been asked at http://english.stackexchange.com/questions/59224/what-are-the-differences-between-manual-guide-and-instruction however from a user experience point of view, what is the most straightf…
Why most of the microphones are placed on the left of headsets / headphones?
I’ve noticed that the mayority of the well-known brands (Sennheiser, Logitech, Plantronics, Razer, SteelSeries, Audio-Technica, Phillips, etc) tend to make headsets with the microphone on the left, is there any UX related rea…
What are the advantages of a card-centric user interface?
It’s being reported that Google is moving to a “card-centric” redesign in the upcoming Android-5 O/S.
Is it more responsive?
Is it more intuitive (quicker to realize how to do things)?
Does it use less memory thus allowing …
The Keikendo Maturity Model for developing an organization’s UX capabilities
I saw the Keikendo Maturity Model of an organization’s UX maturity and immediately thought of the paper by Jonathan Earthy that talks about the Usability Maturity Model. Comparing the two side-by-side:
Usability Maturity Model
Unrecognised -> Recognised -> Considered -> Implemented -> Integrated -> Institutionalised
Keikendo Maturity Model
Unintentional -> Self-Referential -> Expert -> Centralized -> Distributed
There seems to be a lot of similarities, and it also relates to the Nielson Group’s Usability Maturity Stages 1-8. Aren’t they all talking about the same thing, so why do they all need different names? I think we probably recognize the lower and higher levels of UX maturity, but there are more blurs when it comes to intermediate levels because of the nature of the different organizations.
Has anyone tried to apply/adopt this model with any success? Or does anyone have any opinions or ideas about the model compared to similar models?
The Keikendo Maturity Model for developing an organization’s UX capabilities
I saw the Keikendo Maturity Model of an organization’s UX maturity and immediately thought of the paper by Jonathan Earthy that talks about the Usability Maturity Model. Comparing the two side-by-side:
Usability Maturity Model
Unrecognised -> Recognised -> Considered -> Implemented -> Integrated -> Institutionalised
Keikendo Maturity Model
Unintentional -> Self-Referential -> Expert -> Centralized -> Distributed
There seems to be a lot of similarities, and it also relates to the Nielson Group’s Usability Maturity Stages 1-8. Aren’t they all talking about the same thing, so why do they all need different names? I think we probably recognize the lower and higher levels of UX maturity, but there are more blurs when it comes to intermediate levels because of the nature of the different organizations.
Has anyone tried to apply/adopt this model with any success? Or does anyone have any opinions or ideas about the model compared to similar models?
How to indicate that specific sections of a page can be swiped
There are a lot of mobile UI design patterns that support swiping, and these are designed based on interaction and animation that indicate the behaviour. Examples include the ‘swipe/pull down to refresh’ and also the page fli…
How to display save/cancel actions in an accordion
I’m in the middle of designing a setup flow and have decided to go for an accordion paradigm (due to the large amount of steps, using tabs would result in tab overflow in mobile devices). Upon entering the setup flow, the use…
How to display save/cancel actions in an accordion
I’m in the middle of designing a setup flow and have decided to go for an accordion paradigm (due to the large amount of steps, using tabs would result in tab overflow in mobile devices). Upon entering the setup flow, the use…