User Story:

As an experienced Wikimedian editor or patroller, I want access to impact metrics that match the depth and complexity of my contributions, so that I can efficiently understand and evaluate my work without relying on tools that are too basic or disconnected from my workflow.

Description

The Growth team’s Impact module on the Newcomer Homepage is designed to reinforce early contributions by showing lightweight impact metrics (for example, pageviews and edit counts). However, community feedback suggests that the module becomes less useful as editors gain experience, particularly for highly active contributors and patrollers.
More experienced editors often rely on external tools such as the XTools Edit Counter for deeper and more comprehensive contribution insights. This raises an opportunity to rethink how the Impact module scales with user experience, and whether it should adapt, redirect, or phase out over time.

Problem

The current Impact module:

• Is optimized for newcomer motivation, not ongoing contributor workflows
• Provides limited depth compared to tools used by experienced editors
• Does not adapt based on editor maturity or needs

Community feedback

In T341599#11721478, @Mathglot wrote:

The more experience a user has, the more they should shift away from using the Impact module and toward the Toolforge Edit counter tool, which contains all of the Impact stats (except for 'streak', which is probably the least valuable of them, especially when one is no longer a newbie).

Note: the tool does have some limits, but they are stratospheric; one million edits is a hard limit. For a typical user, results take a second or two. The #1000 top editor (99k edits) takes about 9 seconds to return complete results. The #25 editor (918k edits) takes over a minute. For a user with > 1M edits, the tool returns immediately but with only one estimated statistic.

I would propose we implement a "shift" in the Impact module, thus:

• add an Ec tool link below the current stats when the users total edits exceeds X (X =~ 1,000?)
• replace all content in the module with a 'Please see...' and a link to the Ec tool when total edits exceeds Y (Y =~ 5,000?)
• drop the Impact module when total edits exceeds Z (Z =~ 10,000?).

So, for their first 1,000 edits, the modules would appear as it does now, and then at thresholds X, Y, and Z it would shift them increasingly towards using the tool.

To help support this, and come up with good values for X, Y, and Z, it would be helpful to see a line graph of number of clicks on the Homepage tab as a percentage of all clicks by a given user (y-axis) plotted against total number of edits (x-axis). This might be useful for other growth apps as well.

Goal

Explore design directions for how the Impact module could better support:

• More experienced editors
• Patrollers and high-volume contributors
• While maintaining its effectiveness for newcomers

Design questions / exploration areas

• Should the Impact module adapt based on experience level? If so, how?
• What is the right balance between keeping users within the Homepage ecosystem & pointing them to external tools like the XTools Edit Counter?
• Are there opportunities to surface more advanced metrics in-product?

Acceptance criteria

• Design exploration includes multiple concepts
• Sharing designs with involved WMF teams and interested community members (via this task)