The Cone Trees network The UX Bookmark UX Quotes UX Jobs in Singapore Nice one yeah!

Interaction Design

Interaction Design

Guidelines for Aligning Data in Tables for Great Table Usability

Status: Work in progress (what is this?)
I have had the privilege to work across the User-Centered Design (UCD) process on banking websites and web applications such as Business Information Systems (BIS) and Management Information Systems (MIS). All of these are obviously data-intensive and it is crucial that data representation in both table and graphical representation [...]

When to Use Tables and When to Use Graphs

Status: Work in progress [what is this?]
I’ve done a fair amount of work in interaction deisgn for data visualization in MI (management Information) and BI (Business Information) systems, mostly around setting graaphical data representation and interaction guidelines for such applications. One of the most basic things which people get wrong again and again is when [...]

Future Healthcare Concepts

Summary
Here are two human-centered healthcare concepts I have come up with and imagine will be true in the future where technology and service design are applied to not only make the health care experience invisible (concept 1) but fun and way beyond simply retaining the human element (concept 2).

Concept 1: The Phone of the Future- [...]

When Introducing UCD in an Organinzation, Technical Capability is Only Half the Story

Summary
This article is a reproduction of my chapter in the book, UX Storytellers- Connecting the dots, edited by Jan Jursa of IATV. You can download it for free or get it for the Kindle at Amazon. Other contributing authors include Deborah Mayhew (author of Cost-Justifying Usability), Aaron Marcus (author of The Cross-GUI Handbook for Multiplatform [...]

Increase Conversions in Long Web Forms by Resolving the Accidental Back Button Activation Issue

In this article, originally published at Evolt, I talk about the issue of accidentally activating the browser back button through the keyboard while interacting with a long web form that is applicable to users across expertise levels. The time and effort wasted by the user can be said as proportional to the number of input fields filled by the user before accidentally exiting the page.

Since no application feedback indicating cause of the error to the user is provided, depending upon user expertise, the user may or may not realize the cause of the error. Realizing what is wrong does not guarantee the possibility of reverting the error either.

This leads to unnecessary loss in form conversions despite favorable user intent. A solution to resolve this issue (that I hope becomes standard practice) to plug the hole for lost conversion that translates to big numbers in absolute terms for high traffic websites is also provided.