Modify the Solution Validation process
As Product Designers and Product Design Managers shift to take on more responsibility for Solution Validation efforts, it'll help to have the process updated in the handbook. After a review of the existing process outlined in the Product Development Workflow and the UX Research pages, I've distilled it down to the following steps...
- Determine if solution validation is needed. Note: Solution validation is only needed after designs or solutions have been proposed. If we lack confidence in a specific direction or if there is a high risk in moving forward without user validation, then continue with these steps.
- PD creates a new issue using the
Solution validation
template in the GitLab project. (automatically assigns ~”workflow::solution validation” label.) Link the Opportunity Canvas and design-related issues. Assign the new issue to yourself, PM, and the PD Manager. - PM and PD meet to discuss user recruitment needs and to clarify the research study's goals and hypotheses. Once a draft is complete, the PD Manager reviews and provides feedback.
- PD begins crafting a screening survey in Qualtrics. Note: It's important that the screening survey is completed in a timely manner so that user recruitment can quickly begin. In most cases, user recruitment should begin before the usability testing script is complete.
- PD creates a
recruitment request
issue in the GitLab Research project using the available issue template. Assign it to the relevant Research Coordinator. - The Research Coordinator will perform a sense check to make sure your screener will catch the people you’ve identified as your target participants. If there are multiple rounds of review, the Coordinator will pause activities until the uncertainty about your screening criteria has been resolved.
- PD drafts the usability testing script in collaboration with the PM. When a first draft of the script is complete, the PD Manager reviews and provides feedback.
- PD prepares the testing environment. This will likely be a clickthrough wireframe or prototype (low or high-fidelity screenshots, or an interactive UI prototype). Note: Design reviews should happen prior to preparing for testing. Make sure solutions are viable and include feedback from PM and Engineering.
- The PD is responsible for forwarding usability testing invites to the UX Research calendar. (
gitlab.com_kieqv96j35mpt8bdkcbriu2qbg@group.calendar.google.com
) and any other interested parties (PDs, PMs, Engineers, etc). - PD is responsible for leading (moderating) the usability testing sessions. PM should observe research sessions and take note of insights and pain points. Recommendation: Leave some time between your initial and second usability testing session. Use your first testing session as an opportunity to test your script and make amendments if necessary. All remaining participants (4+ participants) should receive the same testing script, or you will struggle to analyze and draw conclusions from the data you have collected.
- After the usability testing sessions are concluded, the PD updates the
Recruitment request
issue in the UX Research project. The Research Coordinator will reimburse participants for their time (payment occurs on Tuesdays and Thursdays). - PM and PD work collaboratively to synthesize the data and identify trends, resulting in findings.
- PD Manager reviews findings and provides feedback if needed.
- PD creates issues in the UXR_Insights project documenting the findings. Please refer to the project's ReadMe and
Usability testing insight
template for instructions on how to do this. - PD updates the Solution validation issue with links to findings in the UXR_Insights project.
- PM updates the opportunity canvas with the synthesized feedback.
- The PM articulates success metrics for each opportunity and ensures a plan for product instrumentation and dashboarding are in place.
At this point, we should have a clear direction on how to move forward. If the solution is validated, then the issue is ready to enter the build track. If the solution was not validated, revisit and make appropriate adjustments.
Things to do/update:
-
Create an MR to change the Product Development process (solution validation section). -
MR to correct formatting issues
-
-
Propose an update to the Recruitment request
template to include an example and handbook instructions to help others. -
Propose an update the the UX Research handbook (solution validation section) to avoid duplication. -
Create a new issue to discuss unmoderated research (out of scope for this issue). -
Create a solution validation
template and include it automatically applying appropriate labels.
@gitlab-com/gitlab-ux/managers - Please review and provide feedback.
Edited by Valerie Karnes