For the case of Flow, I don't recall if there is any study that exercises that part of the UI heavily. For notifications, where the same metaphor is used, it worked well in the last round of research we did (where users were asked to use several of the actions behind a "..." menu):

all participants were able to discover the secondary actions menu when prompted (unlike the first round, where discoverability was identified as an issue)
[...]
people have no problem finding and understanding the "mark as read" option, and most are quick to find the option to mark individual messages as unread.

Thank you Pau for the quote.

all participants were able to discover the secondary actions menu when prompted (unlike the first round, where discoverability was identified as an issue)

"Discover when prompted" reveals (I think) a problem: discover because someone ask them to really pay attention about it is not the same at all than being along in front of a screen, alone, trying to find something. :) But I know, this study is for Notifications, which is not built or designed the same as Flow. And I think Notifications have a better integration of these three-dots than Flow (closer to content).

I can search for feedback, but I remember some people who asked me (at least on fr, mw or irl, including CLs) for actions which were hidden on that three-dots menu.

"Discover when prompted" reveals (I think) a problem

@Capt_Swing may be able to add to this, but I think the text refers to asking the users about a need for which an action supporting it happens to be behind that menu. I think the research plan (T116741) was created in a way to avoid leading users.

I compiled some examples from the recordings in the report from the three users willing to share their recordings publicly:

• Here a user discovers the three dots on their own (view)
• Another user checking the menu when asked about which notifications are there in the list (view).The same user looks for options to keep a notification as a reminder (view).
• Another user opens the menu when asked on how to get less notifications of that kind (view)

This is not a complete list, but illustrates that we were not simply asking them to click on those three dots.

Thank you Pau.

Having a study or feedback from a few group of users does not mean we found a global problem (or solution). I'll try to find again feedback I've read. Then, we can compare both.

Having a study or feedback from a few group of users does not mean we found a global problem (or solution). I'll try to find again feedback I've read. Then, we can compare both.

Definitely. I just want to link as much as possible from related phabricator tickets now that the information is fresh in my mind, since it is often hard to find the relevant talk page discussions/wiki page reports/video links/etc as time passes.