Calls to Action and Justice
How can we effectively translate thought to action, given that ethical technologies lie in opposition to intricate power structures?
COMBATTING THE DOMAINS OF DOMINATION
- Structural: organizes oppression- laws and policies.
- Disciplinary: administers and manages oppression. Implements and enforces laws and policies.
- Hegemonic: circulates oppressive ideas- culture and media.
- Interpersonal: individual experiences of oppression.
- (Source)
ACKNOWLEDGE WHAT IS ALREADY IN THE WORKS
- A call to action should not equate to a savior complex. Research and join community-led movements that are already addressing ethical harms.
ACTION FOR EVERYONE
- Commit your time and resources to missions that align with your values
- Spread discourse about ethical technologies (interpersonal + hegemonic)
- Speak out when technologies do not comply with laws and policies (structural)
- What else? There is much to be added to this list!
ACTION FOR SOFTWARE ENGINEERS
- Research alternatives, such as software, hardware, or UI design choices, processes, features, implementations, and interventions that could increase or reduce the ethical risks (disciplinary)
- Build confidence to speak up to your team and leadership
- Ask questions as opposed to leading with assumptions (interpersonal + hegemonic)
- Highlight existing standards and best practices of responsible computing (structural)
- Present tangible alternatives based on your research (disciplinary)
- Advocate to work on projects that align with your values
- What else? There is much to be added to this list!
COMPLICATIONS TO CONSIDER
- What risks do engineers face in voicing their concerns? How do/should these risks affect our actions?
- If you work on a siloed part of the whole… How might you know that the ‘whole’ aligns with your values? Is it enough to just know that your part aligns with your values?