10 Essential Strategies for Designing Safe and Inclusive Tech

In the world of tech design, good intentions alone aren't enough to keep users safe. As antiracist economist Kim Crayton aptly puts it, “intention without strategy is chaos.” Biases, assumptions, and neglect of marginalized groups have led to dangerous products. But how do we move from awareness to action? This listicle breaks down the key strategies from the Process for Inclusive Safety—a practical framework for embedding safety into every stage of design. Whether you're building a new feature or overhauling an existing one, these ten steps will guide you toward truly ethical and inclusive tech.

1. Acknowledge That Intention Alone Is Not Enough

Before diving into tactics, understand that safety isn't a checkbox—it's a mindset shift. Many teams express a desire to “do good,” but without a concrete strategy, those wishes evaporate. The first step is admitting that biases and oversight have historically harmed vulnerable users. Recognize that safety must be an intentional, structured effort woven into your workflow from the start. Only when you accept that intention without a plan leads to chaos can you begin to design responsibly.

2. Define Your Ultimate Safety Goals

Every safe product rests on three core objectives: identify how your product could be misused, design mechanisms to prevent that abuse, and empower users who are most at risk. This means shifting from a reactive to a proactive stance. For instance, a social media platform should anticipate harassment patterns and build in protective features before launch. By setting these clear goals, you create a north star that guides every design decision.

3. Embrace the Process for Inclusive Safety

Developed in 2018, the Process for Inclusive Safety is a toolkit that captures the best practices for designing with vulnerability in mind. It comprises five action areas: conducting research, creating archetypes, brainstorming problems, designing solutions, and testing for safety. The beauty of this process is its flexibility—you can adapt it to any product, whether you're starting from scratch or adding a new feature. It's a living document meant to evolve with your team's needs.

4. Start with Deep, Inclusive Research

Research is the foundation. You must go beyond typical user demographics to understand the experiences of marginalized groups. Interview survivors of abuse, people with disabilities, or those from underrepresented communities. Ask about their fears and coping mechanisms. This research reveals the real-world consequences of poor design and highlights features that might inadvertently harm users. Without this empathy-driven insight, your safety strategy will be built on assumptions.

5. Develop Archetypes, Not Just Personas

Traditional personas often gloss over users' vulnerabilities. Instead, create archetypes that emphasize power dynamics and potential abuse. For example, an archetype might be “a user who is being monitored by an abuser” or “a teenager exploring identity in a hostile environment.” These archetypes help you imagine worst-case scenarios and design barriers to prevent harm. They keep the most vulnerable users front and center throughout development.

6. Brainstorm Every Possible Abuse Scenario

Set aside time specifically to brainstorm how your product could be weaponized. Gather a diverse team—including edge-case thinkers—and ask: How could someone use this to stalk, harass, or exclude? Consider features like direct messaging, location sharing, or content recommendation. Document every risk, no matter how small. This exercise flips the script from “what do users want?” to “what could users face?” and prepares you to address vulnerabilities before launch.

7. Design Solutions That Prioritize Prevention

Once you've identified risks, design features that actively prevent abuse. This might include default privacy settings that limit public visibility, consent flows before sharing data, or automated moderation filters. Use design patterns that give users control—like allowing them to block, report, or limit interactions easily. The goal is to make the safe choice the easiest choice. Prevention is far more effective than trying to fix harm after it happens.

8. Test for Safety with Realistic Scenarios

Testing must go beyond usability. Run simulations where testers act as both abusers and targets. Check if safety features work under stress—for example, can a user quickly delete their account if being tracked? Does the reporting system actually work? Use a range of devices and network conditions to ensure accessibility. Iterate based on findings. Testing is not a one-time event; it should be continuous as the product evolves.

9. Know When to Go Deeper: Specialized Products for Vulnerable Groups

The Process for Inclusive Safety is designed for general products used by a wide audience. However, if you're building an app specifically for domestic violence survivors, people with addiction, or trauma victims, you'll need a more specialized approach. For those cases, refer to dedicated resources (like Chapter 7 of the original book). Such products require extra caution around data privacy, emotional support, and consent. Always consult experts and community representatives.

10. Build a Culture That Values Safety Over Speed

Finally, lasting safety depends on organizational buy-in. Convince stakeholders that investing in safety reduces long-term risks, legal liability, and reputational damage. Respond to the critique that “more diversity on the team” alone solves everything—diversity is crucial but incomplete without a structured safety process. Advocate for dedicated resources, training, and time. When your whole team treats safety as a core metric, you create technology that truly serves everyone.

Designing for safety is not a one-off project—it's a continuous commitment. By following these ten strategies, you shift from chaotic intention to strategic action. Your product will not only be less harmful but also more trusted and inclusive. Start where you are, use the parts that fit your context, and never stop iterating. Safe tech is possible when we design with empathy, foresight, and courage.