Update survey design guidelines #105
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I reviewed survey design guidelines from the issue added by @reese-lee, articles that were already linked from the README page, as well as two more. In addition to that, I reviewed past community surveys and created my own list of observations. (I documented my notes in the proposal for transparency but we can consider deleting them) Based on that, I compiled a list of 15 simple guidelines that folks that create or review surveys to improve the quality of their surveys.
In this MR I didn't tackle improvements to survey creation or review process nor collaboration in the SIG on running surveys. I think it would be better to do this as separate MRs or in different issues.
Please review @reese-lee @avillela @danielgblanco
Resolves #85