Practical Strategies for Designing Inclusive and Safe Technology

Antiracist economist Kim Crayton’s assertion that “intention without strategy is chaos” resonates powerfully within our unfolding conversation about ethical technology. We've examined the worrisome outcomes that arise when biases and negligence towards marginalized groups shape tech innovation. The pressing question that emerges is: what concrete steps can we take toward meaningful change? Clearly, a mere desire to enhance safety in technology won't suffice; we require a deliberate and actionable strategy. This section aims to furnish you with practical methodologies that integrate safety into your design processes. We will unpack the elements essential for crafting technology that prioritizes user safety, persuade stakeholders of this necessity, and decode the discourse around the call for increased diversity—though necessary, diversity alone doesn't remedy the fundamental issues of unethical tech development.

Understanding Inclusive Safety

When it comes to designing technology with safety in mind, three objectives should guide your efforts: - Recognize potential misuse of your product. - Devise measures to mitigate these risks. - Empower vulnerable users to regain agency and control. The Process for Inclusive Safety, a methodology I developed back in 2018, encapsulates these principles into a tangible framework (see **Fig 5.1**). Whether you're embarking on the creation of a new product or enhancing an existing one, this structure can seamlessly fit into your design workflow. The methodology consists of five fundamental actions: 1. **Conduct research** 2. **Create archetypes** 3. **Brainstorm problems** 4. **Design solutions** 5. **Test for safety** The framework isn’t rigid—it’s adaptable to fit various team workflows and project needs. You're encouraged to use the elements that resonate with your unique context, making it an organic part of your existing development practices. I invite you to engage with this methodology actively. If your application of it sparks ideas for improvement, I would love to hear from you. This isn't set in stone; it's a dynamic tool intended to support technologists as they navigate the complexities of their work. If you're designing for specific vulnerable groups or trauma survivors—like developing an app for survivors of domestic violence—make sure to check Chapter 7. This chapter will address nuances encountered when catering specifically to individuals who have experienced trauma, diverging from the broader guidelines meant for a general audience.

Step 1: Conduct Research

The foundation of effective design begins with thorough research. You need to understand how your technology might be exploited and gather insights from both survivors and perpetrators of abuse. This investigation should focus on interpersonal harm and any related issues—such as data security vulnerabilities, bias in algorithms, and harassment.

Broad Research

