Stacking questions in questionare and other format issues

[shapironick]

A repost of @novakn 's comment in #4 I can see your point about the repetitive survey questions--I am a little worried that distributing them throughout the survey could be confusing or could prime people to respond differently based on the other questions surrounding them. Another option (and I'm sorry if this is annoying since you have already made these questions) would be to ask about a few symptoms at a time (If you look at the Google survey you can see how they were divided into categories of 3 to 6 symptoms each-- fatigue/cognitive, respiratory, skin, other). We could ask the Yes(often), Yes(sometimes), No questions for one set of symptoms at a time, and then have a follow-up page that asks about their attribution to home environment only for the symptoms for which they said "Yes". Would this be ok? This is actually returning slightly to the format of the symptom survey ours is based on--I attached a screenshot.

[mmnoo]

More thoughts on this:

I have been thinking that that approach might not necessarily encourage people to complete the survey. It may help, but maybe not that significantly. Also, the cognitive break that would happen at the end of a question subset might also be a psychological invitation to leave the survey. It also would require a decent amount of extra coding, which I am happy to do, but given that hypothetical risk that it doent significantly reduce frustration from the survey process, it might not be worth the expense.

I wonder if we should focus our efforts instead on planning for the inevitable, that many people wont complete 30 questions + 34 potential follow up questions. I wouldnt answer all those questions, would you guys? I might answer 15 - 20 tops.

If we randomize the order we ask the questions in, would that data still be useful to the research? We would have lots of null values (which I hypothesize that we will have lots of regardless), but we will have answers for all of our questions, not just the ones that get asked at the beginning in order. If we have a big enough dataset, we could still pick out patterns statistically, no?

Or maybe we should ask less questions?

Or maybe we can offer some sort of incentive for fully completing the survey to get more comprehensive data?

(my recent comment in #18 was in response to my own misunderstanding, feel free to disregard it)

[mmnoo]

Also, randomizing the survey questions would be pretty easy, therfore cheaper for you guys.

[shapironick]

I think this is another issue that may have been closed accidentally.

Building out the survey is the big next step in terms of usability.

This involves two aspects. 1) filling out the rest of the sections and have them correspond to the dashboard. 2) create a related question/grid format for symptom lists that can be more easily and quickly used (ie fewer clicking next and waiting for page reloads). here is the link to the final survey list with page breaks and comments by both me and nicole embedded. https://docs.google.com/forms/d/1N6OV_E5AEHzcPEQZG1AfLBqaiqcsbHuUY5BNew75WK8/edit

The priority of this should be after you complete the security tasks. @novakn and I still need to do a final pass on the question list. If you get to this part of the workflow and you haven't seen us say its good to go just ping us on this threat. Thanks so much!

[shapironick]

@novakn do we want to add a section on Health Hardware? I think this is important to look at the extra-chemical structural impacts of housing on health. http://www.habitation.gouv.qc.ca/fileadmin/internet/centredoc/CC/NS23559.pdf