Skip to content

WIP: Update PA JTBDs to align with the JTBDs framework and move the user stories to a new page

Nadia Sotnikova requested to merge nadia_sotnikova-master-patch-26666 into master

Why is this change being made?

Currently the documented PA JTBDs don't align with the JTBDs framework.

  • The JTBDs are too granular and aren't product agnostic. A JTBD needs to focus on the Job and the Motivation for that Job rather than a specific solution.
  • We’re meant to have 1-2 main JTBDs for the Pipeline Authoring product category. We have too many, and this MR boils them down to 3.

According to the JTBDs docs:

JTBDs are a chance to step back from your business and understand the objectives of the people you serve. To innovate, don’t ask customers about their preferences, but instead understand their underlying needs and motivations.

I propose to strip down our JTBDs list and start building it up from a clean slate, so we can focus on the underlying customer needs and create some space to innovate with our solutions.

The new JTBDs focus on the core jobs and motivations of our users while being solution agnostic and taking two different job executor types into consideration.

The user stories can be documented in a separate page which will be cross-linked in the PA category page, the JTBDs page, and UX direction pages. We can also link it in the PA Group page, and any PA engineers docs page where it'd be relevant.

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.
Edited by Nadia Sotnikova

Merge request reports