Page MenuHomePhabricator

Introduce feature notice for the New Discussion Tool
Open, Needs TriagePublic

Description

This task is about introducing a notice to make people who have the Discussion tools beta feature enabled aware that the New Discussion Tool exists and know what to do to manage (read: enable/disable) the new tool. More details in the ===Requirements section below.

Objectives

The goal of this intervention is for people who have the Discussion tools beta feature already enabled to:

  • Be aware that the New Discussion Tool exists before they start to create a new discussion topic
  • Know what to do to try the New Discussion Tool
  • Know what to do to use the existing section=new experience
  • Know what to do to manage (read: enable/disable) the New Discussion Tool

Background

T259943 implemented the Discussion tools beta feature. To make it easier for people to use new talk page features as they're available, we implemented the Discussion tools beta feature in such a way that this single preference will "govern" the behavior of several discrete features (e.g. Reply Tool to start, then the New Discussion Tool and lastly, Visual Enhancements). [ii]

In implementing the Discussion tools beta feature in the way described above, we created the potential for a scenario that would go something like this: [iii]

  1. Person enables the Discussion tools beta feature to gain access to the Reply Tool, without fully knowing what "new tools" the beta feature description is referring to. [iv]
  2. The New Discussion Tool is made available as a beta feature by way of it being added as a sub-feature "within" the Discussion tools beta feature.
  3. At some point after "2.", Person initiates the process for starting a new discussion topic on a talk page on desktop (read: they click an Add topic or New section affordance) and could be some variation of surprised/confused/frustrated/etc. when they see the New Discussion Tool as opposed to the existing section=new form they were most likely expecting to see.

Requirements

⚠️ Note: the below are likely to change pending a decision on which of the approaches outlined above we move forward with.

When the New Discussion Tool becomes available as a beta feature, the following should be true for people who have enabled the Discussion tools beta feature in Spécial:Préférences#mw-prefsection-betafeatures...

  • When they initiate the section=new workflow for the first after the New Discussion Tool is made available...
    • They should be be made aware:
      • That a new beta feature for starting conversations on talk pages is now available before they are taken to the tool
      • What value/functionality this "new beta feature for starting conversations on talk pages" offers them (read: an in-line form for creating new topics).
      • That this "new beta feature for starting conversations on talk pages" is part of the broader project to improve talk pages.
    • They should be able to:
      • Decide to view the New Discussion Tool in once click
      • Decide to view the existing section=new form in one click
  • When some decides to view the new Discussion Tool or view the existing section=new form...

Note: additional work will need to be done to implement a persistent affordance within the New Discussion and Reply Tools that creates a way for people to easily disable these tools in Special:Preferences > Editing > Discussion pages. This work will happen in T270789.

Approaches

  1. Tooltip-like affordance
  2. Echo notification
  3. Offer a small message within the tool, similar to how the T&S are currently presented. [vii]
  4. Show people a generic dialog when they click the New section link/tab for the first time after the New Discussion Tool is made available
  5. Send a [mass] talk page message to people who have the Discussiontools Beta Feature enabled at the partner wikis where the New Discussion Tool is being made available.

Designs

@iamjessklein to post mockups here.

Done

  • Mockups that implement what the ===Requirements section describes are created and posted in the ===Designs section above
  • The mockups posted in the ===Designs section above have been implemented

i. https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Pr%C3%A9f%C3%A9rences#mw-prefsection-betafeatures
ii. Note: people are able to enable/disable features individually in Special:Preferences. See: T270121 and T270119.
iii. Please note that over time new tools for interacting with talk pages will be added. See: https://w.wiki/rqK .
iv. Thank you to @Tacsipacsi for noting this risk in T270119#6704032 which inspired us to create and prioritize work on this task.
v. By default, the tool will be enabled for people who have the Discussion tool beta feature turned on.
vi. T270119
vii.

Event Timeline

ppelberg created this task.
ppelberg moved this task from 📚 Backlog to 📢 To Do on the Editing Design board.
ppelberg moved this task from Backlog to Triaged on the DiscussionTools board.
ppelberg added a subscriber: Esanders.

This is a lot of information to throw at the user before they've even used the tool, and a lot of work to implement. We could just deploy the new feature to one or two beta wikis first and see if this is actually a problem before investing all this effort.

I also think the approach where we put a small message inside the tool explaining how to disable it in preferences is less disruptive to the workflow, and considerably easier to design and implement.

