Skip to content

[2019Q2] UX Scorecard - Understanding dependencies

OKR Job to be Done

When creating a task (Task C) within a larger list of tasks that need to be completed to deliver a feature, I want to identify and document the dependencies for Task C (what tasks or subtasks need to be completed before Task C can be worked on, what tasks or subtasks are blocked by Task C, and how they relate to each other), so that I can prioritize Task C appropriately and help the assignee of Task C understand how their deliverables support the next task in the sequence as well as where their work falls in the completion of the larger project scope or feature.

Note here: task doesn't have to literally be a task, it can be any chunk of work (epic, issue, task, something else?) I just didn't want to be prescriptive. IE: For Parker: When creating an issue within an Epic that contains other issues, I want to identify and document in this issue what issues or tasks my new issue is blocking, and what issues or tasks are being blocked by my issue (how they relate to each other), so that I can prioritize this new issue appropriately and help the assignee of it understand how their deliverables support the next task in the sequence as well as where their work falls in the completion of the larger project scope or feature.

Research Findings ### Research Findings ###### Larger JTBDs for just for context (not to be documented): **Parker’s Job:** When creating and refining my backlog, I want to understand the relationship and dependencies between Epics, Issues, and Tasks so that I can better prioritize work within my backlog and estimate when an entire feature may be delivered in a more mature state (ability to do rollups of issues to get status on a much larger 'application), understand the scope of what has already been completed, and be confident communicating this with stakeholders and customers.

Delaney’s Job: When I am working on an Issue that has dependencies, I want to understand where my Issue falls within these dependencies and what the relationships are, so I can contribute toward and understand the overall vision of what our team is delivering and be a collaborator instead of blocker to the next iteration of work that depends on my Issue being completed and handed off successfully.

Tasks

  1. If your JTBD spans more than one stage group, that’s great! Review your JTBD with a designer from that stage group for accuracy.
  2. Document the current experience of the JTBD, as if you are the user. Capture the screens and jot down observations. Also, apply the Emotional Grading Scale below to document how a user likely feels at each step of the workflow.
  3. Use the Grading Rubric below to provide an overall measurement that becomes the Benchmark Score for the experience.
  4. Once you’re clear about the user’s path, create a clickthrough video that walks through the experience and includes narration of the Emotional Grading Scale and Benchmark Score.
  5. Post your video to the GitLab Unfiltered YouTube channel, and link to it above.
  6. Create an issue to revisit the same JTBD the following quarter to see if we have made improvements. We will use the grades to monitor progress toward improving the overall quality of our user experience. Add that issue as related to this issue.

Emotional Grading Scale

Expand/collapse scale
  • 🎉 Positive: The user’s experience included a pleasant surprise—something they were not expecting to see. The user enjoyed the experience on the screen and could complete the task, effortlessly moving forward without having to stop and reassess their workflow. Emotion(s): Happy, Motivated, Possibly Surprised
  • 😐 Neutral: The user’s expectations were met. Each action provided the basic expected response from the UI, so that the user could complete the task and move forward. Emotion(s): Indifferent
  • 😠 Negative: The user did not receive the results they were expecting. There may be bugs, roadblocks, or confusion about what to click on that prevents the user from completing the task. Maybe they even needed to find an alternative method to achieve their goal. Emotion(s): Angry, Frustrated, Confused, Annoyed

Grading Rubric

Expand/collapse rubric

A (High Quality/Exceeds): Workflow is smooth and painless. Clear path to reach goal. Creates “Wow” moments due to the process being so easy. User would not hesitate to go through the process again.

  • Frustration: Minimal to none
  • Task Completion: Successful
  • Steps to Accomplish Task: Minimal

B (Meets Expectations) Workflow meets expectations but does not exceed user needs. User is able to reach the goal and complete the task. Less likely to abandon.

  • Frustration: Low
  • Task Completion: Successful
  • Steps to Complete Task: Minimal

C (Average) Workflow needs improvement, but user can still finish completing the task. It usually takes longer to complete the task than it should. User may abandon the process or try again later.

  • Frustration: Medium
  • Task Completion: Successful but with unnecessary steps
  • Steps to Complete Task: Average complexity

D (Presentable) Workflow has clear issues and should have not gone into production without more thought and testing. User may or may not be able to complete the task. High risk of abandonment.

  • Frustration: High
  • Task Completion: Unlikely, but there may be a chance that there is completion
  • Steps to Complete Task: Excessive

