This paper is about the kind of tools and techniques that are accessible to resource weak groups for use in design and evaluation of computer support. ‘Resource weak’ means in…
Abstract
This paper is about the kind of tools and techniques that are accessible to resource weak groups for use in design and evaluation of computer support. ‘Resource weak’ means in this connection, that the economic power and the ability to control the ‘local environment’ of the group is limited. The human resources of such groups are often (potentially) strong, but restrained by the organization of work and society; and although the tools are cheap the activities are demanding in terms of human resources. This kind of work should be seen as a supplement to participation in design processes controlled by others. When end users participate in projects set up by management, these ‘lay’ designers often lack familiarity with the tools and techniques, they lack the power and resources to influence the choice of questions to be considered, and they are not the ones deciding how to utilize the results of a design project when actually changing the workplace. To give the context of the work on which the paper is based, I first describe the Scandinavian tradition of trade union based end user participation in systems development. Then I discuss some of the issues involved in improving the conditions for independent end user design activities. I go on by presenting a set of ‘cheap tools’ and techniques, including the use of mock‐ups. This set covers the issues of establishing the possibility of alternatives, of creating visions of new and different uses of technology and of designing computer support. A central question in relation to the tools and techniques is their accessibility to end users, and I discuss this based on the notions of family resemblance and ‘hands‐on’ experience.
Scandinavian research in systems development can be grouped into three major traditions, based on quite different ideologies and theories: the systems theoretical school, the…
Abstract
Scandinavian research in systems development can be grouped into three major traditions, based on quite different ideologies and theories: the systems theoretical school, the socio‐technical school and the critical school. The differences between these schools are closely related to the historical and social contexts in which they developed. External political, economic and cultural factors have strongly influenced research in this field. In particular, the basic theoretical differences between the schools reflect their different interpretations of the relationship between capital and labour.
Discusses experiences on the development and use of horizontal andvertical prototypes. Explains the difference. Resolves that horizontalprototypes can be developed with ′little…
Abstract
Discusses experiences on the development and use of horizontal and vertical prototypes. Explains the difference. Resolves that horizontal prototypes can be developed with ′little effort′, but end users are reluctant to become involved in the development process. Contrastingly resolves that vertical prototypes appear to stimulate constructive response. Reasons that developers should be aware of the tacit knowledge which plays an important part in users′ work practices and should be involved early in the development process. Proposes three techniques to meet the requirements – participation, simulation and evaluation.
Details
Keywords
Design rationale is design information that explains why an entity is designed as it is. This paper investigates how the documentation process and the use of documents in service…
Abstract
Purpose
Design rationale is design information that explains why an entity is designed as it is. This paper investigates how the documentation process and the use of documents in service design projects influence the reuse of design information across projects.
Design/methodology/approach
This study analyzes two sets of data collected through interviews and field observation. It first applied Lund's (2004) four elements of documentation process to categorize the collected data. Then it used bottom-up data analysis approach to identify patterns of the documentation process.
Findings
The author speculates designers' focus on certain documents' social aspect instead of material aspect influences how they reuse design information across projects. Some documents are important because they represent a consensus, and some are important because of the document producers rather than its content. The author also found a similarity between economists and service designers by comparing the study results with Harper and Sellen's (1995) findings. Based on the comparison, the author concludes that detailed research reports are easily reusable across design projects. Finally, although the author observed that designers are using templates to explicate design rationale, the created content is not used across projects.
Originality/value
This study identifies six types of documents that are commonly created in service design projects, three types of producer involvement and three types of provisional design outcomes. It also provides two suggestions for designers to reuse design information across service design projects better and two implications for future study.