MétaCan
Menu
Back to cohort
Record W4323055029 · doi:10.7764/disena.22.article.7

Design Processes and Tools as Oppression? Rethinking our Design Practice for more Just Design Outcomes

2023· article· en· W4323055029 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueRevista Diseña · 2023
Typearticle
Languageen
FieldArts and Humanities
TopicCrafts, Textile, and Design
Canadian institutionsEmily Carr University of Art and Design
Fundersnot available
KeywordsOppressionReflexivitySociologyEngineering ethicsDesign thinkingContext (archaeology)EpistemologyComputer sciencePolitical scienceEngineeringSocial sciencePoliticsHuman–computer interaction

Abstract

fetched live from OpenAlex

Our design processes and tools matter, as our design is always shaped by the processes and tools that we use. Context necessarily shapes the content of our design processes and tools. But, without paying attention to the content emerging from that context, the use of these tools and processes may become oppressive. In the wake of colonialism, the un-reflexive use of design tools and processes underpinned by Western conceptual ideas and schema can lead to oppression for design with non- Western or Indigenous peoples. Even tools and processes designed with a supposedly liberatory intent, such as promoting democratic practice or equality, can lead to oppression in their un-reflexive use. Looking at two experiences from my design practice with my own hapū (clan), this article explores the ways in which ideas of democratic participation and equality raised in these two design spaces could function in an oppressive way to cause a form of violence against our traditional lifeworld. This article proposes some ways in which this aspect of design might be modified to help lead to more just design outcomes, through a more reflective and intentional approach when choosing and applying the design tools and processes we use in our design practice.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.004
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Scholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.880
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.004
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0020.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.233
GPT teacher head0.368
Teacher spread0.135 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it