Wikimedia Product/Contribution taxonomy

Rationale
Our wikis are nothing without their communities, and retention of new and existing editors alike has been a perennial challenge. There are a very large number of contribution tasks across our wikis, and they vary considerably in their approachability, scalability, and how much they contribute to editors' retention or burn-out.

Almost all tasks and workflows involve the platform maintained by the Foundation (edits, diffs, templates, categories, …); some tasks are supported directly with native tools maintained by the Foundation (the citoid service, the OTRS e-mail ticket system, the page views tool); some use near-native tools created and maintained by community members (gadgets and user scripts), or more full "second party" tools (RTRC, AWB, Twinkle, etc.); finally, some use "third party" tools (browser spell checkers, browser extensions like Grammarly, and so on). Some tasks require a lot of experience, domain knowledge, social capital within the community, having the right tools, or other key items.

On-boarding to these tasks can thus require these needs to be met, but without proper support editors can fail to get "in". Similarly once using the tools, editors can be frustrated by lack of workflow support and eventually leave. Understanding what we have is key to building better editing experiences.

What does the Contribution Taxonomy consist of?
The concept framework for the initial contribution taxonomy project, is to the right. It defines the scope of contribution workflows that were documented in this first round. There are two parts to the contribution taxonomy:

Master inventory includes

 * Wikipedia Workflows and steps
 * Assessment criteria
 * Weighting matrix

Visualization system

 * Visual elements used to build workflow visuzlizations
 * Workflows that have been visualized

The master inventory
The master inventory contains the bulk of the information on workflows and steps.


 * Scroll through and look at details of the 88 workflows and over 500 steps listed in the initial round of building out this taxonomy.

The Assessment criteria
The assessment criteria was designed to assess each step and workflow in order to select the most important steps and workflows to focus on for a particular project or team.

The criteria is divided into two sets:


 * Current User Difficulty asses the skill levels needed to accomplish the workflows or steps. These specific criteria are:
 * Process familiarity: How visible and clear is the process? What's the learning curve like?
 * Technical comfort: Is much technical experience needed for me to be comfortable taking part?
 * Community feeling: How much understanding of the community and its values do I need to do this?
 * Personal social capital: Do I need to have and spend my personal social capital to make this happen?
 * Domain knowledge: How much familiarity with the content's or policy's topic you I need to have to be able to participate?
 * Moble potential ability criteria assesses if the step or workflow is most or least suitable across to be built for mobile. The specific criteria are:
 * Parallel activiteis: Do I need to have many things open at once to do this?
 * Detail/high context (small screen issues): Is there a lot of context, where I might need to repeatedly zoom out and in to understand it?
 * Temporal length (continuous use issues): Do I have to do this all at once, or can I do a little and then come back?
 * Tied steps (continuous use issues): Must I do lots of steps in succession, or is it one-and-done?
 * Precision needed (touch screen issues): How important is very careful pixel-perfect / key sequence precision to the task?

There are also some measures about scale and permissions included in the master inventory. These measures are used along with the above groups of criteria, to assess the importance of working on one workflow or another.


 * How many times does this workflow happen per day? (See columns R, S, T, U, V)
 * Does this happen on every wiki, or just one/some? (See columns Z, AA, AB, AC, AD)
 * Is this step something that happens a lot? ( To do this, one needs to filter by the steps’ codes in colunm Y)
 * Do I need any special rights / access to do this? (see column AT)
 * Do I need a special tool to take part here? (See column X)
 * Does this only work if my wiki has this set up? (see column AR)
 * Do I need anything as a user to do this? (See column AS)

The weighting system
The weighting system is inside the master inventory, and is used to raise and lower the priority of specific sets of criteria. In using the weighting system, people assessing which workflows to focus on can weight the criteria for a specific audience, community, platform or team. Once the weighting is defined, it is applied to the workflows and steps that have been scored against the assessment criteria, in the master inventory.

The visualization system
The visualization system consists of a set of elements that are used to visually build out the steps and workflows listed in the master inventory.