Page MenuHomePhabricator

Notifications: Research: Map Junior Contributors' current notification experience
Closed, ResolvedPublic

Description

This task represents the work involved with creating journey maps that lead the team to understand what opportunities exist for improving the current talk page notifications to make it easier for Junior and Senior Contributors to know:

  1. When another person is talking to them.
  2. When another person is saying something in a conversation they are interested in..

Journeys

As part of this task, we will create maps of these two stories/journeys across desktop and mobile web...

Journey nameJourney startJourney end
1) Junior Contributor starts a new discussion topic on an article talk pageJunior Contributor wants to make their first edit to the article and they do not know how.Junior Contributor feels confident editing the article in a way the the project and other editors will deem valuable.
2) Senior Contributor starts a new discussion topic on a Junior Contributor's user talk pageJunior Contributor makes an edit to an article that defies Wikipedia's policies.Junior Contributor thinks they have a better understanding for what a "good edit" of Wikipedia can look like and feels empowered to start making more of them.

Done

  • Journey maps are created for the two Journeys above.

References

Below are some links that may be helpful as you think about this task. It is not exhaustive.

Event Timeline

ppelberg renamed this task from [SPIKE] Map current Junior Contributors' current notification experience to [SPIKE] Map Junior Contributors' current notification experience.Oct 31 2020, 12:26 AM

I am trying to decide which wiki to test on.
Would it be easiest to use the prototype server?
Will I get normal notifications there for each action that I take?

The plan here would be to use two pages - an article page and a user talk page and then try to reproduce each step in the flow to see at what touchpoint a junior contributor receives notifications, where they am getting them and if the type and instructions make sense.

CC/ @Esanders @matmarex @DLynch

@ppelberg - Can you give me edit access to the notifications spreadsheet doc? I would like to add a page to it for the user experience of notifications so that it's all in one place.

@ppelberg - Can you give me edit access to the notifications spreadsheet doc? I would like to add a page to it for the user experience of notifications so that it's all in one place.

@iamjessklein: can you use the sheet temporarily titled "JESS" in this workbook [i]? I do not have edit access to the one listed in the task description [ii] either.


i. https://docs.google.com/spreadsheets/d/1bxaYJunuQCOVo4Ri8099EU6saSmmnyRITMSAoUkKOb0/edit#gid=493171328
ii. https://docs.google.com/spreadsheets/d/1PdGW5JxhLcXuYJR4iIgSt8aumCRuda2j934eb-JCmaQ/edit#gid=0

For the purpose of this research, I am going to use the following links:

Can anyone tell me if there's an email associated with the user accounts and if not, how can I make that association?

Notes from the conversation @iamjessklein and I had earlier today...
As Jess and I were talking today, it became clear that we had slightly different definitions in mind for what "notifications" means/refers to in the context of this task:

  • For Jess, she understood "notifications" as any point throughout a Junior or Senior Contributors' journey (defined in T247763) where another person and/or the "system" is talking to you.
  • For me (Peter), I understood "notifications" as any point when another person is talking directly to you.

After identifying the above, we came to wonder: What definition for "notifications" is appropriate in this context?

Jess then went on to note that if we are to assume a "broader" definition of notifications as we construct the "map" this task is asking for, we could identify opportunities to increase the likelihood Junior Contributors start and continue making successful edits to Wikipedia that we might not notice should we assume a "narrower" definition of notifications.

On thinking about the above some more with the objective of this work (T233447) in mind [i], for the purpose of this task, I'd like us to remain focused on mapping the experiences around the "notifications" that are sent when someone is talking to "you."

This means, I'd like us to "map" out the experience for the following notifications:

  • Someone comments on your user talk page [ii]
  • Someone mentions you in a comment [iii]
  • Someone mentions you in an edit summary [iv]
  • Someone starts a new discussion on your user talk page [ii]
  • Nice to have: someone send you an email [vi]

Rationale: while identifying opportunities for new notifications to be sent could be a secondary effect of the work this task is asking, the primary objective is to understand the extent to which Junior Contributors are finding the existing notifications valuable and effective.

Resulting ask: Jess how does the above sound to you? Are there new questions the above raises for you Provided, you are okay with taking the approach above to start, I'll update the task description's "Artifact components" section to reflect thsi thinking.


i. "Junior and Senior Contributors receive timely and relevant responses to the things they say."
ii. https://www.mediawiki.org/wiki/Help:Notifications/Types#Talk_page_messages
iii. https://www.mediawiki.org/wiki/Help:Notifications/Types#Mentions
iv. https://www.mediawiki.org/wiki/Help:Notifications/Types#Mentions_in_edit_summary
vi. https://www.mediawiki.org/wiki/Help:Notifications/Types#Emails_from_other_users

I'm happy to do the approach that you provided. I still feel the need to
document the meta workflow at some point. Is there a ticket to do that
somewhere else?

