Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Usability Test: Wiki's Information Architecture #168

Closed
6 tasks
hannahsgr opened this issue May 5, 2022 · 3 comments
Closed
6 tasks

Usability Test: Wiki's Information Architecture #168

hannahsgr opened this issue May 5, 2022 · 3 comments

Comments

@hannahsgr
Copy link
Member

hannahsgr commented May 5, 2022

Overview

Do a moderated usability tree test on the revised information architecture on a small group of people (4-6) to see how people navigate the site and find information. The purpose of this usability test is to catch any problems people may encounter before launching another tree test to the HfLA community.

Action Items

  • Create a 1-1 usability testing script
  • Create a tree test
  • Recruit participants
  • Run study
  • Analyze findings
  • Revise the IA based on findings

Resources/Instructions

https://github.com/hackforla/access-the-data/wiki
IA Tree Test Research Plan
Figma Site map
Figma IA
ATD IA Tree Test Research Report
ATD Sitemap
Tree Test Report)

@hannahsgr hannahsgr added enhancement New feature or request feature: user research role: research size: 2 pts 2 points = 7-12 hours and removed enhancement New feature or request size: 2 pts 2 points = 7-12 hours labels May 5, 2022
@hannahsgr hannahsgr added this to the 05 - Website: Information Architecture and Sitemap milestone May 5, 2022
@lrchang2
Copy link
Contributor

@hannahsgr how is this different from #164 and is it needed?

@mxajPrice mxajPrice removed this from the 05 - Website: Information Architecture and Sitemap milestone Jun 28, 2022
@lrchang2
Copy link
Contributor

lrchang2 commented Jul 5, 2022

@hannahsgr Please add update using this template (even if you have a pull request)

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either:

  1. ask for help at your next meeting
  2. put a "Status: Help Wanted" label on your issue and pull request
  3. put up a request for assistance on the #access-the-data channel.

@hannahsgr
Copy link
Member Author

This issue is on hold as the design team updates the information architecture on the website.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

7 participants