I am working in an organization that is focused on doing quick,
lightweight usability research, especially once the work has a good
foundation: bringing a design into a coffee shop, for example,
running 5 quick (15 minute) studies, making changes, showing 3 more
people the next day, etc.
In this model, I've seen things get revised and re-tested 10 or more
At the same time, there is a formal research organization that would
like to have all the results organized and indexed so they can find
I have to do a presentation (at very short notice for a job interview)
on improvements to a search interface for clinical data. Does anybody
know of any useful resources that focus on the design and usability
of search interfaces. Thanks
Most of the time while working with heavy data intensive application I
have encountered that there is 20 to 30% of the
modules/webparts/portlates/functionality are rarely useful for the
end-users in most of the applications for example elements like News,
Article, Record Summery, Archive Records, User Summery, Report
My name is Andrea Richeson. I have worked in web design and
development for Texas state government for several years and am
currently a graduate student at the University of Texas School of
I am working with Dr. Randolph Bias, Dr. Eugenie Bertus, and graduate
student Jana Tate to co-author a book chapter on the use of return on
investment (ROI) methods.
A friend and sometimes client told me over lunch this week, "I think
of you as the usability guy." I didn't much care for this, because
I think of usability in terms of activities rather than an identity
to aspire to. It got me thinking about related terms, like "user
experience" (UX), and its cousin, user-centered design (UCD).
Hello. I am about to begin designing a usability study on a government
website and evaluating the accessability of the site will be a big
component. I'm looking for advice on comparing data from the
visually disabled participants (using screen readers and magnifieers)
to participants with typical vision.
In a meeting today, a client said they wanted a single-page checkout
process. The checkout tunnel is an area that I prefer to have as
vanilla as possible so that customers have no surprises, but I am
open to change.
I've never done any testing on one-page vs. staged checkout, and I
haven't been able to find any data, only opinions. Does anyone have
any non-proprietary data they'd care to share about one-page