What do you think?
Rate this book


360 pages, Paperback
First published February 7, 2020
Design justice rethinks design processes, centers people who are normally marginalized by design, and uses collaborative, creative practices to address the deepest challenges our communities face.The full set of principles can be found at https://designjustice.org/1. We use design to sustain, heal, and empower our communities[...]
2. We center the voices of those who are directly impacted by the outcomes of the design process.
3. We prioritize design’s impact on the community over the intentions of the designer.
5. We see the role of the designer as a facilitator rather than an expert.
8. We work towards sustainable, community-led and -controlled outcomes.
9. We work towards non-exploitative solutions that reconnect us to the earth and to each other.
VSD is descriptive rather than normative: it urges designers to be intentional about encoding values in designed systems but does not propose any particular set of values at alll […] VSD never questions the standpoint of the professional designer, doesn’t call for community inclusion in the design process (let alone community accountability or control), and doesn’t require an impact analysis of the distribution of material and symbolic benefits that are generated through design. Values are treated as disembodied abstractions, to be codified in libraries from which designers might draw to inform project requirements[...]In a sense, Design Justice it grows out of Participatory Design and is more akin to the EU’s Responsible Innovation (RI) approach, but goes well beyond RI in the political role and importance played by non-mainstream and indigenous communities.
...designers tend to unconsciously default to imagined users whose experiences are similar to their own. This means that users are most often assumed to be members of the dominant […] group: in the United States, this means (cis)male, white, heterosexual, “able-bodied”, literate, college-educated, not a young child and not elderly, with broadband internet access, with a smartphone, and so on […] Unfortunately, this produces a spiral of exclusion as design industries center the most socially and economically powerful users, while other users are systematically excluded on multiple levels: their user stories, preferred platforms, aesthetics, language, and so on, are not taken into consideration.She criticizes what she calls “stand-in strategies to represent communities taht are not really included in the design process”, particularly user personas, especially if they are, as they often are, “...created out of thin air by members of the design team (if not autogenerated by a service like Userforge), based on their own assumptions or stereotypes about groups of people...”. Other unsuccessful stand-in techniques like the designation of a “user diversity advocate”, real-world user testing or even disability simulations:
None of these techniques are as good as the incluion of diverse users on the design team throughout the process.This chapter looks into the design process, as one of the key sections’ subtitles has it: “From participation to accountability to ownership”. Userr participation has been espoused by approaches such as participatory design, sociotechnical user design, user-led innovation, user-centered design, human-centered design, inclusive design and codesign among others. Costanza-Chock details why and how design justice requires much higher levels of community involvement and power based on the creation and use of formal, intitutionalized mechanisms of community accountabily and control, as recommended by the T4SJ Project’s recommendations for achieving community accountability. In short, as Costanza-Chock remarks in the closing section of this chapter:
Beyond employment equity, design justice requires full inclusion of, accountability to, and ultimately control by people with direct lived experience of the conditions the design team is trying to change [...I]t also focuses on concrete mechanisms for community control […]Chapter 3 looks at design narratives, paying close attention to
...who receives attention and credit for design work, how we frame design problems and challenges, how we scope design solutions and what stories we tell about how design processes operate.”It analyzes appropriative design strategies:
In design justice, those whose lived experience guides the process are recognized as codesigners; they become co-owners of designed products, platforms, systems, and other outputs and also become coauthors of the story about the project.The author also pays close attention to corporate misappropriation of innovations and the misrepresentation and downplaying of the role of social movements in innovation. The author’s critical analysis of narratives in the Gates Foundation’s Reinvent the Toilet Challenge is particularly noteworthy and memorable. Wrapping up the case study, she says:
Design justice considers “Who contributed? to be a critical question for the evaluation of any given design project.
The Gates Challenge […] ignores existing solutions; assumes that solutions will come from university labs far from the social realities of those without access to sanitation; makes no stipulation for, or even suggestion of, a codesign approach that would include local expertise and/or tacit and experiential knowledge; and makes no mention of [such ley problems as] adoption, usage or maintenance[…] In one of the most insightful articles about the challenge, Lloyd Alter writes that the winning projects are all expensive, complicated and difficult to maintain […] Some are potentially deadly: several superheat feces[…] Alter also writes about the wasted water and energy involved in all flush toilet systems.Chapter 4 covers design sites and how hackerspaces, fablabs, hackathons and discotechs work, are used and abused.
We will be working to design and develop real world projects, grounded in the needs of CBOs. As a student you will be part of a co-design team led by a partner organization […] Our goal is twofold: to develop an understanding of the ways that technology design processes often replicate existing power inequalities, while at the same time moving beyond critique towards community coauthorship, as much as possible within the constraints of any given project.The chapter richly reports on student experiences and projects. She bases her course on Seymour Papert’s and Michael Resnick’s constructionism and Paolo Freire’s ideas and principles on real world action-reflection cycles for transformative popular education as set forth in his most well-known work Pedagogy of the Oppressed and provides background on popular technology education initiatives in different countries. Sacha Costanza-Chock provides an extremely honest and pragmatic appraisal of the challenges of teaching Design Justice:
I have organized a discussion of each challenge, with examples drawn from student case studies. I have placed them in dialogue with the Design Justice Network Principles….This makes for especially interesting reading for anyone who has had to struggle to teach a minimally “realistic” project-based software engineering, information systems engineering and in general any such engineering design course. For example, the following observations will certainly strike very familiar chords:
1. It’s hard to overstate the importance of honestly asking: “What will community members [external stakeholders in more traditional parlance] get out of the process?”There are, of course a number of other issues specific to design justice which Costanza-Chock vividly brings up. Finally the author also briefly analyzes what what aspects of computers should be included in popular education and what is the best way to go about doing it -she rather disappointingly appears to focus more on teaching coding even though it must be admitted that she argues strongly for trascending teaching programming:
2. [T]he start-up discourse that valorizes failure can be particularly harmful in design justice processes. Start-up ideology such as “move fast, break things” and “fail hard, fail fast” can become a justification for working styles […] that involves making mistakes in the real world at the expense of community partners
3. [D]ecision making in any design project involves a delicate balance between the desire to be inclusive, collaborative, and accountable, and the need to get things done.
4. When student teams spend too much time researching, theorizing, analyzing and ideating, but fail to move quickly enough to mock-ups or prototypes, they lose invaluable opportunities to iterate on the project based on user testing and feedback.
5. It’s very easy for design teams operating on a semester schedule to run out of time.
6. Because design justice pedagogies emphasize a balance of process and product, rather than simply valuing “final” products, regular assessment of student work and of the design process can help improve the overall experience for everyone. Leaving assessment to the end of the process, or just to one or two key moments (such as mid-term and the end of the semester), is a mistake. To further complicate matters, students do not always appreciate pedagogy that emphasizes process, real-world contexts, challenges and partnership; instead many desire a design studio that allows them to freely explore the limits of their creativity, with evaluation based on a final product.
7. [The need for steering] students away from the pitfalls of tech solutionism and technochauvinism [and the NIH syndrome to explore] whether the design team might be able to amplify, remix, or otherwise repurpose existing projects, practices, applications or tools, rather than build something new.
[Might we advocate that people learn to code in ways that also push them to think more critically about software, technology, and design and that prepare them to help reshape technology in the service of human liberation and ecological sustainability […]?It is worth wrapping up this review with a final, optimistic quote from Sasha Costanza-Chock’s book:
Design justice is a framework that can help guide us as we seek to teach computing, software development and design in ways that support rather than suppress, the development of critical consciousness and that provide scaffolding for learnerr’s connections to the social movements that are necessary to transform our world.