Documenting research findings (UX research processes)
@tauriedavis @pedroms @dimitrieh @cperessini @hazelyang
I've now completed a few research studies for GitLab and I'm in the process of reviewing how things went. I feel there is a lot that could be improved upon and I'd really like your input. I've had a couple of conversations with a few of you (which have been really helpful, so thanks!) but I thought it would be good to have an issue where we can flesh things out a bit better. Ultimately, you are the people who are designing the solutions to users' problems so it's important that you are getting the answers you need from the research conducted.
Here are a couple of things which have been bouncing around my mind:
Documenting research findings
I appreciate that the meta research issue may too detailed - what information would you like to see in a meta issue? How would you like that information structured?
I'm not sure whether it's the best use of my time or helpful to you when I create multiple issues from the meta issue. There is some duplication happening (despite my best efforts searching for an issue), some seem to be falling through the cracks (no comments on them) and some are not considered important by the product owner (which is cool, unfortunately we can't always action everything and sometimes more evidence is required to support the prioritisation of the problem). Perhaps there needs to be more of a discussion about which findings are turned into issues? Does every finding necessarily need a separate issue? With better storage of research findings (see #22 (closed)), if we don't create an issue and then see repetition of that behaviour in future research studies, we should be able to easily find reference to the previous study and raise an issue to say "Hey this has happened more than once now, we need to do something!"
Storing research findings Moved to #22 (closed)
Communication of research findings Moved to #23 (closed)
I'd really love your thoughts/comments on any of the above. Please feel free to completely honest about what is/isn't working for you. Rough ideas are fine - I don't expect to get it right first time, we can keep working on this
Solution
Create a meta research issue in the UX research project
Encourage discussion within this issue about the research. Agree with UX designers and product owners what findings should be turned into issues.
Create new issues linked to the meta issue within the GitLab CE/EE project. Ensure the label UX research: done
is added to issues which are an outcome of the research.