2003
DOI: 10.1055/s-0038-1634235
|View full text |Cite
|
Sign up to set email alerts
|

Working IT Out in Medical Practice: IT Systems Design and Development as Co-Realisation

Abstract: Summary Objectives: The paper explores possibilities for situating IT design and development work within the context of use so as to support the co-realisation of technology and ‘design in use’. The aim is to build a new understanding between IT professionals and users which is grounded upon what happens as the latter grapple with the problems of applying IT, appropriating its functionalities and affordances into their work practices and relations. Methods: Following a discussion of partici… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
25
1
1

Year Published

2006
2006
2018
2018

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 38 publications
(27 citation statements)
references
References 17 publications
0
25
1
1
Order By: Relevance
“…These findings stress the importance of telecare technology providers taking an interest in learning from the experiences of call centre staff (fieldwork extract 16). As one staff member remarked, BYou can't improve something until it goes wrong.^This resonates with findings from Participatory Design, of the importance of 'design-in-use', which emphasises that design does not end after a IT system or service has been implemented (Henderson and Kyng 1992;Procter and Williams 1996;Hartswood et al 2000;Voss et al 2000;Hartswood et al 2002Hartswood et al , 2003bHartswood et al , 2008.…”
Section: Discussionmentioning
confidence: 57%
“…These findings stress the importance of telecare technology providers taking an interest in learning from the experiences of call centre staff (fieldwork extract 16). As one staff member remarked, BYou can't improve something until it goes wrong.^This resonates with findings from Participatory Design, of the importance of 'design-in-use', which emphasises that design does not end after a IT system or service has been implemented (Henderson and Kyng 1992;Procter and Williams 1996;Hartswood et al 2000;Voss et al 2000;Hartswood et al 2002Hartswood et al , 2003bHartswood et al , 2008.…”
Section: Discussionmentioning
confidence: 57%
“…Our proposal argues that translating this practice into a software design is full of interesting potentialities for the group decision support domain. This allows us to maintain a structuring, organising and constitutive practice, and to build robustness and resilience by the intensive everyday usage of writing tools and the co-creation process that we observed (Hartswood et al, 2003).…”
mentioning
confidence: 90%
“…We anticipate that a codesign or corealisation approach will prove particularly helpful here. 47 Finally, there is the question of the 'generalisablity' of our theory of resistance raised by reviewers of this report. The three cases (three contrasting social practices linked to three very different technologies) all 'fitted' the theory -but this study is preliminary and was not designed or resourced to provide a definitive theoretical framework that has been fully tested across the full range of possibilities.…”
Section: Some Avenues For Further Researchmentioning
confidence: 99%
“…'Co-evolution' refers to the parallel and reciprocal evolution of technologies and work roles or routines. 44,47 It might be a largely unintended consequence of introducing a technology (i.e. it is inadvertently found that work roles and practices have to change), or there might be a deliberate plan for such evolution to occur (i.e.…”
mentioning
confidence: 99%