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

Preference Testing options for Toolkit page #3448

Closed
6 tasks done
vaisali89 opened this issue Aug 2, 2022 · 11 comments
Closed
6 tasks done

Preference Testing options for Toolkit page #3448

vaisali89 opened this issue Aug 2, 2022 · 11 comments

Comments

@vaisali89
Copy link

vaisali89 commented Aug 2, 2022

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

  • Have Bonnie add you to the 1password vault so that you can get access to our email address [email protected]
  • 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
Copy link

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
Copy link
Member

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 github-actions bot added the To Update ! No update has been provided label Aug 12, 2022
@github-actions

This comment was marked as outdated.

@nehasyed97
Copy link
Member

  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.

Screen Shot 2022-08-14 at 6 24 10 PM

@github-actions github-actions bot added 2 weeks inactive An issue that has not been updated by an assignee for two weeks and removed To Update ! No update has been provided labels Aug 19, 2022
@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@nehasyed97
Copy link
Member

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

@nehasyed97 nehasyed97 removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Aug 26, 2022
@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Sep 2, 2022
@7kram
Copy link
Member

7kram commented Sep 8, 2022

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

@ExperimentsInHonesty
Copy link
Member

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

@ExperimentsInHonesty ExperimentsInHonesty added the ready for research lead Issues that research needs to create new issues from label Nov 26, 2022
@ExperimentsInHonesty ExperimentsInHonesty removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Nov 26, 2022
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 15, 2023

  • Ready for design lead to copy the contents out of this figma file into one owned by our project.
  • 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

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on ready for design lead ready for research lead Issues that research needs to create new issues from and removed ready for research lead Issues that research needs to create new issues from labels Jan 15, 2023
@jdingeman
Copy link
Member

  • Ready for design lead to copy the contents out of this figma file into one owned by our project.
  • 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:

@jdingeman jdingeman removed the ready for dev lead Issues that tech leads or merge team members need to follow up on label Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: New Issue Approval
Development

No branches or pull requests

5 participants