Guide: Creating a UX survey template

[ExperimentsInHonesty]

Overview

We need to create a survey template that has all the questions that we need to ask so that we can create new community surveys quickly

Action Items

Action Items

• [x] Gather examples of how other Hack for LA projects or volunteers have done this (if applicable), adding each example as a link in the resources section below
  • [x] If the guidance you received from the teams that have done this practice was not sufficient, remove the "Guide: Gather Examples" label and add the "Guide: Research" label
• [x] Research existing information about [name of item] in [relevant resources, articles, etc.]
  • [x] Once done, evaluate if the guide requires a template. If it does then
  • [x] if yes, remove the "Guide: Research" label and add the "Guide: Draft Template" label
    • [x] Create a draft template
      • [x] Once done, remove the "Guide: Draft Template" label and add the "Guide: Draft Guide" label
  • [ ] if no, remove the "Guide: Research" label and add the "Guide: Draft Guide" label Create a draft guide, either in markdown format in this issue or a google doc in the ux/ui google drive
  • [x] Once done, remove the "Guide: Draft Guide" label and add the "Guide: Needs Peer Review" label
• [x] Review the guide with UX/UI community of practice
  • [x] Once done, remove the "Guide: Needs Peer Review" label and add the "Guide: Leadership Review" label
• [ ] Present to the Hack for LA leadership team for sign off
  • [ ] Once approved, remove the "Guide: Leadership Review" label and add the "Guide: ready publication" label

Resources/Instructions

• Guide for UX Survey Template
• UX Survey Template
• How to Peer Review a Guide
• How to Format a Guide

Types of survey tools

Qualtrics Google Forms Survey Monkey Alchemer Wufoo Surveytown Typeform

Projects to check

• 100 Automations
• 311 Data https://github.com/hackforla/311-data/issues/534#issuecomment-612537629
• Access the Data https://github.com/hackforla/access-the-data/issues/76#issue-1005012320
• BallotNav https://github.com/hackforla/ballotnav/issues/483#issuecomment-1157218843
• Brigade Organizer's Playbook
• Civic Tech Index
• Civic Tech Jobs
• Civic Tech Structure
• Data Science Projects https://github.com/hackforla/data-science/issues/26#issue-817029328
• Design Systems https://github.com/hackforla/design-systems/issues/350#issue-1140360855 https://docs.google.com/document/d/1zuFgBkTl_4RzNJbCZvIXVWoj5z6RMOOQwFPRP-PUNQI/edit#heading=h.yzbdwdi6y59j
• Engage
• Expunge-Assist (formerly known as Record Clearance) https://github.com/hackforla/expunge-assist/issues/603#issue-1291747812
• Food Oasis
• GreenEarthOS
• Guides
• HomeUniteUs
• Internship project https://github.com/hackforla/internship/issues/258 https://docs.google.com/forms/d/e/1FAIpQLSdNByzgUK19HlWSmdyuegaMwHrVGTe4d1Phq0pJZ9DCtjs-sw/viewform https://docs.google.com/forms/d/e/1FAIpQLSe7ayBv9P6_cihKzgoMM6UO7uoCaPytaCICTKQ-cbTeAk7eNQ/viewform https://docs.google.com/forms/d/e/1FAIpQLSe1iAi5xpOW5EXyAAKHbjdDUt_scR02Oy0bkiligSyuQEi1dw/viewform
• Lucky Parking
• Open Community Survey
  • Community-Survey-empowerment-website
• TDM Calculator https://github.com/hackforla/tdm-calculator/issues/725#issue-791706996 https://docs.google.com/document/d/173GcghrnybVhPHx5eQySVpuSwN_DSGg1i-DEca4HFYw/edit
• VRMS
• Hack for LA's Website
• Youth Justice Nav https://github.com/hackforla/YouthJusticeNav/issues/89#issue-1335360825 https://docs.google.com/forms/d/e/1FAIpQLSdQRjqLDg_qVgOdebCK3B4V06jbLm5hh6g4oajFnORGpm4YnA/viewform