I feel that adding onboarding is a thing to avoid as much as possible. Because it's always an awful experience in every place that does it, and I doubt we'll buck that fundamental part of the concept.

Jess to talk to:

  • Content translation
  • Growth
  • Web

Goals:

  • understand how they do feature alerts

I talked to Content Translation @Pginer-WMF and Growth @RHo and learned that although there is some desire to have some kind of minimal notification for feature updates (echo notification etc) there is currently no system in place.

"Maybe in the future once there is a more stable set of features that have been used for a while that gets an overhaul. So far our users and features are fairly new and unfamiliar." - Rita

" We don't use notifications for feature updates. I think that would be a nice addition to the general beta feature infrastructure. However, I don't think there is a team actively working on it." - Pau

Pau alerted me to some relevant tickets:

So, we have a few options in terms of next steps and I think that the answer relates to whatever our real goal is here. Do we want to alert users so that they can be aware of the feature update so in turn we can get more feedback? Do we want to alert users so that they can change their settings? After talking it through a bit with @Esanders I am actually wondering if the value to users being notified (for them) is so that they can turn off the feature, which I think we would want to know about and want to know WHY. If that's true then maybe we want to alter the feedback ux/ui to help users to opt out from the feedback form. If we want to bring more attention to the feature, then, as @Whatamidoing-WMF suggests, maybe a small echo notification is more appropriate.

@ppelberg - Does this resonate with you? Which (if any) of the approaches do you suggest we move forward with?

I talked to Content Translation @Pginer-WMF and Growth @RHo and learned that although there is some desire to have some kind of minimal notification for feature updates (echo notification etc) there is currently no system in place.

This is helpful context [i][ii][iii] for us to be aware of and consider – thank you for pulling together this research, @iamjessklein.

So, we have a few options in terms of next steps and I think that the answer relates to whatever our real goal is here. Do we want to alert users so that they can be aware of the feature update so in turn we can get more feedback? Do we want to alert users so that they can change their settings? After talking it through a bit with @Esanders I am actually wondering if the value to users being notified (for them) is so that they can turn off the feature, which I think we would want to know about and want to know WHY. If that's true then maybe we want to alter the feedback ux/ui to help users to opt out from the feedback form. If we want to bring more attention to the feature, then, as @Whatamidoing-WMF suggests, maybe a small echo notification is more appropriate.

The goal of this intervention [iv] is for people who have the Discussion tools beta feature already enabled to:

  1. Be aware that the New Discussion Tool exists at the moment they are starting to create a new discussion topic
  2. Know what to do to try the New Discussion Tool
  3. Know what to do to use the existing section=new experience
  4. Know what to do to manage (read: enable/disable) the New Discussion Tool

These four points sound like they amount to a blend of what [I understand] @Esanders and @Whatamidoing-WMF to be describing/suggesting.

@ppelberg – ...Which (if any) of the approaches do you suggest we move forward with?

With the goal above in mind, as I was writing what's currently described in the task description's ===Requirements section, //one potential/ I had in mind is something that could look like some version of:

  • The tooltip we surface in VE and
  • The notice Github surfaces to draw peoples' attention to their beta Discussions feature. [v.]

Although, before moving forward with this, I'd like to understand the complexities @Esanders alluded to in T270788#6711100. [vi.]


i. T67182
ii. T76573
iii. T76580
iv. This language is borrowed from the task description's ===Background section
v.

VE tooltipGithub Discussions notice

vi. "...a lot of work to implement."

Next steps

  • @ppelberg to discuss with @Esanders the complexities he alluded to in T270788#6711100 and the approach(es) those complexities are related to.
  • Team to discuss lighter-weight approaches that could deliver on the task description's newly created ===Objectives section. Note: I've added an ===Approaches section to the task description.

11-Jan standup notes

Next steps

This morning, @Esanders shared the "complexities" come from the work involved with introducing a new UI component.

  • Team to discuss lighter-weight approaches that could deliver on the task description's newly created ===Objectives section.

The approaches the team shared:

  • Offer a small message within the tool, similar to how the T&S are currently presented within the tool [i]
  • Show people a generic dialog when they click the New section link/tab for the first time after the New Discussion Tool is made available
  • Send a [mass] talk page message to people who have the Discussiontools Beta Feature enabled at the partner wikis where the New Discussion Tool is being made available as well.

The above have been added to the task description's ===Approaches section.

