With this thesis we have been interested in how to utilise an user interface beta test period. Which activities are appropriate to be performed, with focus on how activities contribute to user interface validation, further user interface improvements, and improvements of the user interface roll‐out. Additionally we have tried to couple this to end‐user satisfaction and acceptance of this new user interface, since the usage of the system is mandatory for the end users.
We have approached this by developing a method that is based on four different perspectives. Three perspectives are studied theoretically, and one perspective is based on empiric research. These perspectives are separate from each other; to combine them we have used a common denominator of increased system usage. This denominator is derived from a viewpoint upon end‐users and how user satisfaction, user acceptance, and behaviour incentives for usage affect the perspectives and consequently our result.
This broad research has resulted in a self‐sustaining method that we describe both in an overview and in greater detail explain the beta period and the associated roles, the different activities and how they should be executed in relevance to time. For every activity a table of considerations, i.e. when, who, how, and why are presented together with an explanation how the activity can influence end‐users to use the system.
We conclude that the result of this thesis will aid and guide vendor companies through the beta testing program of a new user interface. The resulting method determines which activities that can be of interest to carry out and how these will contribute to future development and/or improve roll‐out. By utilising this method as a framework we see the possibility to incorporate it in an existing user-centre development process, but it can also be used as a simple, straightforward, and self‐sustaining method.