Heuristic analysis of the application - gather things that don't work

[jbubar]

Overview

We are about to deploy the application, and it would be nice to have a list of all the things that should be changed to improve the user flow. That way we can chose to make changes or not repeat the same mistakes in v0.4

Action Items

• [x] Run the application locally
• [x] Make sure that you are an admin
• [x] Create user flow of current screens
• [x] Click around the application and conduct a heuristic analysis
• [x] Place your notes in the issue
• [ ] Prioratize issues, and categorize: UX vs dev
• [ ] Create smaller issues on Github and assign them
• [ ] Usability Testing
  • [x] w/ Bonnie
  • [ ] w/ PM
• [ ] Continue checking heuristics and updating this issue

Heuristic Evaluation

1. (home) How important is it to display all the stats in Home? a. Which stats are most important?
2. (events) Clicking on meeting details also shows the same details (button is redundant). Can we add other important info (ex: zoom link, attendees, etc.)? a. Clicking close doesn’t work. How can I go back to events list from there? b. “Add event” only takes me to projects page
3. No scrolling feedback on any page a. How far can you scroll on the events page? Does it loop around? It’s hard to know without any visual feedback b. How can I search for a specific event? Can we add filter or search feature?
4. (admin) Why “add a new project” on admin page? Could probably just add a button or icon in the projects page instead? See issue: https://github.com/hackforla/VRMS/issues/1105#issue-1196722136 a. Should the user be able to, not only input project name, but also edit the project (add description, team members, etc.) when it's being created instead of having to go to projects tab and then do it? See issue: https://github.com/hackforla/VRMS/issues/1104#issue-1196718213 b. “Admin dashboard” could probably be a back arrow instead
5. (projects) How do I delete a project? a. Can I search for a project?
6. (projects>selected project) Unnecessary edit buttons on project details. Is it possible to just have one “edit project” button that lets the user edit any field? Or maybe icons instead of the word edit? a. Maybe it would be beneficial to have a display page and then a seperate edit page. b. Can “back to select project” be a back arrow instead? c. Will all the fields be used? Can we only have filled fields show up on the display page and then have all the fields appear when user wants to edit the project?
7. (admin>user management) Could probably improve filter elements on user management page. a. When I click “back to search” should it display the previous results searched?
8. Wording is confusing (events/meetings/projects). What is the difference between them, especially events and meetings? a. Some other titles and copywrite could be improved.
9. Check in as new user links to same page as create a new profile, so button is redundant.
10. (check-in) There is no back arrow to go to the previous page if user makes a mistake and wants to check in as new user instead of returning for ex. a. What’s the purpose of checking into a meeting? Who gets this information/data? Where is it displayed (will/could it appear on the events page>meeting details?)

Usability Testing with Bonnie

Task 1: Bonnie needs to add a new project

1. User gets notified of new project created but then doesn’t know where to go to view the project that has just been created.
2. The project’s form fields need data validation, as opposed to them being free text fields. a. Location: dropdown to preselected options
3. Remote: links will be provided on the events of each project
4. In person: a field appears to add an address b. Github identifier: What if there’s multiple repos? c. Google Drive ID: Is this field necessary? d. Video Conference Link: This won’t be necessary on the projects page but only for the events created for a project. e. Looking for description: We don’t need this field. f. Recruiting Categories: We don’t need this field.
5. The “ Create New Event Button” is confusing. Layout and hierarchy needs to be improved. a. Does this create an event for any project or the one the user is currently seeing?

Task 2: Bonnie needs to assign a user to a project

14. (admin>user management) Once a search result shows up the user doesn’t know where to click next to see the user details or continue with other tasks. Layout and hierarchy needs improvement. White space is tight and elements are too close together. a. The “Admin Dashboard” button calls the user to click it. b. Does a user get notified when they’ve been added to a project?

Task 3: Bonnie needs to remove a user from a project

15. (projects>selected project) UAL or member fields need to be added to the project page so the user can edit it from there as well.

Task 4: Bonnie needs to add and edit project event time

16. (events) The search feature should work using any word related to the event. Maybe we can add tags?
17. Users shouldn’t have to scroll all the way down to create another event. A button can be more accessible on the top.
18. Other filter options could be added to projects and user management pages to help the user search for and results.
19. Iconography and other components lack consistency and need improvement.
20. Reset button works with the information while it’s being edited in the modal but once the user clicks update, it doesn’t reset anymore.
21. Typography needs improvement. Type is too small, text hierarchy is missing.
22. We need to make sure we meet some accessibility and heuristic standards

Resources

https://www.figma.com/file/9c6pxjImN8MjHAZLH7zxYm/VRMS-Mocks?node-id=23726%3A2254 https://dev.vrms.io IMG_8227.pdf

[juliagab56]

Some notes from v3's heuristic analysis. Next step is comparing and prioritizing these issues with our new goals in mind.

[juliagab56]

Do we want to use this to improve v0.4 user experience?

[JudyLee533]

I am adding on to the issues from Bonnie's v3 usability testing on 10/3/22.

[juliagab56]

This issue is ongoing but we might be able to close it once we discuss it. We used it to gather pain points and heuristic information from VRMS and usability tests

[juliagab56]

Will need to transfer all research info to a doc and store it in the drive instead