Inclusivity before Simplicity

The principle of Inclusivity before Simplicity is part of the Manifesto for Sustainable Software Development created by software developers, designers and entrepreneurs to call for responsibility among our peers to prioritize sustainability — not only in terms of ecological impact but also in inclusivity, ethics, and the long-term resilience of the digital systems we create. By prioritizing Inclusivity over Simplicity when designing our software, we may contribute to a shift toward a better digital future where technology serves the needs of society, humanity, and the planet — rather than exploiting human psychology for the benefit of a few.

This manifesto is a work in progress, and we are actively seeking feedback, ideas, and support. We invite you to join the conversation and contribute in any way that resonates with you — whether big or small, every voice matters.

Simplicity in design has undeniable value—it makes systems easier to use, improves initial accessibility, and reduces friction for new users. However, prioritizing simplicity over inclusivity often results in systems that exclude users with unique needs or more advanced requirements. Inclusivity ensures that technology adapts to diverse user groups and remains flexible enough to evolve with future demands, creating more equitable, resilient platforms.

Inclusivity in software design ensures that systems serve a wide range of users with diverse needs, abilities, and preferences. While simplicity is valuable for creating accessible and user-friendly systems, prioritizing simplicity at the expense of inclusivity often results in marginalizing individuals who do not fit the assumed user profile. Inclusivity goes beyond basic accessibility by addressing the needs of groups who might otherwise be excluded from meaningful participation due to technological, cultural, or socioeconomic barriers.

Systems designed solely for simplicity can fail to accommodate individuals who require alternative means of interaction, such as those with disabilities, elderly users who may not be comfortable with modern technology, or individuals in resource-constrained environments without access to advanced devices. While accessibility features, such as screen readers or keyboard navigation, should be standard in all modern software, inclusivity demands a deeper examination of how systems can bridge gaps for marginalized communities. For instance, community software that assumes all users have access to smartphones could limit interaction for individuals who rely on simpler channels, like email or SMS. Designing systems that integrate these channels could open up participation to a wider audience, ensuring no one is left behind.

Inclusivity is rooted in principles of equity and fairness. According to Hansen (2019), systems that cater to diverse needs strengthen resilience within communities, enabling all members to contribute meaningfully. This aligns with the World Wide Web Consortium (W3C) guidelines, which emphasize the importance of adaptable systems that allow users with varying levels of technical proficiency and physical ability to engage effectively. Universal Design principles further underscore the need for systems to support multiple methods of interaction, enabling users to engage with technology in ways that best suit their circumstances and preferences.

To achieve inclusivity, designers must go beyond providing accessibility features and consider how to actively include marginalized groups. This involves creating systems that are not only easy to use but also flexible enough to meet the needs of diverse users. Examples include:

  • Offering alternative interfaces for users who may not have access to smartphones, such as email-based interactions or SMS notifications, ensuring individuals with limited technological skills or devices can still participate.
  • Building multilingual support into software to address language barriers and make platforms accessible to global audiences.
  • Designing modular systems that allow users to toggle between basic and advanced features, enabling both novice and experienced users to interact with the system effectively.
  • Providing simplified interfaces or workflows for elderly users who may struggle with modern technology but still want to engage in digital communities.

Failure to prioritize inclusivity can exacerbate inequalities. Marginalized groups, such as those with disabilities or limited access to advanced technology, may be excluded from opportunities to connect, collaborate, or access essential services. This exclusion can lead to further social and economic disparities, as technology becomes increasingly central to daily life and participation in society. Moreover, systems that fail to address diverse needs risk alienating entire user segments, reducing their effectiveness and long-term viability.

Inclusivity also has broader societal implications. When technology fails to cater to diverse user groups, it often reinforces existing power imbalances, favoring those who already have access and technical expertise. By contrast, systems that actively include marginalized individuals foster greater equity, enabling all members of society to benefit from technological advancements. This approach not only aligns with ethical principles but also contributes to the long-term success and sustainability of platforms by expanding their reach and relevance.

To implement inclusivity effectively, designers should engage with a wide range of users during the development process. This includes conducting user testing with individuals from different cultural, socioeconomic, and technological backgrounds to identify and address potential barriers. Designers should also prioritize flexibility in their systems, ensuring they can adapt to changing user needs and emerging technologies over time. By prioritizing inclusivity, designers can create systems that are not only accessible but also empowering, enabling all users to engage meaningfully and equitably in the digital world.