Drupal Usability Meeting 2023-11-17

I notice that 🐛 Put each entity type table into a details element on admin/config/regional/content-language Fixed was recently Fixed. From the issue description, it seems like a good idea, but it might be worth a quick look.

benjifisher → credited AaronMcHale → .

benjifisher → credited ckrina → .

benjifisher → credited Emma Horrell → .

benjifisher → credited rkoller → .

benjifisher → credited simohell → .

benjifisher → credited worldlinemine → .

Here is the summary provided by the Zoom "AI Companion". I have not edited it except for formatting.

Quick recap

Cristina and Ralf conducted a pilot test for a new navigation system. They discussed potential issues, usability challenges, and functionality of content types on the website. They also debated the placement and naming of the revisions option and the design of the top and side bars. The team decided to discuss the navigation system as a group rather than continuing the test. They also discussed ongoing layout and redesign work, including the change in the location of the notifications bar.

Summary

Pilot Test for New Navigation System

Cristina led a pilot test for the fourth phase of a new navigation system. She asked for the test to be conducted by Ralf, with the rest of the team observing and taking notes. Cristina emphasized the importance of verbal feedback during the test, especially on any issues or dislikes encountered. She also mentioned the possibility of having a new iteration of the navigation ready by the end of December. The test involved creating a page, naming it 'About Us', and adding it to the main menu. Ralf took the team through each step of the process, with Cristina asking him to verify each action.

Website Usability Challenges and Article Revisions

Ralf and Cristina discussed potential issues and usability challenges on the website. Ralf highlighted confusion over the horizontal toolbar with preview and save buttons, the lack of a 'save' button in the content section when in edit mode, and the omission of 'content blocks' from the sidebar. They agreed to look into these issues. In the next scenario, Ralf was tasked with finding revisions or changes made to a specific article and found no changes. Cristina then suggested Ralf try this from the edit form, which would likely require altering the script.

Toolbar, Language, Navigation, and Content Types

Ralf and Cristina discussed the placement and naming of the revisions option in a toolbar. They considered having a link to the revisions in the sidebar instead of grouping all options under a generic "More options" list. The discussion then moved on to adding French as a new language to the site, with Ralf guiding Cristina through the necessary steps. The utility of overview pages in the configuration was also debated, with Ralf favoring a minimalist approach. Finally, they discussed the functionality of content types in a system, including potential navigation issues and the possibility of adding a second icon for expanding to a specific page.

User Test Results and Navigation Discussion

Cristina and Ralf discussed the results of a user test they had conducted. Cristina suggested that they not follow the steps from the content user, as the site builder had done everything a content user would do. Ralf clarified his previous point, emphasizing the importance of the user explaining the task back to the interviewer in their own words. Cristina then introduced the idea of extra questions for all participants to answer, which Ralf posted in the chat. They agreed to use the new navigation frequently and considered the value of the extra questions. Ralf rated the current form a 3 on a scale of 1 to 3, indicating some usability issues.

Vertical Toolbar vs Horizontal Toolbar Debate

Ralf expressed his dislike for the vertical toolbar and his preference for the horizontal one. Ralf also mentioned his struggle with the scope of the question, stating that he would prefer to focus only on the left side.

Navigation System Bars Evaluation

Ralf and Cristina discussed the functionality of the top and side bars in a new navigation system. Ralf found the top bar unnecessarily complex and it was the main reason he struggled to use the system. However, he found the new navigation easy to use once he got the hang of it. He rated the sidebar 3 or 4 for its direct access to creation of entities, but found it complicated with more options. He rated the combination of the two bars as 2. Cristina agreed with Ralf's assessment, and they both acknowledged the need for technical support to use the new navigation.

Discussing Navigation Toolbar Test Results

Cristina suggested that instead of going through the test, it would be more useful to discuss the navigation as a group, as there were many opinions on the subject. She also mentioned that there were several questions and discussed the results of the three previous tests. Ralf agreed to provide feedback on the open questions after the meeting. The team discussed the resistance to change from users with experience using the top toolbar and the preference for the left toolbar from those without experience. Cristina mentioned the need for a strategy to manage change, particularly for site builders. Thomas shared his thoughts on the changes, noting that while he liked some of them, the difference in the save buttons made him feel uneasy.

Layout and Redesign Discussion

Cristina discussed the ongoing layout and redesign work, including the change in the location of the notifications bar. Aaron added that the new top bar provides a consistent experience between the front and back end, which is important for tasks such as viewing content and revisions. The team is still gathering feedback and exploring the best approach.

Menu Structure Revisions

Ralf expressed concern about the visual structure of the menu items, particularly when they are collapsed. He suggested that it might be beneficial if the menu remained open when clicked on. Benji agreed to include a visual indicator to differentiate between links and groups of links. Emma emphasized the importance of observing user behavior when navigating the menu, as preconceived notions could impact user experience. Cristina had several hypotheses about potential improvements to the menu structure, but was uncertain if changes could be made in time. She also suggested that the menu might be more useful if it were sticky, remaining visible as the user scrolls. The team agreed to continue the discussion in Slack and considered meeting again next week.

Next steps

• Cristina will provide a link for the next meeting and invite participants to test the new navigation.

That issue can also be closed. I forgot to comment back in here. I had a follow up huddle with cristina right after the meeting where aaron also joined. I've left an overall summery of the points i've noticed during the meeting, the huddle and some further testing on the weekend: #3402454-2: Prototype revision on the the Friday Usability meeting → . Commenting in here just slipped through.

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