Commit 40bf4106 authored by Valerie Karnes's avatar Valerie Karnes 💬

Merge branch 'TN-experience-baseline-update' into 'master'

Updating the language on the Experience Baseline steps

See merge request !22975
parents 8647f1c4 a50c162e
Pipeline #62685967 passed with stages
in 23 minutes and 7 seconds
......@@ -8,11 +8,16 @@ As UX practitioners, we must think strategically about fixing usability challeng
Creating an Experience Baseline with associated Recommendations enables us to *identify, scope, and track* the effort of addressing usability concerns within a specific workflow. When it's complete, we have the information required to collaborate with Product Managers on grouping fixes into meaningful iterations and prioritizing UX-related issues.
### Initial Setup
1. Create a main stage group Epic (e.g. "Experience Baselines and Recommendations: {{Stage Group}} OKR Q2")
2. Create two related sub-epics for **Part 1: Experience Baseline** and **Part 2: Experience Recommendations**
### Part 1: Experience Baseline
1. Work with your Product Manager to identify the top 3-5 tasks (in frequency or importance) for users of your stage group. Ideally, you will base this task list on user research (analytics or qualitative findings).
1. Write each task as a "Job to Be Done" (JTBD) using the standard format: When (situation), I want to (motivation), so I can (expected outcome).
1. Create an epic for each JTBD.
1. Create an issue for each JTBD and include them in the **Part 1: Experience Baseline** sub-epic.
1. Document the current experience of the JTBD, as if you are the user. Capture the screens and jot down observations. Also, apply the following **Emotional Grading Scale** to document how a user likely feels at each step of the workflow. Add this documentation to the epic's description.
- **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*
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment