This meeting takes place every Friday at 10:00am ET (7:00am PT, currently 15:00 UTC). See Time.is to see what that is in your timezone.

The meetings are held using Zoom, and a link is posted in the #ux Slack channel 10 minutes before the meeting. Agenda is first come, first serve and set by attendees. Use the Needs usability review issue tag for issues that need review and/or suggest issues in comments here.

ping:
@Gábor Hojtsy (he/him), @worldlinemine, @lauriii, @Aaron McHale, @anmolgoyal74, @Antoniya, @Ravi, @shaal, @ckrina
Go to the issue of the next meeting to add/remove yourself to/from the list.

Recording of this week's meeting: TODO

Transcript of this week's meeting: Drupal Usability Meeting - 2022-03-04.txt

We discussed the following issues:

  • [#TODO]
  • [#TODO]
  • [#TODO]

NR and RTBC issues marked Needs usability review.

Comments

benjifisher created an issue. See original summary.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Status: Active » Needs work

The main topic of discussion at this meeting was the idea of listening sessions to gather requirements for dashboards. That discussion was summarized and continued in this Slack thread: https://drupal.slack.com/archives/C1AFW2ZPD/p1648219035305469

Here is a transcript of that thread as of now:

We talked about the dashboard idea, and how to understand the problem to solve better, since dashboards are difficult to design. i've suggested a two folded approach for some initial research we agreed to post in here to discuss. (*I'll paste the rest of the points inside as a thread).

rkoller it might be useful to simply ask a wide variety of people from different roles and experience levels what their top task are they quickly need to accomplish as well as which are the types of informations they need to stay on top of and need to access easily and quickly. and to ask that question in a manner that they shouldnt think long about it but the first and most important that come to their mind. and afterwards collect the answers in a google doc or spreadsheet. so people from the ux team or anyone interested help to ask co workes, clients as well as people on meetups or camps and so forth. the only thing is we would have to agree on a brief an concise question to ask as well as the channel and format where to collect the answers. (based on the answers something like gerry mcgoverns top task methodology might be applied)
rkoller 2. aside those informal questioning and the aggregation of tasks and answers there might be the methodology of listening sessions i've already mentioned in the discussion about the dashboard here in the ux channel. a method framed by indi young. she has written a book about it called practical empathy (https://rosenfeldmedia.com/books/practical-empathy/) on rosenfeld media (well back then it wasnt exactly called listening sessions yet) and she will soon publish a new book which is currently in the making. as well as she recommends a book about how to listen well by a psychologist (https://www.goodreads.com/book/show/38370466-listening-well). all out of the scope to quickly read up and get an idea about the method. but a few months ago she did a micro course about how to conduct a listening session on the design thinking 101 podcast. https://fluidhive.com/dt101-64/ there she talks through the process as well as she provided transcripts for three listening sessions (https://indiyoung.com/demo-listening-sessions/). that way you are able to get an idea about the process and intention (edited)
rkoller it is basically you just set a topic at the beginning of a listening session and you as the person conducting the listening session dont have any list of questions. you stick to the words and mental model the person you are actually listening to is using. and then you dive in and you start to discover and get to know the inner thinking the emotional reactions and the guiding principles of the person you are listening to.
rkoller and according to indi patterns emerge already after 7to 10 listening sessions. i havent conducted those listening sessions on my own yet, as mentioned i only read up those books the last few months, and due to the lack of a suitable example havent applied them yet. but i think the dashboard topic might be a suitable example for it to give it a try.
rkoller and we agreed on the ux meeting that i'll sum up what we talked up today in regards of the dashboard related research and in regards of listening sessions post the introductory links in here everybody is able to get an idea about and we then revisit the topic in one of the next ux meetings and talk about possible wording of the questions for point 1) and where to collect the answers as well as about point 2) the listening sessions about what would be a good, concise and clear context/topic for those listening sessions
ckrina This sounds amazing! My only concern is that this research could block the feature itself (because it might take time, or not enough support from community/sponsors?) during too much time and loosing the momentum/ interest by the community. Do you think this could be focused on “what” to add instead of “creating or not” a Dashboard to avoid that?
Aaron McHale Thank you for sharing all of this @rkoller very useful! At UoE I have access to a wide network of content designers and web publishers, so if we have agreement on the question (or questions) we want to ask I might be able to share that said network for input. That would hopefully be a quick way to gather a wide range of input.
webchick I agree with @ckrina. IMO dashboards are "table stakes" at this point in basically every online application, and it's a significant hindrance for us not to have that functionality OOTB. What goes into them though needs a solid round of research so we can make sure we prioritize that this time, not just the architecture of the dashboard itself. @rkoller’s framework sounds very cool for that. I think both "figuring outs" can be done in parallel, and one doesn't need to block the other.

benjifisher credited AaronMcHale.

benjifisher credited andy-blum.

benjifisher credited kimberlly_amaral.

benjifisher credited rkoller.

benjifisher credited victoria-marina.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented

I am crediting the attendees.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented

benjifisher credited Guilherme Rabelo.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave commented
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.