Page MenuHomePhabricator

Designs: Progression System to motivate and support newcomers
Open, HighPublic

Description

Project goal

To support the goal of increasing constructive edits by new contributors, the Growth team is exploring a structured progression system to guide and motivate newcomers. Building on previous work in Positive Reinforcement, this feature aims to create a rewarding contributor experience for newer editors (fewer than 100 edits) by helping them discover meaningful entry points and stay engaged as they begin contributing to Wikipedia.

Hypothesis:

Project-level Hypothesis
If newer editors (fewer than 100 edits) are offered a structured progression system with clear milestones, next steps, and lightweight forms of recognition, then they will be more likely to stay engaged and make constructive contributions — because clear guidance and a sense of progress can increase intrinsic motivation and create a more satisfying editing experience.

Q1 Hypothesis:
Improve Tone Suggested Edit (WE1.1.5) -
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.

Related work:

FAQ

Is this system only for newcomers?
While the initial scope is focused on supporting newcomers and improving constructive activation and newcomer retention, the long-term vision includes broader applicability. This may include progression pathways for more experienced contributors, in roles where more support is often needed.

What are the milestones within the progression system?
We aren't sure! That's part of what we will uncover in community discussions and user testing. Some initial ideas:

  • Verify email / add email
  • Welcome Survey (to help build your personalized editor journey)
  • Complete a small edit (Suggested Edit?)
  • Make a first unreverted edit
  • Create a user page
  • First sandbox edit
  • Watch a Wiki Minute video read a key policy page
  • Get assigned a mentor
  • Make 10 article (mainspace) edits
  • Complete a Wikipedia:Five Pillars quiz or NPOV training
  • View 3 example small edits / diffs ("Show and tell")
  • Make a first talk page edit
  • Create a user page
  • Join wiki event or WikiProject
  • Reach user group milestones (autoconfirmed, extended confirmed, etc.)
  • Qualify for Wikipedia Library access
Acceptance Criteria:
  • Work with Product to help clarify the user problem or opportunity.
  • Early design exploration: low-fidelity wireframes & explore multiple directions.
  • Community input and preliminary validation: Collaborate with Design Research and Product Ambassadors to get early feedback.
  • Second design iteration: Refine designs based on input from users, stakeholders, and technical constraints.
  • Complete prototype design testing with users.
  • Handoff to engineering: Provide specifications, assets, and interaction guidance. Collaborate on implementation questions and edge cases.

Details

Other Assignee
bmartinezcalvo

Event Timeline

KStoller-WMF moved this task from Inbox to Up Next (estimated tasks) on the Growth-Team board.
AAlhazwani-WMF renamed this task from Designs: Progression System to motivate and support newcoemrs to Designs: Progression System to motivate and support newcomers.Jul 30 2025, 3:14 PM

Thank you all for all your feedback. Sharing the up to dated version of the Progression System on mobile that we will test with users. This is a summary of what we've decided during the last conversations:

  • Levels and modules: the Progression Path is organized by expertise levels (e.g. Beginner, Active Editor, Advanced), and include modules within each level (so we can better organize the progress on each level). For example, the Beginner level (newcomers one) includes modules 1–4.
  • Progression Path:
    • Homepage: It appears as a simple section on the Homepage, showing the user’s current level (with badge), active module, and a ProgressBar to track completion.
    • Page: Users can access the full Progression Path page for more details from the Homepage’s section.
  • Progress in long tasks: To make long tasks feel more manageable, we could include text indicators showing progress (e.g. “12 of 500 edits completed”).
  • Autonomy: In some milestones, users will be able to choose between different tasks to complete. For example, in Module 2 of the Beginner level, the “Enrich an article” milestone allows users to choose between adding a citation, an image, or an internal link.
  • Contextual messages for key milestones: After completing milestones, a confirmation messages will explaining why that step matters. For example, when completing the User page, a message will appear indicating the user why this was important.
  • Barnstar on Talk page: After completing the Beginner path, users could receive a barnstar from another editor, including a personalized message. This message would appear in a popover/dialog when opening the Talk page the first time and could also be sent via notifications. The goal is to make the reward feel personal and community driven.
KStoller-WMF updated Other Assignee, added: bmartinezcalvo; removed: AAlhazwani-WMF.
KStoller-WMF added a subscriber: bmartinezcalvo.

Thanks, bmartinezcalvo, for the support! I'll moved this to Blocked until AAlhazwani-WMF can resume work on this.

This has been blocked due to other higher prioritizes. Let's discuss if there is time to pull this task (or a smaller subtask) into next sprint.

KStoller-WMF raised the priority of this task from Medium to High.Oct 7 2025, 6:42 PM
KStoller-WMF moved this task from Current Sprint to Active Epics on the Growth-Team board.
KStoller-WMF edited projects, added Growth-Team; removed Growth-Team (Current Sprint).