Next steps

  • @ppelberg to decide on one of the approaches.

@Dyolf77_WMF, @Patriccck, @Samat and @Urbanecm_WMF: we have two questions for each of you about the New Discussion Tool.

These questions are below and so is the situation that's prompting us to ask these questions. cc @Tacsipacsi


Questions

  • 1. When and how do you think people at your wiki (ar, cs and hu) who have enabled the Discussiontools Beta Feature [i] will expect to be made aware that the New Discussion Tool is available?
  • 2. How would you expect people at your wiki to react when they go to start a new discussion and they see the New Discussion Tool instead of the existing workflow [ii], which they were likely expecting?

Situation
To make it easier for people to use new talk page features as they become available, we implemented the Discussion tools beta feature in such a way [i] that this single preference "governs" the behavior of several features (e.g. Reply Tool, New Discussion Tool and eventually, Visual Enhancements).

This means, someone who had enabled the Discussion tools beta feature to gain access to the Reply Tool might be surprised/confused/frustrated/etc. to see the New Discussion Tool, instead of the existing workflow [ii], the first time they go to start a new conversation after the New Discussion Tool has been made available as a Beta Feature.

More details
You can find additional context in the task description's ===Background section.

Timing
If possible, it would be great to hear what you all think about the above before this week is over.


i. T245539

ii. "Existing workflow" = the section=new form

Not involved in this project in my WMF capacity.

Not involved in this project in my WMF capacity.

Ah, yes. Thank you for adjusting the ticket, @Urbanecm.

Hi @ppelberg

Questions

  • 1. When and how do you think people at your wiki (ar, cs and hu) who have enabled the Discussiontools Beta Feature [i] will expect to be made aware that the New Discussion Tool is available?
  1. in my opinion, for ar wiki, while people are adding a new topic, they expect the regular tool(s), but they will notice the new tool during the normal use. It will be an efficient way to be aware of the availability of the NDT. A warning/explaining message could be added to the NDT when it is triggered in the first time.

Otherwise, we will send a message on the Community talk page, Discussion Tools project page just after releasing the feature.

  • 2. How would you expect people at your wiki to react when they go to start a new discussion and they see the New Discussion Tool instead of the existing workflow [ii], which they were likely expecting?
  1. I understand by people: user who enabled the Discussiontools, if so, they are waiting for a such update. And as they were informed about the Editing team work on this NDT, I think they will adopt it and don't hesitate to talk about it and comment it, like with the Reply Tool.

+1 to @Dyolf77_WMF re:

warning/explaining message could be added to the NDT when it is triggered in the first time. Otherwise, we will send a message on the Community talk page, Discussion Tools project page just after releasing the feature.

Hi @ppelberg

Questions

  • 1. When and how do you think people at your wiki (ar, cs and hu) who have enabled the Discussiontools Beta Feature [i] will expect to be made aware that the New Discussion Tool is available?
  1. in my opinion, for ar wiki, while people are adding a new topic, they expect the regular tool(s), but they will notice the new tool during the normal use. It will be an efficient way to be aware of the availability of the NDT. A warning/explaining message could be added to the NDT when it is triggered in the first time.

This is helpful context – we appreciate you thinking this through, @Dyolf77_WMF.

Good thought...this idea of offering some kind of onboarding experience that helps Junior Contributors, who are starting a new conversation for the first time, understand the purpose of talk pages and subsequently use them, seems like it could be valuable. Here's a ticket for that: T273079. cc @iamjessklein who expressed support for this T270788#6757670.

Otherwise, we will send a message on the Community talk page, Discussion Tools project page just after releasing the feature.

To start, we're going to do as you're suggesting above, make announcements about the tool's availability that include what changes people can expect in their experience and who will see these changes. This will happen in T273077.

If the "make announcements" method of raising awareness about the feature (T273077) proves to be insufficient at the Arabic, Czech and Hungarian Wikipedias, we can revisit this ticket and decide whether it is worthwhile to implement a way of raising awareness within the software before offering the New Discussion Tool at a larger number of projects.

  • 2. How would you expect people at your wiki to react when they go to start a new discussion and they see the New Discussion Tool instead of the existing workflow [ii], which they were likely expecting?
  1. I understand by people: user who enabled the Discussiontools, if so, they are waiting for a such update. And as they were informed about the Editing team work on this NDT, I think they will adopt it and don't hesitate to talk about it and comment it, like with the Reply Tool.

Understood.