Why It Matters
Technology often amplifies existing inequalities. Platforms designed for “average users” exclude those with disabilities, limited resources, or marginalized identities. Designing from the margins—prioritizing the needs of the most excluded—creates solutions that are more inclusive, more robust, and more humane for everyone.
Core Principle
Actively involve perspectives of diverse and marginalized communities in design. Recognize and address systemic obstacles. Build accessibility and inclusion from the start, not as an afterthought. When we solve for the most excluded, we create better products for all.
Examples in Practice
- Designing with disabled users, not for them
- Accessibility built in, not bolted on
- Addressing needs of marginalized and vulnerable populations first
- Diverse teams involved in design and decision-making
- Testing with users from underrepresented communities
- Recognizing and removing systemic barriers in the technology
- Supporting users in countries with restrictive governance
Guiding Questions for Decisions
- Who is excluded by this design, and why?
- Have we involved marginalized communities in shaping this?
- Does this solve for the most vulnerable, or just the comfortable?
- What systemic barriers does this design create or remove?
- Are we building accessibility or just checking compliance boxes?