Page MenuHomePhabricator

Impact Module: New editors who have edited outside of the main namespace should see the Impact module empty state
Closed, ResolvedPublic

Description

User story & summary:

As a new editor who has edited outside of mainspace, I want the impact module's layout to make sense.
As the Growth PM, I want to be sure that our A/B test isn't influenced by the empty state logic.

Example of current issue

The old impact module only displays if a user has edited in mainspace. The new impact module should follow that same logic to ensure this change isn't impacting activation data in the A/B test AND so we ensure newcomers aren't seeing an odd partially empty impact module (or the demotivating "0 views" mobile preview card).

Screenshot 2023-06-09 at 11.58.20 AM.png (1×798 px, 72 KB)

Mobile Preview: includes article view count (despite no article edits)

Screenshot 2023-06-09 at 11.56.26 AM.png (494×1 px, 43 KB)

Background & research:

This task is important because 10% of new registrations activate outside of the main namespace. These account for 23–25% of activations on desktop, and 29–30% of activations on mobile. (From the Growth Pilot Wiki Levelling Up experiment T337320#8919203)

Acceptance Criteria:

Given I'm logged into an account that hasn't edited in mainspace,
When I visit the newcomer homepage,
Then I see the Impact module's empty state

Event Timeline

KStoller-WMF renamed this task from Impact Module: empty space below scorecards to Impact Module: improvements for new editors who have edited outside of the main namespace.Jun 9 2023, 7:15 PM

As mentioned in T337320, I wonder if the large number of outside mainspace activations are in User Talk and Wikipedia/Wikipedia Talk tracks with newcomers using the Help panel/Mentor feature? I also wonder if we are saying that this is proportion of non-mainspace activation is higher than the old Impact module design or overall? If not, it generally seems that the non-mainspace activation levels would be hard to shift via a change in the Impact module design.

As mentioned in T337320, I wonder if the large number of outside mainspace activations are in User Talk and Wikipedia/Wikipedia Talk tracks with newcomers using the Help panel/Mentor feature?

Good question, I'm sure that some of the "outside mainspace activations" are from newcomers asking Mentee questions. But my understanding is that this doesn't differ significantly across the experiment and control group:
"Mentor module interactions: We find no significant difference in the proportion of newcomers who interact with the Mentor module. The proportion for newcomers who get the old module is 2.4%, for those who get the new module it's 2.2%. A Chi-square test finds this difference not significant". https://www.mediawiki.org/wiki/Growth/Positive_reinforcement#Impact_4

I also wonder if we are saying that this is proportion of non-mainspace activation is higher than the old Impact module design or overall? If not, it generally seems that the non-mainspace activation levels would be hard to shift via a change in the Impact module design.

I don't think the new impact module has really shifted this, based on @nettrom_WMF 's comment here: https://phabricator.wikimedia.org/T337320#8919203 "There's not a significant difference between the experiment groups."

All that being said, I am considering if we want to adjust the logic to simply match the previous behavior:
Given a new editor hasn't edited in mainspace,
When they visit the newcomer homepage,
Then they see the Impact module's empty state (which includes a call to action to try Suggested edits)

That way we are removing a potential confounding variable from the experiment. Any concerns with that approach? @nettrom_WMF / @RHo / @JFernandez-WMF

As mentioned in T337320, I wonder if the large number of outside mainspace activations are in User Talk and Wikipedia/Wikipedia Talk tracks with newcomers using the Help panel/Mentor feature?

Good question, I'm sure that some of the "outside mainspace activations" are from newcomers asking Mentee questions. But my understanding is that this doesn't differ significantly across the experiment and control group:
"Mentor module interactions: We find no significant difference in the proportion of newcomers who interact with the Mentor module. The proportion for newcomers who get the old module is 2.4%, for those who get the new module it's 2.2%. A Chi-square test finds this difference not significant". https://www.mediawiki.org/wiki/Growth/Positive_reinforcement#Impact_4

I also wonder if we are saying that this is proportion of non-mainspace activation is higher than the old Impact module design or overall? If not, it generally seems that the non-mainspace activation levels would be hard to shift via a change in the Impact module design.

I don't think the new impact module has really shifted this, based on @nettrom_WMF 's comment here: https://phabricator.wikimedia.org/T337320#8919203 "There's not a significant difference between the experiment groups."

All that being said, I am considering if we want to adjust the logic to simply match the previous behavior:
Given a new editor hasn't edited in mainspace,
When they visit the newcomer homepage,
Then they see the Impact module's empty state (which includes a call to action to try Suggested edits)

That way we are removing a potential confounding variable from the experiment. Any concerns with that approach? @nettrom_WMF / @RHo / @JFernandez-WMF

SGTM, thanks!

KStoller-WMF renamed this task from Impact Module: improvements for new editors who have edited outside of the main namespace to Impact Module: New editors who have edited outside of the main namespace should see the Impact module empty state.Jun 23 2023, 8:27 PM
KStoller-WMF updated the task description. (Show Details)

That way we are removing a potential confounding variable from the experiment. Any concerns with that approach? @nettrom_WMF / @RHo / @JFernandez-WMF

This sounds good to me too! Happy to reconfigure some data aggregation to start fresh once this is deployed as well.

Change 934368 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] User impact: set module unactive until user edits in mainspace

https://gerrit.wikimedia.org/r/934368

Sgs changed the task status from Open to In Progress.Jun 30 2023, 9:01 AM
Sgs moved this task from In Progress to Code Review on the Growth-Team (Sprint 0 (Growth Team)) board.
Urbanecm_WMF changed the task status from In Progress to Open.Jul 7 2023, 8:16 AM
Urbanecm_WMF moved this task from Code Review to QA on the Growth-Team (Sprint 0 (Growth Team)) board.

Change 934368 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] User impact: set module unactive until user edits in mainspace

https://gerrit.wikimedia.org/r/934368

Etonkovidova subscribed.

Checked in testwiki wmf.17. The edits in non-main namespace (User page and another User talk page are not present in the new Impact module.

The screenshots are for a user who did two non-main namespace edits.

DesktopMobile
Screen Shot 2023-07-12 at 8.15.53 AM.png (1×1 px, 192 KB)
Screen Shot 2023-07-12 at 8.16.34 AM.png (1×768 px, 179 KB)
Screen Shot 2023-07-12 at 8.18.01 AM.png (1×742 px, 126 KB)

Note: Moving to Design review to make sure that the following cases are ok.

  • a user with non-main namespace edits sees the notification
    Screen Shot 2023-07-12 at 8.14.22 AM.png (1×1 px, 330 KB)
  • a user with non-main namespace edits may receive Thanks. The info popup on the new Impact module informs a user "You may be thanked by another contributor for an edit you’ve made [...]". So a user sees thanks count, and is informed that those thanks are for their edits, and yet, the Impact module edit count is still zero.

Screen Shot 2023-07-12 at 8.36.13 AM.png (1×1 px, 228 KB)

@Etonkovidova, thanks for documenting these cases where the "0 edits so far" text seems incongruous with the "You've made your first edit" notification or Thanks count.

@JFernandez-WMF - This is in design review for you to decide if this incongruity is OK, and if you consider this task resolved / complete.

My opinion is that I don't think this is something we need to fix as part of this task. I think we can consider this task resolved and just create a follow-up task to consider an improvement in the future... perhaps the empty state should say "0 article edits so far" or something?