I'm happy to do the approach that you provided.

Cool cool.

I still feel the need to document the meta workflow at some point. Is there a ticket to do that somewhere else?

Here's one: T267657.

Tho, it's just a placeholder...can you please fill in the description with what you have in mind?

Task description update
I've updated the task description to include the updated Notification spreadsheet @Catrope created in T259572#6615268.

See:

Spreadsheet listing the different notification people can receive on Wikipedia; last updated 2020: Notification spreadsheet.

@Esanders is updating test wiki so that the new discussion tool works there and i can test it properly.

iamjessklein renamed this task from [SPIKE] Map Junior Contributors' current notification experience to Map Junior Contributors' current notification experience.Feb 4 2021, 5:53 PM
iamjessklein renamed this task from Map Junior Contributors' current notification experience to Notifications: Research: Map Junior Contributors' current notification experience.Feb 5 2021, 5:09 PM

Update: 10-Feb
Below is a summary of the outcomes from the meeting @iamjessklein and I had earlier today...

Journey scope: work on this ticket will be finished when we have produced two journey maps that illustrate the following user stories:

Journey nameJourney startJourney end
1) Junior Contributor starts a new discussion topic on an article talk pageJunior Contributor wants to make their first edit to the article and they do not know how.Junior Contributor feels confident editing the article in a way the the project and other editors will deem valuable.
2) Senior Contributor starts a new discussion topic on a Junior Contributor's user talk pageJunior Contributor makes an edit to an article that defies Wikipedia's policies.Junior Contributor thinks they have a better understanding for what a "good edit" of Wikipedia can look like and feels empowered to start making more of them.

Journey map purpose: these journey maps should lead the team to understand what opportunities exist for leading Junior and Senior Contributors to have an easier time knowing the following:

  1. Junior and Senior Contributors know when another person is talking to them.
  2. Junior and Senior Contributors know when another person is saying something in a conversation they are interested in..

Next steps

  • 1. @iamjessklein to finish drafting the high-level steps within "Journey 1)".
  • 2. @ppelberg to review and offer feedback about the high-level steps within "Journey 1)".
  • 3. @iamjessklein to draft the high-level steps within "Journey 2)".
  • 4. @ppelberg to review and offer feedback about the high-level steps within "Journey 2)".
  • 5. @iamjessklein to draft the details of what people experience within each step of "Journey 1)".
  • 6. @iamjessklein to draft the details of what people experience within each step of "Journey 2)".

๐Ÿ‘

Great. Task description updated with what we decided on in T266203#6820285.

As I'm working on trying to recreate the experiences that we listed in the Task Description, I noticed that I wasn't getting any kind of notification for Watching the page. I've discussed this with @Catrope and @Esanders and in technical terms they believe the issue is that the enotifwatchlistpages preference defaults to false. This means that the notification actually DOES exist but it is by default unchecked when it's accessed (if accessed somehow magically via the bottom of the user profile tab) on all wikis.

If you do enable that, you get emailed once when a watched page first changes, but then if it changes again, you don't get subsequent emails until you visit that page (so you don't get a deluge of emails).

Many experienced users have either found this feature and enabled it, or they use their watchlist as a dashboard and check it multiple times per day.

This is mostly an observation that I wanted to call out because it seems bizarre but also, perhaps, the off-by-default preference is a bug?

Some relevant tasks from previous times people brought up the idea of sending watchlist emails by default:

If you do enable that, you get emailed once when a watched page first changes, but then if it changes again, you don't get subsequent emails until you visit that page (so you don't get a deluge of emails).

See also T203941, which takes this feature and makes it an echo notification (web and/or email). It has been written, but not deployed anywhere.

I've made a map of the first draft of the journey maps laying out what I see as possible design intervention/opportunities for the page.

Here is the link to the FIGMA file.
Please provide high level feedback here in Phabricator and discreet pieces of feedback or clarifications as comments on the Figma file.

Note that these are mapping the experiences using the current editing experience on Talk Pages (not Flow or Liquid Discussions)

Here are some screenshots (primarily so you can make sure that you are looking at the correct screens):

Article Talk Journey Map:

User Talk Journey Map:

I've made a map of the first draft of the journey maps laying out what I see as possible design intervention/opportunities for the page.

Each new iteration of these journey maps is more legible than the previous one...nice work, @iamjessklein .

Please provide high level feedback here in Phabricator and discreet pieces of feedback or clarifications as comments on the Figma file.

I've added comments in the Figma file [i]; I figure we can document any salient high level thoughts in Phabricator after you and I talk next.


i. https://www.figma.com/file/kU1p9eny9TCJTlG8ZsnhsV/OWC-x-Journey-Maps?node-id=316%3A2

Replied to your comments, please reply or "Resolve" the comment on the file to communicate that you are good with the response.

Replied to your comments, please reply or "Resolve" the comment on the file to communicate that you are good with the response.

โœ…