F (Poor) Workflow leaves user confused and with no direction of where to go next. Can sometimes cause the user to go around in circles or reach a dead end. Very high risk of abandonment, and user will most likely seek other methods to complete the task.

  • Frustration: Very High
  • Task Completion: Very Unlikely
  • Steps to Complete Task: Lacking

Current experience

Grade: C (Average) Workflow needs improvement, but user can still finish completing the task. It usually takes longer to complete the task than it should. User may abandon the process or try again later.

  • Frustration: Medium
  • Task Completion: Successful but with unnecessary steps
  • Steps to Complete Task: Average complexity

Experience walkthrough: https://www.youtube.com/watch?v=XyEf0E1e8ns

1. View epic and attached issues

Step Screenshot Emotional grade
I navigate to the epic my team has been working on Screen_Shot_2019-07-02_at_11.43.54_AM 🎉 I see all the issues that comprise this epic, along with the sidebar metadata

2. Creating a new issue

Step Screenshot Emotional grade
I need to create a new issue in this epic, so I navigate to the + button on the Issues widget Screen_Shot_2019-07-02_at_11.44.06_AM 😠 I don't have an existing issue; I want to create a brand new one
Step Screenshot Emotional grade
I'll use the + button on the nav. I've created new issues that way before Screen_Shot_2019-07-02_at_11.44.18_AM 😠 I can't create an issue from here either
Step Screenshot Emotional grade
I guess I'll try via the side nav Screen_Shot_2019-07-02_at_11.44.35_AM
Step Screenshot Emotional grade
More clicks to get where I need to be Screen_Shot_2019-07-02_at_11.45.03_AM 😠
Step Screenshot Emotional grade
Hooray! I was finally able to create a brand new issue Screen_Shot_2019-07-02_at_11.45.17_AM 😐 This form is pretty standard; nothing unexpected
Step Screenshot Emotional grade
I clicked save, and can now see my newly created issue Screen_Shot_2019-07-02_at_11.45.49_AM 😐 This is the content I expected to see

3. Attaching issue to epic

Step Screenshot Emotional grade
Now I need to attach this issue to my epic. I look at the sidebar where I can edit all the metadata. I see Edit next to every component except Epic Screen_Shot_2019-07-02_at_11.46.07_AM 😠 Extremely frustrated. I guess I need to use that paste URL option from Step 2, but I didn't keep a tab open with the epic. Now I need to go locate it agian
Step Screenshot Emotional grade
I find my epic again, and use Add issue button to paste in my issue URL Screen_Shot_2019-07-02_at_11.46.40_AM 😐 I was expecting this, although it's still not an ideal experience
Step Screenshot Emotional grade
There's my new issue, right at the top! Screen_Shot_2019-07-02_at_11.47.08_AM 😐 I was expecting this

3. Reordering issues

Step Screenshot Emotional grade
This issue needs more thought, UX, and dev input. I should move it to the bottom of the open issues Screen_Shot_2019-07-02_at_11.47.25_AM 🎉 I love that I can order them in whatever way I want. In this case, I have the closed issues at the bottom, and the others ordered by importance

4. Establishing a hierarchy & dependencies

Step Screenshot Emotional grade
I click on the issue I just created, and now I can see that the epic name is displayed in the issue sidebar Screen_Shot_2019-07-02_at_11.48.16_AM 😐 I was expecting this
Step Screenshot Emotional grade
This issue is dependent on another issue within the epic, so I'd like that to be known. I don't see a Dependency or blocking issues option, so I'll just use Related issues Screen_Shot_2019-07-02_at_11.48.56_AM 😠 Related issues is a nice feature, but it doesn't really solve for blocking issues. Also- the same pattern with pasting in the URL. I'd need to go searching for my issues in a separate tab
Step Screenshot Emotional grade
I go back to the epic, and look at the sidebar to see all the parent epics Screen_Shot_2019-07-02_at_11.52.47_AM 😠 Why is the top level epic closed? Not sure that makes sense. Surely if there are still open epics and issues within it, it should remain open?
Step Screenshot Emotional grade
I click on the immediate parent of my epic to see how related epics are coming along Screen_Shot_2019-07-02_at_11.53.06_AM 😠 I can't see how many issues and epics are nested within these two epics, making it difficult to plan the next few milestones
Edited by Valerie Karnes