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

A/B Testing Information Architecture Labels #164

Closed
4 tasks done
hannahsgr opened this issue May 1, 2022 · 4 comments
Closed
4 tasks done

A/B Testing Information Architecture Labels #164

hannahsgr opened this issue May 1, 2022 · 4 comments
Assignees

Comments

@hannahsgr
Copy link
Member

hannahsgr commented May 1, 2022

Overview

A/B test the labels of the information architecture of the website to identify which labels people would most commonly look under to find information.

Action Items

  • Create an A/B test survey
  • Administer the survey
  • Analyze the results
  • Update the information architecture

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 this to New Issue Approval in ATD Product Management via automation May 1, 2022
@hannahsgr hannahsgr added this to the 05 - Website: Information Architecture and Sitemap milestone May 1, 2022
@hannahsgr
Copy link
Member Author

Progress: Created and administered survey. I will finalize analysis on Friday. I currently have 14 respondents and the data shows clear trends/"winners."
Blockers: None
Availability: 6 hours
ETA: Friday

@lrchang2
Copy link
Contributor

@hannahsgr are you still doing a/b testing for the info architecture or has this been pivoted to usability testing? if you are still working on this, please provide update, thanks!

@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.

@lrchang2 lrchang2 moved this from New Issue Approval to Prioritized Backlog in ATD Product Management Jul 5, 2022
@hannahsgr
Copy link
Member Author

This issue is complete. I will close.

ATD Product Management automation moved this from Prioritized Backlog to Done Jul 5, 2022
@mxajPrice mxajPrice removed this from Done in ATD Product Management Jul 7, 2022
@mxajPrice mxajPrice added this to New Issue Approval in MVP - CLOSED via automation Jul 7, 2022
@mxajPrice mxajPrice moved this from New Issue Approval to Done in MVP - CLOSED Jul 7, 2022
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

5 participants