Counter-Data Mapping
Identify 2-3 organizations or projects that address the same problem differently.
Comparative Matrix
| Dimension | Original Initiative | Alternative 1 | Alternative 2 | Alternative 3 (optional) |
|---|---|---|---|---|
| Who controls the data? | -- | -- | -- | -- |
| Who benefits? | -- | -- | -- | -- |
| How is consent achieved? | -- | -- | -- | -- |
| Who funds the project? | -- | -- | -- | -- |
| Data collection methods | -- | -- | -- | -- |
| Accountability mechanisms | -- | -- | -- | -- |
| [Add your own dimension] | -- | -- | -- | -- |
Deep Dive: Most Compelling Alternative
Select the counter-data project you found most compelling or complete. Analyze it using data feminist principles.
Project Overview
Project Name: [Name of alternative project]
Organization: [Organization name]
Brief Description: Summarize what this project does and how it differs from the original initiative.
Data Feminist Principles Analysis
1. Examine Power
How does this project challenge or redistribute power? Who gains power? Who might lose it?
2. Challenge Power
What power structures does this project challenge? How?
3. Elevate Emotion and Embodiment
How does this project incorporate lived experience, emotion, or embodied knowledge?
4. Rethink Binaries and Hierarchies
How does this project move beyond binary categories or challenge hierarchical structures?
5. Embrace Pluralism
How does this project incorporate multiple perspectives, methods, or ways of knowing?
6. Consider Context
How does this project account for context, history, and local knowledge?
7. Make Labor Visible
How does this project acknowledge and value the labor involved in data work?
Strengths & Limitations
Strengths
- Strength 1
- Strength 2
- Strength 3
Limitations
- Limitation 1
- Limitation 2
- Limitation 3
Feminist Redesign Proposal
Based on your analysis, propose a redesign of the original data initiative or algorithm.
Redesign Vision
Provide a brief overview of your redesigned system. What are the core changes you're proposing?
1. Redesigned Methodology / Logic Flow
For Data Initiative: Describe your redesigned data collection, analysis, and use methodology.
For Algorithm: Create a new logic flowchart showing how your redesigned algorithm would work.
Figure: Visual representation of the redesigned system
Key Changes
- Change 1: Description and rationale
- Change 2: Description and rationale
- Change 3: Description and rationale
2. Refusal Statement
Identify what data or features you would refuse to collect or build.
What We Refuse to Collect/Build:
- Refusal 1: [What you refuse] - Why this refusal matters
- Refusal 2: [What you refuse] - Why this refusal matters
- Refusal 3: [What you refuse] - Why this refusal matters
Refusal as Feminist Practice
Examine how refusal can be a feminist practice. How does saying "no" to certain data or features protect communities and challenge power structures?
3. Accountability Mechanisms
How would you prevent or address harm in your redesigned system?
Mechanism 1: [Name]
What: Description of the accountability mechanism
How: How it would be implemented
Who: Who would be responsible
Mechanism 2: [Name]
What: Description of the accountability mechanism
How: How it would be implemented
Who: Who would be responsible
Mechanism 3: [Name]
What: Description of the accountability mechanism
How: How it would be implemented
Who: Who would be responsible
4. Stakeholder Map
Visualize who gains or loses power in your redesign.
Figure: Stakeholder map showing power shifts in the redesigned system
Power Shifts Analysis
Who Gains Power?
- Stakeholder 1: How they gain power
- Stakeholder 2: How they gain power
- Stakeholder 3: How they gain power
Who Loses Power?
- Stakeholder 1: How they lose power
- Stakeholder 2: How they lose power
- Stakeholder 3: How they lose power
5. Vulnerability Assessment
Identify the limitations and vulnerabilities of your redesign. Be honest about what your proposal cannot solve.
Limitations
- Limitation 1: Description and implications
- Limitation 2: Description and implications
- Limitation 3: Description and implications
Potential Vulnerabilities
- Vulnerability 1: How your redesign could still cause harm
- Vulnerability 2: Unintended consequences to consider
- Vulnerability 3: Challenges to implementation
References
- Author, A. (Year). Title of work. Journal Name, volume(issue), pages.
- Author, B. (Year). Title of work. Journal Name, volume(issue), pages.
- Author, C. (Year). Title of work. Journal Name, volume(issue), pages.
- Author, D. (Year). Title of work. Journal Name, volume(issue), pages.
- Author, E. (Year). Title of work. Journal Name, volume(issue), pages.
- Author, F. (Year). Title of work. Journal Name, volume(issue), pages.
- Author, G. (Year). Title of work. Journal Name, volume(issue), pages.
- Author, H. (Year). Title of work. Journal Name, volume(issue), pages.
- Author, I. (Year). Title of work. Journal Name, volume(issue), pages.
- Author, J. (Year). Title of work. Journal Name, volume(issue), pages.
- Author, K. (Year). Title of work. Journal Name, volume(issue), pages.
- Author, L. (Year). Title of work. Journal Name, volume(issue), pages.
At least 12 sources total (including those from previous parts)