Repository navigation
Make the pilot feedback form fit a lab that has not collected yet - #16
Merged
Merged
Conversation
The form assumed the person filling it in had an archive. It asked how long the task would normally have taken, which has no answer when there was no previous way of doing it, and whether they trusted it with their data, which has no answer when there is not any yet. Half the people being invited to test would have been answering questions about a situation they were not in. It now opens by asking which situation they were in, marks the timing question skippable, and offers "no data at risk" as an answer to the trust question. It also asks the question that matters most from someone starting fresh and which nothing was asking: whether the structure fits how their lab actually works -- their modality, their acquisition software, the way they already think about subjects and sessions. Somewhere it does not fit is worth more than somewhere it does, and the form says so, because a lab convention that disagrees with the standard for a good reason is how the standard improves.
This file contains hidden or 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.
The feedback form assumed the person filling it in had an archive.
It asked how long the task would normally have taken — no answer when there was no previous way of doing it. And whether they trusted it with their data — no answer when there isn't any yet.
Half the people being invited to test would have been answering questions about a situation they were not in.
Changes
And one new question
Nothing was asking the thing that matters most from someone starting fresh: does the structure fit how your lab actually works? Your modality, your acquisition software, the way you already think about subjects and sessions.
The form says explicitly that somewhere it doesn't fit is worth more than somewhere it does — a lab convention that disagrees with the standard for a good reason is how the standard improves.
319 tests, unchanged.