Archive of Interface Design Articles

Just Plain BadLameAverageGoodGreat (2 votes, average: 4 out of 5)
Loading ... Loading ...
January 17th, 2008

User Adoption ROI

using or bypassing the software

You want your software to be used, not to sit on the shelf. You can’t achieve the ROI of your software if people don’t use it. And you can’t achieve the ROI of your software by forcing people to use it either.  Some will fail to achieve the benefits, and others will delay using it or refuse to use it entirely.  You have to make them want to use it, and you have to design the software for the users who must use it.  Otherwise, you won’t achieve the ROI.

Just Plain BadLameAverageGoodGreat (2 votes, average: 4.5 out of 5)
Loading ... Loading ...
December 20th, 2007

Global Actor Hierarchies and Personas

Actor Hierarchy

We use actor hierarchies to organize the different users of a system. Different people play different roles, and thus do different jobs. We use different actors to identify and organize those people. When deploying a system globally, we usually discover people that do the same jobs, but do them differently. Incorporating the notion of personas lets us deal with this.

Just Plain BadLameAverageGoodGreat (3 votes, average: 2.67 out of 5)
Loading ... Loading ...
July 25th, 2007

Interface Design: Visualization Methods

periodic table of visualization techniques

Visualizing complex data can be very difficult. There are almost as many ways to visualize data as there are data to visualize. The Ralph Lengler and Martin J. Eppler at the Visual Literacy Organization collect many of them for us in a periodic table.