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

Create a Survey: True Intent #2733

Closed
2 tasks done
ExperimentsInHonesty opened this issue Feb 2, 2022 · 18 comments
Closed
2 tasks done

Create a Survey: True Intent #2733

ExperimentsInHonesty opened this issue Feb 2, 2022 · 18 comments
Assignees
Labels
2 weeks inactive An issue that has not been updated by an assignee for two weeks Complexity: Missing Feature: Analytics google analytics feature: research plan any issue that is specifically about the overall research, not a subtask feature: research role: user research size: 2pt Can be done in 7-12 hours

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Feb 2, 2022

Overview

We need to create a true intent survey so that we can determine who our users are, what their goals are for accessing the website and if they are able to achieve their goals.

Action Items

  • Create survey questions
  • Review with Product

Resources/Instructions

True Intent Instructions and Survey Questions

@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Feb 2, 2022
@github-actions

This comment has been minimized.

@ExperimentsInHonesty ExperimentsInHonesty added UX role: user research Feature: Analytics google analytics feature: research plan any issue that is specifically about the overall research, not a subtask and removed UX Feature Missing This label means that the issue needs to be linked to a precise feature label. labels Feb 2, 2022
@ExperimentsInHonesty

This comment was marked as resolved.

@ExperimentsInHonesty

This comment was marked as resolved.

@ExperimentsInHonesty ExperimentsInHonesty added this to the 03.01 Roadmaps milestone Feb 2, 2022
@ExperimentsInHonesty

This comment was marked as outdated.

@JackieRiley1
Copy link

The survey has been updated. Notes addressing comments from the Google Doc have been added at the bottom of the document.

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Mar 2, 2022

@JackieRiley1 thank you for the details about consent for under 18. Please add a question to the top of the survey asking yes or no, 18 or over. If they say no, then the survey is ended.

I found this, and it might be more applicable. Please review
https://calschls.org/survey-administration/parental-consent/

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Mar 2, 2022

See Code for America's question about gender on their brigade census survey
image

@ExperimentsInHonesty
Copy link
Member Author

@JackieRiley1 Please put your research plan into the format developed on this issue
hackforla/UI-UX#120

If you have sections that are not in the current template. Please create them in your document and then note it in the guide to making a research plan issue, so that the next person who works on the guide can integrate these additional sections.

@JackieRiley1
Copy link

I've added some additional comments in response to the True Intent Survey

@github-actions

This comment was marked as outdated.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Mar 18, 2022
@ExperimentsInHonesty
Copy link
Member Author

@JackieRiley1 I have responded to your comments/questions with same. Looking forward to next version

@github-actions
Copy link

@JackieRiley1

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: "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, March 22, 2022 at 12:19 AM PST.

@github-actions
Copy link

github-actions bot commented Apr 1, 2022

@JackieRiley1

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: "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, March 29, 2022 at 12:20 AM PST.

@github-actions
Copy link

github-actions bot commented Apr 8, 2022

@JackieRiley1

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: "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, April 5, 2022 at 12:20 AM PST.

@github-actions
Copy link

@JackieRiley1

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: "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, April 12, 2022 at 12:20 AM PST.

@github-actions
Copy link

@JackieRiley1

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: "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, April 19, 2022 at 12:20 AM PST.

@github-actions
Copy link

@JackieRiley1

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: "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, April 26, 2022 at 12:21 AM PST.

@sacamp
Copy link
Contributor

sacamp commented May 1, 2022

Questions have been revised and survey implementation options are being explored in issue #2663

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 weeks inactive An issue that has not been updated by an assignee for two weeks Complexity: Missing Feature: Analytics google analytics feature: research plan any issue that is specifically about the overall research, not a subtask feature: research role: user research size: 2pt Can be done in 7-12 hours
Projects
Development

No branches or pull requests

3 participants