Strategic/Foundational UXR Work

In a recent GC, the UXR team shared that they have allocated 30% of their bandwidth for Foundational/Strategic work. This is a great opportunity to understand in new and meaningful ways what our users want. I wanted to encourage each PM director to work with their stable counterparts and identify what that work would/could be.

• Ops
  • Adoption Journeys
• Dev
  • Code review workflows
    • Related topic: Simplifying the editing experience in GitLab
• Secure & Defend
  • Secure: Help organizations elevate DevSecOps Maturity
• Enablement
  • [No plan, as there is no staffing to the best of what I understand]

changed the description

cc: @kencjohnston @ebrinkman @david @joshlambert @asmolinski2

changed due date to August 25, 2020

@adawar Dev has no stable counterpart in UX research at this moment.

@ebrinkman - You still have Katherine. We'll work to backfill your additional researcher position ASAP.

@clenneville thanks for the clarification. I should have written Manage and Plan don't have a stable counterpart at this point in time.

cc: @clenneville FYI

@adawar - Thanks for opening this issue! One minor change: Lorie Whitaker is the UXR for Enablement.

Oh, and one more change: Jeff Crow is the UXR for Growth.

I thought Lorie is working on Adoption journey. @kencjohnston

Lorie and Andrzej both cover parts of Ops (they're collaborating on the CI Adoption Journey), and Lorie also covers Enablement.

@asmolinski2 @adawar - one thing that would help us if we updated something in the Product Category page including at the Section, Stage and Group level where appropriate.

https://about.gitlab.com/handbook/product/product-categories/

@kencjohnston Do you mean looking at that page for accuracy around which Researcher is covering which Section, Stage and Group level?

@asmolinski2 - Yes

@kencjohnston done, but we're working out a linking issue we're experiencing on that page.

@katokpara any thoughts on what this should be for Dev?

@ebrinkman The research proposal I'm currently working on for Create is about simplifying editing experiences in GitLab: gitlab-org&4146 (closed). The goal is to understand the use cases the Web IDE, single-file editor, and Static Site Editor all serve and evaluate the experience of navigating from the repo files to an editor to an MR.

Thinking about Manage & Plan, I'd say that more research around Projects/Groups, project management (especially Issue Boards), or permissions management would be beneficial based on feedback I tend to see in the SUS.

Do you have thoughts on what you'd find most useful?

@katokpara I would prioritize them in this way:

1. Code Review workflows
2. Projects/Groups
3. Permissions
4. Boards
5. Editing experiences

Since you're closest to Create, what do you think about shifting our UXR cycles to focusing on code review workflows?

@ebrinkman We do have a lot of insights from several exploratory and evaluative research studies related to code review:

• gitlab-org&1259 (closed)
• gitlab-org/ux-research#836 (closed)
• CMS https://gitlab.com/gitlab-org/ux-research/-/issues/941
• gitlab-org&2070 (closed)
• gitlab-org&2333 (closed)

So at this stage, my approach would be to first synthesize the findings from prior research, work with @danielgruesso to prioritize a list of actionable insights, and then further investigate any open research questions groupsource code may have.

The editing experiences topic overlaps with considerations around MR discussions in the Web IDE (gitlab-org&72, gitlab-org/gitlab#221068 (closed)), making file changes in MRs, and editing "in context" (gitlab-org&3601). So I think these work well together, with code review as the main focus.

I've added this to the issue description!

That's great, thanks @katokpara! Agree on the overlap and opportunity here. @phikai this would be good for you to stay involved with as well.

marked this issue as related to gitlab-org/gitlab#228957

@adawar and @clenneville - I reviewed this with @asmolinski2 and @tlavi in our last UXR sync up. I gave the "go ahead" on our first foundational project. I linked the associated issue and ask @tlavi to replace it with the correct one if I chose poorly.

/cc @matt_wilson (and @gl-sec-section-pms)

That's awesome, @david - thank you!

@adawar & @clenneville - I also added the link to the description. I'm going to check myself off as I don't think the is awareness and not completion of the project. Let me know if I am misunderstanding.

changed the description

changed the description

marked the checklist item Secure & Defend as completed

marked the checklist item Secure: Help organizations elevate DevSecOps Maturity as completed

changed the description

marked the checklist item Dev as completed

marked the checklist item Enablement as completed

Thank you team for a rapid and quick response. Closing this one out.

closed