Download ALPHA

2.4.3 What expert users need
Experts primarily demand faster access to their working set of tools, which might be quite
large. They will occasionally look for advanced functionality and will use it a lot to make
their work more efficient. An expert is eager to learn more and wants to find new ways to use
the program in his work. Experts appreciate new features. [5]
2.4.4 Wizards
A wizard works in a guiding way, directing users every step, not allowing them to fail. Every
dialog contains a question or two and in the end the program performs whatever action
decided in the dialogs. Wizards are written as step by step procedures, not letting the user
come with any suggestions. The user becomes a robot. Making monotonous tasks contributes
to the user negligence and risks that the user only presses a button in reflex not analyzing
why. The failsafe guide is then failing. This kind of guide is normally too demanding to be
used in daily services. [5]
2.5
Acceptance of Standard systems
This section talks about what to consider when implementing a standard system and how to
get it accepted by the members of the organization. According to Friman and Göransson in
[10] there are many factors to consider when in the process of anchoring a standard system.
These will follow below.
•
The user has to be given a chance to put the system in a context. They have to have a
total view and understand why the system is implemented. The system cannot change
the organization, only the people in it. Those people can only change if they want it
themselves. They have to understand the reasons to why they have to change.
•
Information has to be delivered in an early stage. This is because the user needs to
know what is going in order to feel in control. This will prevent users from getting a
negative view or from getting the wrong idea about the system. If the user already has
received a negative view it is much harder to change it.
•
It is important that the buyer and the supplier make a reasonable presentation of their
application so that the user does not expect too much. This is particularly important in
the case of a standard system, because the system is not complete when the buyer
makes his purchase.
•
The information given to the user has to be adjusted to the users’ previous
experiences. It has to be shaped in to a well designed strategy otherwise the user will
not adjust to it and accept the information. There are different approaches such as
push- or pull-strategies. Push-strategy is when the user is drowned with information.
Pull tries to either figure out what the user wants to know and then provides only that
information, or waits for the user to seek the information themselves.
•
Informal information can be used to find out which acceptance level the system has.
•
Education is an additional way for spreading the goals and ideas with the standard
system.
Ellen Andersson
Marielle Bergström
9