Lazy User Behaviour
In this position paper we suggest that a user will most often choose the solution (device) that will fulfill her (information) needs with the least effort. We call this “lazy user behavior”. We suggest that the principle components responsible for solution selection are the user need and the user state. User need is the user’s detailed (information) need (urgency, type, depth, etc.) and user state is the situation, in which the user is at the moment of the need (location, time, etc.); the user state limits the set of available solutions (devices) to fulfill the user need. The context of this paper is the use of mobile devices and mobile services. We present the lazy user theory of solution selection, two case examples, and discuss the implications of lazy user behavior on user attachment to mobile services and devices, and to planning and execution of mobile services.
If you experience problems downloading a file, check if you have the proper application to view it first. In case of further problems read the IDEAS help page. Note that these files are not on the IDEAS site. Please be patient as the files may be large.
| Length: | |
| Date of creation: | Nov 2007 |
| Handle: | RePEc:pra:mprapa:4330 |
| Contact details of provider: | Postal: Ludwigstraße 33, D-80539 Munich, Germany Phone: +49-(0)89-2180-2459 Fax: +49-(0)89-2180-992459 Web page: https://mpra.ub.uni-muenchen.de More information through EDIRC
|
References listed on IDEAS
Please report citation or reference errors to , or , if you are the registered author of the cited work, log in to your RePEc Author Service profile, click on "citations" and make appropriate adjustments.:
- Dale L. Goodhue, 1995. "Understanding User Evaluations of Information Systems," Management Science, INFORMS, vol. 41(12), pages 1827-1844, December.
This item is not listed on Wikipedia, on a reading list or among the top items on IDEAS.
When requesting a correction, please mention this item's handle: RePEc:pra:mprapa:4330. See general information about how to correct material in RePEc.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: (Joachim Winter)
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
If references are entirely missing, you can add them using this form.
If the full references list an item that is present in RePEc, but the system did not link to it, you can help with this form.
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your profile, as there may be some citations waiting for confirmation.
Please note that corrections may take a couple of weeks to filter through the various RePEc services.