Table of Contents
Fetching ...

Against Scale: Provocations and Resistances to Scale Thinking

Alex Hanna, Tina M. Park

TL;DR

The paper critiques scale thinking as the dominant paradigm in tech innovation, arguing that it frames problems, solutions, and evaluation through the lens of scalable efficiency. It argues that such an orientation may hinder deep, systemic, equity-driven change and that mutual aid offers a concrete alternative for organizing collaborative work. The paper uses Bed-Stuy Strong as a case study to illustrate resistive design practices and proposes evaluative questions to guide technologists. It highlights how datafication and standardization can reproduce inequalities, especially in disaster contexts, and calls for reflexive, participatory design approaches.

Abstract

At the heart of what drives the bulk of innovation and activity in Silicon Valley and elsewhere is scalability. This unwavering commitment to scalability -- to identify strategies for efficient growth -- is at the heart of what we refer to as "scale thinking." Whether people are aware of it or not, scale thinking is all-encompassing. It is not just an attribute of one's product, service, or company, but frames how one thinks about the world (what constitutes it and how it can be observed and measured), its problems (what is a problem worth solving versus not), and the possible technological fixes for those problems. This paper examines different facets of scale thinking and its implication on how we view technology and collaborative work. We argue that technological solutions grounded in scale thinking are unlikely to be as liberatory or effective at deep, systemic change as their purveyors imagine. Rather, solutions which resist scale thinking are necessary to undo the social structures which lie at the heart of social inequality. We draw on recent work on mutual aid networks and propose questions to ask of collaborative work systems as a means to evaluate technological solutions and guide designers in identifying sites of resistance to scale thinking.

Against Scale: Provocations and Resistances to Scale Thinking

TL;DR

The paper critiques scale thinking as the dominant paradigm in tech innovation, arguing that it frames problems, solutions, and evaluation through the lens of scalable efficiency. It argues that such an orientation may hinder deep, systemic, equity-driven change and that mutual aid offers a concrete alternative for organizing collaborative work. The paper uses Bed-Stuy Strong as a case study to illustrate resistive design practices and proposes evaluative questions to guide technologists. It highlights how datafication and standardization can reproduce inequalities, especially in disaster contexts, and calls for reflexive, participatory design approaches.

Abstract

At the heart of what drives the bulk of innovation and activity in Silicon Valley and elsewhere is scalability. This unwavering commitment to scalability -- to identify strategies for efficient growth -- is at the heart of what we refer to as "scale thinking." Whether people are aware of it or not, scale thinking is all-encompassing. It is not just an attribute of one's product, service, or company, but frames how one thinks about the world (what constitutes it and how it can be observed and measured), its problems (what is a problem worth solving versus not), and the possible technological fixes for those problems. This paper examines different facets of scale thinking and its implication on how we view technology and collaborative work. We argue that technological solutions grounded in scale thinking are unlikely to be as liberatory or effective at deep, systemic change as their purveyors imagine. Rather, solutions which resist scale thinking are necessary to undo the social structures which lie at the heart of social inequality. We draw on recent work on mutual aid networks and propose questions to ask of collaborative work systems as a means to evaluate technological solutions and guide designers in identifying sites of resistance to scale thinking.

Paper Structure

This paper contains 5 sections, 1 figure.

Figures (1)

  • Figure 1: The Docker and Kubernetes logos, respectively.