It's terrifying to think that anyone would need to be convinced...but
that's the reality of things, even today.
Even if an application is being designed for "everyone", there is still
a set of characteristics that are common to a dominant segment of the
audience. For example, amazon is a website for everyone, but how many
of those "everyones" have broadband? How many can read typefaces below
10 points? How many have the Flash 8 player? How many are first-time
users? How many are afraid to use a credit card on the internet?
Failing to understand these attributes or characteristics can be fatal,
even if the task analysis is sound and the functional requirements are
Dante Murphy | Director of Information Architecture
Medical Broadcasting Company | A D I G I T A S INC. COMPANY
MBCnet.com | t: 215/399.3456 | f: 215/545.4440 | m: 215.292.3144
How do you counter the argument that the product you're designing is for
How do I convince product teams to think through who their target users