[bdavis73]

Here is a resource that might be helpful as you create this guide on surveys. https://dps.mn.gov/divisions/ojp/forms-documents/Documents/Wilder_Program_Evaluation_10.pdf Although this document is written for program evaluators, the information is applicable to survey development in any context. You may have to copy and paste the link to get it to work (sorry).

[yumengluo]

https://docs.google.com/document/d/1XOneRY3o29sgtSUJNn0PoloOQdB_rFOi/edit I compiled a bunch of online sources together in this file. I am not sure this is what the team is looking for. I would like to have more clear instructions for creating a survey template.

[daniellex0]

Added @bdavis73 as reviewer

[ExperimentsInHonesty]

@yumengluo checking in with you. Do you still want to work on this guide and if you do, what resources do you need to move forward?

[yumengluo]

@yumengluo checking in with you. Do you still want to work on this guide and if you do, what resources do you need to move forward? Hi Bonnie, I think I will not work on this guide anymore.

[carolzjy]

The template doc is a mix of guide and template. The guide portion also doesn't align with the HfLA guide format. The next step is to divide the doc into 2 separate files, and create a guide that is consistent with the standard.

[ExperimentsInHonesty]

This guide should also have a reference to another guide which is

How to choose a survey platform for your surveys/user testing which will include Advantages and limitations of each platform Examples from projects that have used it

[bkobak33]

To start making this guide, I studied each project under "Projects to Check" through their Github links and searched their Issues to find any relevant discussion of surveys or survey templates. If I did, I copied the link to that relevant Issue in the "Projects to Check" section. I will include Google Doc links for actual templates once I gain access to relevant projects. This was already done for the Open Community Survey and TDM calculator.

[bkobak33]

I contacted the following projects for survey templates: Access the Data, Data Science, Expunge Assist, Internship, Youth Justice Nav, and Design System. TDM calculator already had a link to a survey template with google docs. After a week of communication, I was able to add links to survey templates with the Internship program and Youth Justice Nav.

[bkobak33]

4 projects responded with specific Google Doc links: Internship, TDM Calculator, Youth Justice Nav, and Design System. For the remainder of projects, I will leave a link to potentially relevant Github issue.

[bradyse]

@bkobak33 Great work on this guide. If you are comfortable with posting in the UI/UX Slack channel requesting a peer-review from others, that would also be a great way to get your guide reviewed. If no one ends up reviewing it within the next week or so, then one of the CoP co-leads can review it and you can remove the "Needs Peer Review" label and add the "Leadership Review" label.

[bkobak33]

Thank you! I will do exactly that, appreciate you clarifying the next steps

[bkobak33]

Reviewers from the UI/UX CoP chose to provide comments and communicate through the Google Doc itself (instead of here on Github). Anastasiia Svyrydova, Kelene Lee, Samantha Hyler, and Richard Weinert all provided feedback on the document after an announcement circulated on the ui/ux Slack channel. Specific issues had to do with body text font choice, examples used to illustrate good survey questions vs. bad survey questions, details about the Likert scale, as well as risks to consider before sending out a survey.

I also discovered a template to making a guide for HfLA so I tried to change some titles and formatting to reflect that. https://docs.google.com/document/d/1-8gmeC-wnfM8C8fVvmTP1BLA2WfNjKH_XJrHB1OAV6Q/edit#heading=h.7nt92ljmyii5

[bkobak33]

Tyler Toldeo also left comments on the survey template itself in terms of giving participants a sense of time the survey will take and how to communicate rating scales in the questions.

[bkobak33]

Zhao Ding added suggestion to Google Doc to link to Qualtrics as an online survey method tool

[juliagab56]

We need a status update. Does this guide still need leadership review or is it completed?

[ExperimentsInHonesty]

@bkobak33 Please provide update

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 or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."

• remember to add links to the top of the issue if they are going to be needed again.