Verify:Testing - Usability Testing JTBD Research

What’s this issue all about?

The Verify:Testing group has been grooming the Jobs To Be Done (JTBD) for the Web Performance Testing Category. The next step is to connect with our users to understand what JTBD they would prioritize. Our plan is to gather data around what JTBD would be required to migrate to Gitlab's Web Performance Testing category to the Viable Maturity.

Who is the target user of the feature?

Developers - Writing code daily that some other person (developer, product manager, designer) needs to review before merging to the default branch.
Product manager / Designer - Review changes from developers prior to a feature being merged/shipped to ensure functionality / look and feel match what was intended.

What questions are you trying to answer?

Core questions

"Which of these JTBD/stories are necessary for you to be confident you know all feedback about the implementation was collected."

Additional questions

Are the Jobs listed all of the jobs that apply to usability testing a developer can do?
Which of the JTBD would you say directly impacts the users day to day work?
Which of the JTBD would have the lowest impact on the users day-to-day?
How do users perceive the maturity of their most important JTBD at GitLab? (interesting comparison could be between current GitLab and Non-GitLab users)
Of the JTBD the user rated as highly impactful, what improvements or features would they expect/desire a solution to offer?

What hypotheses and/or assumptions do you have?

Some of the JTBD will consistently be ranked as important while others are unimpactful. There will also be more consistency in responses when user types are compared independently.
There might be some JTBD that are important or relevant to our users that we have missed.

What decisions will you make based on the research findings?

What JTBD will be focused on next in priority for research, design, and product development.
What JTBD will be getting user based UX Scorecards.