Skip to main navigation Skip to search Skip to main content

Three Perspectives on Human Vulnerability: Enriching Responsible Computing Design Processes

Research output: Contribution to journalArticleAcademicpeer-review

7 Downloads (Pure)

Abstract

In response to the increasing interest in (designing for) human vulnerability within the field of responsible computing, we articulate the multi-dimensionality of the concept of vulnerability to deepen and enrich the conversations about the relationship between vulnerabilities and the design of assistive technologies. Drawing on different philosophical traditions and insights from critical disability studies, we introduce three perspectives on vulnerability–the individualist, relationalist, and enactivist perspectives–that each emphasize a different aspect of what it means to be vulnerable. We argue that, for engineers in the field of responsible computing, it is key to be able to adopt all three perspectives and explicitly and critically reflect upon what each perspective or combination of perspectives brings to the design context at hand. When used in conjunction, the three perspectives together can mitigate the risk of creating technological interventions that may aim at ameliorating vulnerabilities but instead exacerbate or create new ones. To move forward, we call for further reflections and practical considerations on how to best integrate the three perspectives on vulnerability into participatory design practices; how to distribute responsibilities within design teams to ensure that all perspectives are genuinely adopted and engaged with; and how to foster creative, out-of- the- box thinking for assistive technology design.
Original languageEnglish
Article number15
Number of pages21
JournalACM Journal on Responsible Computing
Volume2
Issue number4
DOIs
Publication statusPublished - Dec 2025

Fingerprint

Dive into the research topics of 'Three Perspectives on Human Vulnerability: Enriching Responsible Computing Design Processes'. Together they form a unique fingerprint.

Cite this