Administrators Anonymous
A good presentation about user centered design for administrators. This is an audio presentation by Stanford Online ...
"The lack of focus on administrative interfaces often comes from management's mandates to prioritize end user facing screens ahead of anything else. The number of "eyeballs" is greater for the end user screens than admin screens. It is also easier for all stakeholders, including interaction designers to understand the domain of an e-mail application than it is to grasp things like complex system monitoring, visualization of clickstream data, or the tools needed to bridge interdependent systems. However in more complex software, this initial emphasis on the end user turns out to be a short lived priority. The more significant costs of running software are often associated with installation, configuration, deployment, maintenance, and upgrade. Often, this is referred to as LCM, or Lifecycle Change Management. Industry estimates state that the budget for LCM can be 2-4 times as large as the initial license cost of enterprise software. More information is needed about how administrators work to manage these systems and what business and integration problems they are trying to solve. UCD, or user centered design can help answer these questions.
The administrator is often a misunderstood user type. Experts have recently started to shed light on this subject. As reported in this forum by Rob Barrett of IBM Almaden, administrators cling to their shells, scripts, and other command line utilities. We create GUI tools for them, but is that what they really need to lower the Total Cost of Ownership (TCO) of software, or to be more efficient when communicating with each other? What are the real frustrations in a given admin's day and how can Human Computer Interaction practitioners help them?" continued ... (Via Stanford HCI - Luke Kowalski)
"The lack of focus on administrative interfaces often comes from management's mandates to prioritize end user facing screens ahead of anything else. The number of "eyeballs" is greater for the end user screens than admin screens. It is also easier for all stakeholders, including interaction designers to understand the domain of an e-mail application than it is to grasp things like complex system monitoring, visualization of clickstream data, or the tools needed to bridge interdependent systems. However in more complex software, this initial emphasis on the end user turns out to be a short lived priority. The more significant costs of running software are often associated with installation, configuration, deployment, maintenance, and upgrade. Often, this is referred to as LCM, or Lifecycle Change Management. Industry estimates state that the budget for LCM can be 2-4 times as large as the initial license cost of enterprise software. More information is needed about how administrators work to manage these systems and what business and integration problems they are trying to solve. UCD, or user centered design can help answer these questions.
The administrator is often a misunderstood user type. Experts have recently started to shed light on this subject. As reported in this forum by Rob Barrett of IBM Almaden, administrators cling to their shells, scripts, and other command line utilities. We create GUI tools for them, but is that what they really need to lower the Total Cost of Ownership (TCO) of software, or to be more efficient when communicating with each other? What are the real frustrations in a given admin's day and how can Human Computer Interaction practitioners help them?" continued ... (Via Stanford HCI - Luke Kowalski)
Seminar on People, Computers, and Design.
0 Comments:
Post a Comment
<< Home