Please note that this web site is no longer maintained. After a period of server problems what you can see now is a static version of Usor, without any dynamics that the text sometimes refer to.


Start page

Links and References

Alphabetical list of Methods

This web site contains descriptions of different user oriented methods. These descriptions are not meant to be exhaustive descriptions that you could use right after you have visited this web site. They are rather short summaries with references to more thorough descriptions of these methods.

The purpose of this web-site is to encourage the usage of user oriented methods in both industry and research projects. We also offer a place for discussing these methods, namely the Usor mailing-list.

It is important to remember that this collection and its content will not present one or a couple of methods that will guarantee the usability or user orientation of a project or a system.

This collection is not complete! All contributions are welcome.

All methods are classified with respect to three dimensions; Activity, User involvement, and Goal. See below for a description of these. Please note that all methods are classified according to all of these three dimensions.


These are four different activities that you engage in during a system development process. Most system development projects include these activities or at least similar activities that easy could be identified as one of these four.

Remember that we are not imposing any particular order or way of combining these activities. We are just stating that these activities are very common and easy to identify in many system development processes.

User Involvement

These are three levels of user involvement. It describes in what way the user is being beared in mind during the use of a method. This ranges from just thinking about that the system is going to have users to involving the users in the system development.

Remember that you can work in a user oriented manner even if the user do not participate.


The goal is the reason why the method is being used, for example if you are going to identify short-comings of an interface or if you are trying to measure the interface according to some usability criteria.

This page was maintained by Fredrik Winberg (
Suitable for any browser.