Research: Internal solution validation on MVC Security Widget redesign
What's this issue all about? (Background and context)
In gitlab#12896 (closed) we are proposing a semi-major structural change to how security features are interacted with in the Merge Request. We want to be sure that these changes generally align with user perception.
What are the overarching goals for the research?
Double-check assumptions before committing to a tech/ux investment
What hypotheses and/or assumptions do you have?
Users interacting with the security information in the new merge request experience will have:
- a) more clarity around the results
- b) an easier experience reviewing results and taking action
- c) an easier experience troubleshooting problems they may encounter
What research questions are you trying to answer?
- Are the changes we proposed desired improvements to the merge request experience?
- Are we meeting our users' expectations with the information that is being displayed?
What persona, persona segment, or customer type experiences the problem most acutely?
- MR Reviewers and Maintainers
- Developers
- Security specialists
What business decisions will be made based on this information?
To build or not to build, that is the question.
What, if any, relevant prior research already exists?
Who will be leading the research?
What timescales do you have in mind for the research?
Complete by the end of %13.2
Relevant links (script, prototype, notes, etc.)
Results
- The presentation of information has been validated
- The tabbed approach has been validated
Edited by Andy Volpe