Preference Testing options for Toolkit page

[vaisali89]

Overview

Conduct Preference testing of options provided by the design team for the Toolkits page. Four variations of design have been provided for testing.

Action Items

• [x] Have Bonnie add you to the 1password vault so that you can get access to our email address [email protected]
• [x] Read this article in order to get a refresher/primer/good overview of how best to utilize preference testing.
• [ ] Sign up for a free account on Usability Hub using the project email
• [ ] Set up a preference test that asks participants to compare the four versions, which are : - Applied filer tags on the side vs on the top - The look of the filters - Light background vs dark background - How results show on the page: 3 columns vs 1 column of Figma file
• [ ] Recruit participants through Hack for LA Slack channels
• [ ] Present findings to Product and Design to decide on which version should be developed.

Resources/Instructions

Usability Hub: An introduction to preference testing Usability Hub: Sign Up Figma file

[github-actions[bot]]

Hi @nehasyed97, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[ExperimentsInHonesty]

Hi @nehasyed97 After meeting with Sija today, I setup this Figma page in our Figma account, so that we could do testing internally (with team on Sunday) before we go to external users via usability hub

https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=19750%3A127094

I also created the following items in the slack channel so we can do voting https://hackforla.slack.com/archives/C018FMQTWMT/p1660170421953849

[github-actions[bot]]

@nehasyed97

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

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

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, August 9, 2022 at 12:20 AM PST.}

[nehasyed97]

1. Progress: Completed issue today (14/08/2022) via live preference test. Out of 17 voters, 14 displayed a preference towards Toolkit Dark bg - option 3. While the issue is complete, I will be reaching out to individuals with civic tech jobs to understand the way in which they conduct preference tests. This will help uncover if there are any ways to improve our current method.
2. Blockers: I am not entirely sure how to locate members with civic tech jobs but will explore different Slack channels and send out a message if I need help. I am also not entirely sure on how to create a Figjam file but will have more clarity regarding this once I am able to connect with somebody within civic tech.
3. Availability: 6 hours.
4. ETA: 1/1.5 weeks.
5. Pictures: Attached is the selected Toolkit Dark bg - option 3.

[github-actions[bot]]

@nehasyed97

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

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

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, August 16, 2022 at 12:21 AM PST.}

[github-actions[bot]]

@nehasyed97

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

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

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, August 23, 2022 at 12:25 AM PST.}

[nehasyed97]

Progress: I have spent the last few days playing around with Figjam to come up with a model that could (potentially) be used for preference testing moving forward. Currently, I have come up with 3 different models and will use our team call on Sunday to decide on the most efficient one. Blockers: As I am very new to Figjam and teaching myself how to navigate it, the models I am coming up with are relatively simple. Availability: 6 hours. ETA: August 28, 2022. Pictures: N/A

[7kram]

@ExperimentsInHonesty Because it involves toolkit, lets add the Homepage Launch milestone

[ExperimentsInHonesty]

@nehasyed97 You closed the issue but there are no details of what the final determination was

[ExperimentsInHonesty]

• [ ] Ready for design lead to copy the contents out of this figma file into one owned by our project.
• [x] Ready for development lead to create an issue to start laying out this page. It will eventually replace the toolkit page, but we could develop it with a different name and then replace the toolkit page when its done.
• [ ] Ready for research lead to make sure the research is properly recorded in the wiki

[jdingeman]

• [ ] Ready for design lead to copy the contents out of this figma file into one owned by our project.
• [x] Ready for development lead to create an issue to start laying out this page. It will eventually replace the toolkit page, but we could develop it with a different name and then replace the toolkit page when its done.
• [ ] Ready for research lead to make sure the research is properly recorded in the wiki

Dev issue made here:

• #3959