Skip to content

Refine package JTBD

Katie Macoy requested to merge katiemacoy-master-patch-36265 into master

Why is this change being made?

This issue started from a UX KR. The KR was to write JTBD for features moving up in category maturity. Although the package registry will not move up in maturity until later in FY22, this is an opportunity to review package JTBD based on previous research.

The original package JTBD were informed by research, but are often focused on solution rather than customer intent focused:

Problem JTBD
Existing JTBD focus on GitLab rather than what our customers are trying to accomplish When my organization decides to move forward with GitLab’s Package offering, I need to efficiently plan and migrate my organization’s packages and images to GitLab’s Registries, so I can bring these resources into the single secure DevOps tool without causing disruption to my team.
Existing JTBD are about specific products When my organization is proxying/caching images and/or packages from external remotes, I need the Dependency Proxy to function seamlessly and reliably, so our developers have a consistently stable product development experience.
Existing JTBD focus on technology rather than why When my development organization changes and grows, I need an intuitive way to manage permissions related to the GitLab registries, so that I don't have to maintain multiple authentication systems or passing tokens between applications.

Methodology

Use findings from previous research to refine existing JTBD. Most JTBD were edited and some were added.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this change to the correct DRI(s)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports