Page MenuHomePhabricator

[Request] Informing the design of a progression system for new editors
Closed, ResolvedPublic

Description

Please provide all the following information:

  • Context. Provide a short paragraph with some background context for your request, please include links to relevant material.

To support the goal of increasing constructive edits by new contributors, the Growth team is exploring a structured progression system designed to guide and motivate newcomers. Building on past work in Positive Reinforcement, this new feature will offer clear milestones, suggested next steps, and lightweight recognition to help newer editors (fewer than 100 edits) stay engaged and develop skills.

Primary hypothesis: If newcomers are provided with a structured progression system that includes easy first steps, motivational goals, and constructive feedback, supported by positive reinforcement such as recognition, encouragement, and visible progress, then they will be more likely to continue editing and make constructive contributions. This combination can help build confidence, support learning, and create a more motivating and rewarding editing experience over time.

Q1 focus: If we test a progression system via design prototypes with newcomers, then we can identify which types of milestones, guidance, and recognition are perceived as most motivating, and use these insights to finalize a design for future pilot wiki experimentation.


  • Description.What is your request about?

There are a few research areas that we’d like to explore and learn from.

  • Milestones appeal
    • Which milestone types feel most meaningful to newcomers? Skills-based, community recognition, knowledge-based, quality indicator, something else?
    • How might we make achievements feel credible and skill-validating?
    • What intervals feel natural vs. overwhelming?
  • Progression structure
    • How granular should the initial steps be?
    • Should the progression start pre-editing?
    • How can visual design vary in “playfulness” across different cultural contexts?
    • What makes achievements feel appropriate for Wikipedia?
  • Quality vs quantity tension
    • How to structure the progression to reward constructive vs. quick edits?
    • How to incorporate “time-based elements” vs. pure edit counts?
    • Which quality gates could guide newcomers?
    • How to make “collaborative” achievements more appealing than individual ones?
  • Human vs machine/automated recognition
    • How does the progression system complete or compete with the mentor praise?
    • What balances should there be between automated milestones and human recognition?
    • How to encourage more community thanks/praise alongside the achievement system?
  • Community aspects
    • How to avoid competitive elements? Think of leaderboards or rankings…
    • Opt-out mechanism?
    • How might we make sure that milestones support newcomers rather than distracting them
    • What makes the system feel genuine motivational

Key research questions

  • Do we need more evidence on motivation vs. barrier removal?
  • What did we learn about newcomers’ motivation that still applies?
  • How do different communities view achievement-based systems?
  • How does this build on existing features? Impact module, levelling up, personalized praise, …

  • Expected Deliverable. What is the ideal outcome or result of your request?
    • Desk research: Existing practices and pros, and cons around progression systems (badges, gamification, …)
    • Design framework: Principles and guidelines for milestone selection, and progression structure that feel genuinely Wikipedia
    • Newcomer insights: How different newcomer types respond to progression elements
    • Community review: What feels appropriate to existing/experienced editors?

  • Estimated Effort. Please provide an estimate of the amount of work needed to complete this task, if known.

  • Priority Please indicate a priority of your task and a small description of what it would unlock for you. We ask you to leave this task as “needs triage” since your request will go through a Backlog refinement process where our team will prioritize the work.

What this research unlocks:

  • Finalized progression system design for pilot testing
  • Community-tested approach for broader rollout
  • Evidence-based milestone selection for newcomer adoption/engagement/impact

I need this task resolved in:

  • 1 month.
  • 3 months.
  • 6 months.
  • Whenever you get to it :-)

  • Other. Do you have any other questions or comments ?

For use by WMF Research team; please leave everything below as it is:

  1. Does the request serve one of the existing Research team's audiences? If yes, choose the primary audience. (1 of 4)
  2. What is the type of work requested?
  3. What is the impact of responding to this request?
    • Support a technology or policy need of one or more WM projects
    • Advance the understanding of the WM projects.
    • Something else. If you choose this option, please explain briefly the impact below.

Details

Due Date
Oct 1 2025, 5:00 PM

Event Timeline

Assigning to Daisy and renaming the title.

Confirming we're taking this on for Q1 (and to start on slightly before, in mid-late June, as Daisy is available sooner)

Daisy and I met with Kirsten about this request this week and Daisy will take it from here to start a research plan and start working through further study details.

We want to look for how Tanja (and/or Pablo) can be kept in the loop and contribute to this work as well, given their related work in this space.

DKumar-WMF renamed this task from [Request] Growth WE1.1 Research Request to [Request] Informing the design of a progression system for new editors.Jun 6 2025, 2:52 PM
DKumar-WMF moved this task from Backlog to FY2025-26-Research-July-September on the Research board.

Hoping to connect with both Amin and Kirsten this week before I'm out (will return 7/10) to get clarity on asks.

Discussed the request with Tanja to see where/how we might approach this jointly, and whether there are quantitative elements to be explored. Will do another exploratory set of conversations with Tanja again and also Pablo upon my return.

Met with Kirsten and also Pablo last week to discuss additional specifics and possibilities on the quant side. Received additional follow-up from Amin this week, and shared research brief for feedback 7/22. Have started work on discussion guide in the meantime.

checked in with Sonja last week to clarify goals/brief details, followed up with team ambassadors/analytics support for recruitment details, received back legal-reviewed privacy policy and release form.

still waiting on ambassadors' response, but have some preliminary help from analytics. finalizing discussion guide and starting on recruitment this week, and reading through more material for literature review.

additional recruitment occurring this week with a finalized list from analytics. other project staging logistics ongoing.

Iflorez subscribed.

Quick PA update:
We received a two item batch request; this item was handled first.
I met with @dchen on 08/06 and the supportive material was provided the same day.
An updated request came in on 08/11 which was delivered on 08/15 after security engineering's approval and DM fine-tuning in Slack.
@dchen's feedback: "the final looks good, i will let you know if anything else comes up that could help refine any more."

hoping to schedule sessions soon, and continuing to send out recruitment outreach in batches. received updated prototypes from Barbara. light lit review still in progress and hope to wrap this week.

DKumar-WMF set Due Date to Sep 30 2025, 5:00 AM.

first sessions completed and additional sessions occurring this week and next. if desired, please view via my calendar events!

8 sessions completed. anticipating 2 more this week to conclude. please feel free to view any of interest on my calendar event attachments.

10 sessions completed! beginning analysis/synthesis this week.

completing analysis/synthesis this week and working on final report.

dchen changed Due Date from Sep 30 2025, 5:00 AM to Oct 1 2025, 5:00 PM.Sep 30 2025, 4:11 PM

checked in with Kirsten; confirmed okay to complete some remaining report clean-up and content rearranging into 10/1.

final report completed and shared last week and will schedule a follow-up Q&A session with the team soon.

Shareout to the team completed on Oct 22.