As digital technologies continue to expand, one important question remains unanswered: who shapes these technologies, and whose knowledge and realities inform their design? Digital design refers to the choices made when a technology is developed, including the problem it is intended to address, whose needs it prioritizes, what information it collects, how it works, and the safeguards that govern its use. These choices are often driven by technical expertise, innovation priorities, data platforms, and artificial intelligence tools, while less attention is paid to the experiences of the people whose lives the technologies are intended to affect. Although many digital peacebuilding initiatives aim to promote inclusion, community involvement can begin only during implementation, after key design decisions have already been made. In such cases, people may participate mainly as users, sources of information, or beneficiaries.
This creates a gap between the aspirations of digital peacebuilding and its practice. A holistic approach requires moving beyond inviting communities to use digital interventions and ensuring that they have meaningful influence in designing, governing, and evaluating the technologies intended to support peace processes. Co-design means that technology developers, peacebuilding institutions, and affected communities work together from the stage of identifying a problem through to developing, testing, and reviewing a solution. It is more than consultation: it requires communities to influence decisions, rather than simply provide feedback after those decisions have been made. Digital peacebuilding should therefore not be designed for communities; it should be co-designed with communities.
Rethinking Inclusion in digital peacebuilding
Inclusion in peacebuilding is often understood through the idea of participation, but participation can take different forms and levels. It may involve being informed about a project, consulted, asked to provide information, invited to meetings, or given a role in decision-making. These forms of participation are valuable, but they do not automatically mean that people have influence over the decisions that shape a technology. Inclusion means identifying and addressing barriers that prevent different groups from taking part and having their views considered. Co-design goes further by creating a shared process in which those groups can help define the problem, shape the solution, and influence decisions throughout its development. The distinction matters: participation describes involvement, while co-design describes a process of shared influence and decision-making.
In practice, co-creation means involving communities from the beginning: identifying the problem, shaping the technological solution, deciding which information is necessary, setting ethical safeguards, testing whether the tool works in local contexts, and defining what success should look like. This does not mean that every community member must perform technical development. It means that their knowledge and priorities must influence the choices made by developers and institutions. The people involved should also reflect the different experiences within a community, including women’s organizations, young people, and people with disabilities, local peace committees, community-based organizations, traditional and religious leaders, and groups directly affected by conflict. Community ownership, in this context, does not simply mean legal ownership of software or data. It means that affected people have continuing influence, clear rights, and accountability mechanisms in decisions about how a technology is used and whose interests it serves.
To understand how inclusion can be embedded into digital peacebuilding, it is imperative to examine four interconnected dimensions: data, algorithm design, institutional governance, and legitimacy.
Designing Inclusion across the Four Layers
The data layer: Whose knowledge and reality counts?
Digital peacebuilding relies heavily on data, whether collected through community reports, social media analysis, or early warning systems. However, decisions about what data is collected, whose accounts are treated as credible, and how information is interpreted are often made by external actors. Communities should be involved in determining which knowledge is valuable and how their realities are represented. This could include local peace committee members, women’s groups, youth networks, community-based organizations, people with disabilities, and conflict-affected groups who understand local tensions and reporting barriers. Their role should move beyond being sources of data to becoming partners in knowledge production and decisions about how data is used.
Algorithmic layer: Who shapes digital tools?
Technologies are not neutral. The assumptions, indicators, categories, and rules embedded within digital systems influence how conflicts are understood and how responses are prioritized. For example, a reporting tool that relies mainly on smartphone access or written submissions may overlook people with limited connectivity, literacy barriers, or concerns about being identified. Design choices therefore have consequences and, if not governed, may reinforce existing inequalities and biases. Communities should have opportunities to shape the problem categories, language options, reporting channels, accessibility features, and safeguards built into these systems. Their contribution should inform design and testing, while technical developers remain responsible for explaining how the system works and addressing identified risks.
Institutional layer: Who governs digital peacebuilding?
Digital peacebuilding initiatives are often led or supported by governments, international organizations, researchers, civil society organizations, and technology developers. These actors provide important expertise and resources, but sustainable peacebuilding also requires meaningful involvement from the people affected by the issues being addressed. This should not be treated as an undefined call to involve ‘the community’. Depending on the context, relevant participants may include local peace committees, women’s peace organizations, youth-led groups, community-based organizations, religious and traditional leaders, local journalists, people with disabilities, and residents who use or are expected to use the technology. Institutions should establish clear ways for these groups to influence priorities, governance arrangements, decisions about data access, and the evaluation of outcomes, rather than involving them only during implementation.
The legitimacy layer: Who owns the peace process?
Successful peacebuilding depends in part on trust among communities affected by conflict. A tool may be technically sophisticated, but if it is not considered legitimate, relevant, safe, and reflective of local realities, its usefulness will remain limited. Community ownership is therefore central to sustainability. Here, ownership means more than being consulted or having access to a platform: it involves the ability to shape priorities, question decisions, understand how information is used, and hold responsible institutions to account. Digital peacebuilding should strengthen existing local peace processes rather than introduce external solutions that communities are simply expected to adopt.
Learning from Africa’s Digital Peacebuilding Experiences
Kenya provides important examples of both the opportunities and limitations of digital peacebuilding. The National Steering Committee on Peacebuilding and Conflict Management’s Uwiano Platform for Peace, including its Uwiano@108 reporting channel, uses SMS, incident reports, and media reports to support conflict prevention and coordination. The platform receives reports from the public and links them to peacebuilding stakeholders. During elections, Ushahidi’s Uchaguzi platform has also enabled citizens to report incidents through channels including SMS, WhatsApp, USSD, and social media, working with civil society partners and volunteer verifiers. In the 2022 election, Ushahidi reported that the deployment involved 19 civil society partners and collected more than 93,000 reports. Separately, the United Nations in Kenya documented a coalition of Kenyan organizations that used technology to track and counter online hate speech and incitement during the 2022 election. These examples show how digital tools can support citizen reporting, election monitoring, and responses to harmful online content. They also raise a further question: how much influence do the people contributing information have over the design, data practices, and governance of these systems?
The experience is not limited to Kenya. In Nigeria, Connected Development (CODE) partnered with Ushahidi to deploy the UZABE platform for election monitoring during the 2023 general elections. The initiative trained volunteer observers across the country to submit reports that were reviewed through a verification process. In South Sudan, UNDP has documented the use of the AlertME mobile application to connect local peace actors, including peace committee members and community focal points, with early warning and response structures. These examples demonstrate different ways that digital systems can connect local reporting with wider institutional processes. They should not, however, be taken as proof that every initiative has fully adopted co-design. The important question remains whether people are only contributing information and using tools, or whether they also help define the problem, shape the solutions, and determine how success is measured.
Across Africa, digital peacebuilding must therefore consider not only whether communities can access technologies, but whether they have meaningful influence over how those technologies are created and governed. Community voices need to be considered from the beginning to the end of digital peacebuilding processes. This must also be balanced with protection. Community participation in data collection can expose people to risks such as surveillance, retaliation, stigmatization, or the misuse of sensitive information, particularly when reports identify individuals, locations, or groups in conflict-affected settings. Co-design should never mean that communities are expected to disclose more personal information. Initiatives should collect only what is necessary, explain clearly how information will be used and shared, obtain meaningful consent where appropriate, limit access, protect stored data, and establish clear retention and deletion practices. They should also assess risks before collecting or publishing information and provide safe alternatives for people who cannot or do not wish to use digital channels. Kenya’s Data Protection Act and the African Union’s Data Policy Framework provide relevant foundations for protecting rights and strengthening responsible data governance.
Conclusion
The future of digital peacebuilding in Africa should not be measured only by technological capacity, but also by the extent to which communities affected by conflict have agency in shaping the tools designed to support peace. Inclusion is not achieved simply by providing access to technology or basic knowledge of how to use it. It requires identifying who is excluded, creating safe and accessible ways for different groups to contribute, and ensuring that their views can influence decisions. The central question for the future of PeaceTech in Africa is therefore not only: What can technology do? It is: How can communities shape the technologies that define their pathways towards peace, while ensuring that participation does not expose them to harm further?
