Package Jobs To Be Done (JTBD) research
What’s this issue all about?
The Package stage group has been grooming the Jobs To Be Done (JTBD) we're using to determine the product roadmap. 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 package offering.
Who is the target user of the feature?
Engineers, DevOps, and SysAdmins. A technical buyer persona might also benefit if we better understand what could be blocking that process.
What questions are you trying to answer?
Core questions
"Which of these JTBD/stories are necessary for you to replace your third-party package manager (like Artifactory)?"
Additional questions
- Are the Jobs listed all of the jobs that apply to a Package Offering for our users?
- 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.
When do you need this research to be completed? (Milestone or date)
12.8 - This research may be extended into a follow up research initiative in 12.9