5.1 Producer Conflict in an Open Peer-Production Community: Reflection of Development Phases
Conflicts among members of any OPPC reflect the current agenda of the group. As per our analysis, mapper conflict in OSM involves clashing interests among different subgroups and negative online mapper behaviors.
For example, the boundaries of the subgroups in OSM are characterized by previously known factors (i.e., gender, geographic location, level of knowledge/skill), and more recently also by professional affiliations. This reflects the progression of the OSM from a small group of like-minded users [
17,
18] to a large-scale OPPC that attracts a wide community of users with different intentions [
2]. Similarly, other OPPCs have experienced conflicts between contributors due to similar factors [
24,
41,
42,
53] and a similar progression in their growth and development.
Most OPPCs start as a small group of people with a similar level of technical expertise and a shared vision [
19,
45,
67]. Many studies demonstrate how the rise of OPPCs experiences an influx of contributors who populate products (e.g., Wikipedia articles, open source software) growing exponentially the OPPC’s reputation and usefulness [
19,
33,
58], starting a cycle where the OPPC attracts more like-minded contributors but with more diversity [
33,
67]. At a point where OPPCs saturate with contributors, they start witnessing increased conflict [
13] and experience the need for mechanisms to control the quality of their products. Consider Wikipedia, which required the implementation of selective registration mechanisms and tools to reject entries deemed low in quality [
19]. Community guidelines were implemented to set behavior expectations [
19,
40]. What was not foreseen was how such quality control mechanisms could be perceived as a burden not only for newcomers but also for long-term producers, leading to reduced participation and retention [
19,
58]. If ignored, the decline of an OPPC may start.
In this paper, we argue that applying conflict management theory can support stronger producer retention in OPPCs. From a governance perspective, the discussed producer (here, mapper) retention challenges faced by OPPCs are closely related to tensions between (1) the OPPC’s vision as an online community that is open to everybody and (2) the operational need to control product quality to attract more users and producers. [
33,
45,
67]. Our survey design was based on the first step in a conflict management process,
conflict diagnosis, and provided results that capture the snapshot of the current producer conflict in OSM (i.e., amongst OSM mappers). Numerous aspects of OSM conflict are shared with other OPPCs (e.g., geographic dispersion, diversity of contributors, introduction of code of conduct) [
13,
28], while others are specific (e.g., conflicts that are specific to map editing and the local nature of mapping). Furthermore, we collected the opinions of OSM mappers on useful conflict management tools, thus linking to the next step of conflict management theory,
intervention design. Our study thus indicates the potential of applying conflict management theory to other OPPCs to diagnose producer conflict and to extract customized design implications for conflict management tools.
We highlight the potential of the Delphi method as a data collection method and diagnostic framework in other OPPCs [
6]. Delphi has a number of advantages over other consensus-building methods, including regular single-round survey or voting. First, Delphi captures both agreements and disagreements among participants, providing an in-depth understanding of producer conflict. It consists of multiple rounds, which allow participants to reflect on the experiences of others. An online Delphi survey can support the simultaneous participation of geographically dispersed participants, potentially more numerous than in an in-person setting [
35]. Wikimedia recently used an iterative approach similar to the Delphi method to assess and manage user conflict [
65]. As a user-centered approach, community rules requested through a Delphi method might be perceived as having higher legitimacy when applied during conflict management.
5.2 Design Implications of Online Interpersonal Conflict Management Communication Channels
Throughout the survey, we see reoccurring themes among the four questions we asked the participants regarding their experience on interpersonal mapper conflict in OSM: existence of subgroups within the community and negative online mapper behaviors in mapper communication channels. From these themes, we synthesize two design implications that could help OSM mappers to manage mapper conflicts: procedural clarity and mapper interaction behavior.
Design implication on procedural clarity is focused on minimizing the ambiguity on how contributors could contribute to OPPCs in which steps. In OSM’s case, this is to address mapper conflicts among different subgroups that we found throughout the survey, as well as newcomers to contribute without fear of making mistakes and getting into unwanted conflicts with other mappers. Design implication on interactive behavior aims to encourage people to follow a code of conduct in OPPCs. In OSM, it will aim to address mapper conflicts exacerbated by negative online mapper behaviors that we found from Sections
4.2 to
4.4. We discuss examples of relevant website interface designs from other OPPCs and apply them in OSM’s context.
Our survey results show that online communication channels frequently used for conflict management by OSM mappers are fragmented into (1) public internal channels (e.g, OSM changeset comments, OSM mailing list, mapper diary/blog, and the OSM discussion forum); (2) private internal channels (e.g., direct message to a mapper via OSM mapper profile); and (3) public and private external channels (e.g., Twitter, Slack, personal email, and messenger apps). OSM mappers typically use multiple communication channels depending on the discussion topic, audience, and preference. Our design suggestions are restricted to public internal channels, as the remaining channels are impossible to monitor for compliance with the code of conduct, or because of the impossibility to customize external communication tools for OSM mapper communication. We use the OSM changeset discussion (Figure
5) as an example target for the implementation of our findings, as this channel was implemented in 2014 for the single-edit mapper conflict management [
66].
5.2.1 Procedural Clarity.
An interactive user interface for communication channels could encourage contributors towards a preferred, constructive behavior as recommended by the OPPC community guidelines, guiding them through a sequence of steps (a procedure). An implemented example is the interface of the Stack Exchange Network
9, an online knowledge community that allows users to ask questions and get answers from experienced peers in different fields. Users are shown a step-by-step guide for writing a good question (Figure
6), including concise instructions on how to write the title and body of the question, with links to useful question-asking resources.
10Procedural clarity should provide a reassuring effect on producers contributing to OPPCs, and support them in proactive participation without fear of breaching expected community practices. For example, OSM users who are registered as employees of OSM corporate partners could be prompted to be more transparent with their activities. They could also be guided to communicate clearly and openly with other users, including volunteer mappers. Similarly, newcomers could be supported with a step-by-step guide, prompting how to start a discussion with other, maybe more experienced, users. Procedural clarity might also help understand mapper behaviors that are not accepted by the community, such as vandalism. Introducing procedural design components into OSM’s official communication channels could also improve the usability of community guidelines that can often be verbose, written in a complicated wording, and are typically disjoint from the data production process.
5.2.2 Interaction Behavior.
The code of conduct in OPPCs, for example, in Wikipedia, the Stack Exchange Network, and Github, is implemented to encourage collaborative user behaviors throughout their online interaction.
11 In Wikimedia, a community survey was conducted to understand why contributors manage conflict, which responses show contributors’ voluntary compliance with the relevant code of conduct and their shared vision as members of a community.
12The recently announced OSM Etiquette Guidelines detail expected and unacceptable behaviors of OSM mappers communicating on two of OSM’s mailing lists [
48]. Except for the rare and serious ban on mappers due to vandalism or other deliberate negative actions, OSM expects and is highly dependent on mappers acting in reasonable and collaborative behavior, with voluntary adherence to community guidelines [
48]. Yet, OSM’s code of conduct is not yet exposed in the redesign of any of their tools’ user interfaces, e.g., the Changeset discussion.
Accepted behaviors could be encouraged using design components presented as embedded features in communication channels [
8]. For example, the Talk tab of each Wikipedia article exposes a table with bullet points of the desired user behavior during online interaction as codified in the community’s code of conduct (Figure
7). In OSM, expected communication behavior could be presented next to changeset comment features, to remind mappers how to better interact with other mappers. Negative wording loaded with sentiments could be automatically detected and accompanied by a suggestion for a more positive wording/tone. The proposed design components could expose mappers earlier and more effectively to acceptable behaviors in OSM, removing the barrier imposed by the Guideline being available on a separate Wiki page [
8]. They could encourage OSM mappers to interact collaboratively with each other, but without the need for enforcement.