Start with expansive research into existing products and critical ethical concerns associated with them. For instance, if you’re designing a smart home gadget, gain insights into how other similar devices have been misused. If AI mechanisms are involved, dive into potential biases and risks outlined by experts and existing literature. Resources like [Google Scholar](https://scholar.google.com) can help unearth academic studies on these topics.

Specific Research: Survivors

Conduct direct studies when feasible—surveys and interviews can be incredibly beneficial in capturing the voices of those who have experienced abuse. Engaging with advocates in the field before speaking to survivors can create a compassionate context that minimizes trauma. If you're tackling issues related to domestic violence, connect with survivors and professionals such as hotline workers or attorneys who deal with these cases regularly. Remember, compensating survivors for their knowledge and experiences is fundamental. Don’t ask them to share their trauma without acknowledgment of its value. If direct payment isn’t feasible, consider a donation to relevant organizations as a way of recognizing their contribution.

Specific Research: Abusers

While it may be impractical to interview abusers outright, a general understanding of their behaviors can illuminate how they exploit technology. Focus your investigative efforts on patterns of misuse and the tactics employed to cover their tracks.

Step 2: Create Archetypes

After gathering your insights, construct archetypes representing both abusers and survivors. These archetypes stem from your research and differ from traditional personas, which are based on real-world users. Archetypes serve as generalized models based on common patterns of behavior and anticipated issues; much like accessibility design, you don't need real-life interactions to create considerations for underrepresented users. The abuser archetype embodies the mindset of someone seeking to leverage your product for harm. Conversely, the survivor archetype signifies someone navigating abuse. Each might face distinct circumstances: for instance, does one require evidence of ongoing abuse, or are they only beginning to recognize they’re a target? You can create multiple survivor archetypes to encapsulate varied scenarios. Awareness of the abuse could be present, but the ability to act on that awareness may be limited. Utilize these archetypes to inform your design, aiding survivors in reclaiming control. While modeling your archetypes, prioritize their objectives. The abuser's aim is to inflict harm, while the survivor seeks to prevent or discontinue that harm. Brainstorm how you can thwart abuser goals while enhancing survivor experiences. Keep in mind that these archetypes aren’t one-size-fits-all. Situations may arise where the roles aren’t clear-cut; adapt your framework accordingly—for instance, when considering cybersecurity issues where an unauthorized intruder may pose as the abuser and the user being monitored is the survivor.

Step 3: Brainstorm Problems

Following archetype creation, engage in a brainstorming session to identify unique abuse scenarios and safety concerns specific to your product. These “novel” cases should not overlap with known problems but rather unearth new threats. Invest a dedicated timeframe—perhaps several hours—allowing your team to exhaustively explore potential misuse of your innovation. If you need inspiration, consider a “Black Mirror” brainstorming approach, evoking the show's focus on the darker side of technology. This exercise might bring humor into serious discussions, which is valuable for team dynamics. After this fun initial phase, shift to document more practical concerns. After addressing an array of potential issues, it’s natural to feel uncertain about whether you've considered everything. Embrace that anxiety as part of the process. While reaching perfection isn’t feasible, commit to ongoing attention to safety as your product evolves in the market.

Step 4: Design Solutions

Armed with your list of potential abuse scenarios and archetypal insights, the next step is focused on designing solutions that address these challenges. This should align with existing aspects of your design workflow, as you propose practical remedies for the issues unearthed during your research phase. Consider the following guiding questions to help your design strategy: - Can you engineer your product to prevent identified harms outright? - How might you alert users to the possibility of abuse within your product? - What actions could inform users on how to safeguard themselves? - Can your technology recognize red flags indicating the potential for harm, and provide options for user support? For certain products, it’s feasible to incorporate proactive measures—like enabling users of a health app to report abuse, which in turn could direct them to resources for support. But vigilance is key: ensure no feature inadvertently jeopardizes user safety, particularly in situations where users might be monitored by abusers.

Step 5: Test for Safety

The concluding phase involves rigorous testing from both abuser and survivor perspectives. By simulating scenarios in which an abuser exploits your product, you can identify weaknesses and address them before launch. Testing should ideally align with usability assessments. However, if your company lacks such processes, leverage safety testing to discern usability issues too. Conduct safety assessments on final prototypes or existing products not originally designed with safety in mind—adapting them for enhanced security is a worthwhile endeavor. Remember, testing should encompass each archetype. Depending on your design, it may not make sense to test both at once; instead, focus on scenarios that reflect the various situations you’ve defined in your research. In summary, while the abuser and survivor model provides a useful framework, always be prepared to adjust as new dynamics emerge in your research. By methodically addressing potential risks and empowering users, you stand to create technology that's not just innovative—it's safe and ethical.

Redefining User Safety in Technology Design

As technology increasingly shapes our lives, the importance of user safety takes center stage, especially when addressing how applications operate under different user archetypes. Take, for instance, a fitness app with GPS capabilities. It’s alarming to consider how an individual with malicious intent could exploit these features to track someone’s whereabouts. If a user has set privacy settings, a determined stalker might probe into running routes or profile connections, potentially bypassing barriers meant to protect personal data. This scenario starkly illustrates a broader concern: if your product inadvertently aids such pursuits, it calls for urgent reassessment. So what’s the takeaway here? Recognizing the potential misuse of features isn't just a matter of ethics—it's a business imperative. If through this testing phase you discover that stalker behavior can be facilitated, returning to the design stage to close these loopholes should be a priority. The iterative nature of this process necessitates a commitment to user safety.

Empowering Survivors Through Thoughtful Design

Addressing the needs of survivors must be integral to the design process. Concepts like "survivor testing" provide a framework for designers to assess how their products can empower users who need protection from abuse. In many cases, thwarting an abuser’s actions aligns directly with enhancing a survivor's sense of security. But it’s not a one-size-fits-all approach. Consider a smart thermostat: a survivor might feel vulnerable if someone else is controlling its settings without consent. By scrutinizing user logs and access controls, designers can better understand how to fortify these devices against unauthorized changes. If instructions for regaining control are buried or non-existent, that’s a clear signal that more attention is needed in the design phase.

Incorporating Stress Testing For Real User Experiences

Taking user experience a step further involves integrating stress testing into development. This concept, highlighted in Eric Meyer and Sara Wachter-Boettcher’s *Design for Real Life*, challenges the traditional notion of user personas, which often depict ideal users enjoying smooth interactions. Real life frequently presents users with anxiety, stress, or even trauma, and this is where stress cases come into play. Designing with these scenarios in mind allows for a more compassionate approach. When applications accommodate users experiencing duress, they not only acknowledge diverse experiences but also become more intuitive and supportive. Meyer and Wachter-Boettcher provide valuable insights into implementing these principles—an essential read for anyone serious about user-centered design. In conclusion, as we push the boundaries of technology, emphasizing user safety, survivor empowerment, and genuine compassion will not simply enhance product value; it will also foster a safer digital ecosystem. The conversations we have today will define how we build technology for tomorrow.