Ron Peterson wrote:
>While I agree that we need to be focused on our users in
>designing the NGC or any other service we offer. I don't
>think we should, or even can, do that by "embracing their ever
>changing desires".
While Ron's comments are my jumping off point, this isn't directed
toward any specific comments. Also, please excuse my relative ignorance
on these matters. That said, it seems that a fruitful system approach
would be one that provides the flexibility for the system to dynamically
change in response to actual use of the system. This approach would
provide a means for the user to be an integral part of the design and
use. Some examples (in a library information system/OPAC design
framework):
- relevance and display uses of subject terms/tags/keywords associated
with works would change dynamically based on how users had searched and
retrieved the works (or like works with similar "cataloging" associated
with them)
- front-end design would be continually updated based on what existing
features are being used. In addition, new features would be
incorporated in beta format on a frequent, ongoing basis and
incorporated (or not) based on how these features are embraced using log
analysis. Adoption of new features would be accompanied by moving
unused or underutilized features to secondary screens.
- a blog that introduces all new features and proactively promotes
comments and surveys and feedback from users can be implemented
There are many other possibilities, of course.
Allen Mullen
Received on Thu May 03 2007 - 09:06:18 EDT