Rewriting Usability Testing JTBDs
Why is this change being made?
As part of the UX KR to validate JTBDs to better support Category Maturity, I ran user interviews https://gitlab.com/gitlab-org/ux-research/-/issues/1557 regarding Usability Testing JTBDs, since there wasn't any existing research to validate the JTBDs with. Updating these JTBDs will prepare ~"Category::Usability Testing" to move from Minimal to Viable in 2022.
The main insights that these jobs were created around was from an underlying workflow that I found through the research:
1a & 1b. Assess what the change is about --> 2a. Examine attached screenshots or GIFs --> 2b. Pull the changes locally --> 3b. Make those changes appear --> 4b. Examine and test the updated workflow --> 3a & 5b. Communicate review of changes with MR author --> 4a & 6b. Determine if next steps are necessary
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.