UX Scorecard - Compliance FY22-Q3 - Create audit deliverables
- Job statement: When I am preparing for an audit, I want to create shareable deliverables, so that I can provide evidence of compliance.
- Personas: Cameron (Compliance Manager)
- Scenario: There is an upcoming audit for SOX that you are responsible for passing. As it relates to your self-managed instance of GitLab, you need to create artifacts that can be shared with the auditor you'll be meeting with at the end of the quarter. For this audit, they will be looking for a few things (1) users that have been added and removed to relevant projects and their permissions (2) any failure to maintain separation of duties, and if there are, what were they.
- Setup instructions: Use this GitPod snapshot and login with the credentials sent to you over Slack.
- Previous score and scorecard: N/A
- Benchmark score: N/A
- Walkthrough video: {{add link to YouTube video}}
- Walkthrough deck: {{add link to deck used in Youtube video if applicable. This step is optional and we encourage you to skip this unless it helps you to communicate your findings}}
- Recommendations: {{add link to your recommendation issue/s}}
Heuristic Buddy UX Scorecard Checklist
The Heuristic Buddy UX Scorecards are a twist on our UX Scorecard process. These are specifically designed to help identify areas of usability and learnability improvements. They are to be completed by a designer who does not work within the same product area(s) the job can be completed in. Learn more about UX Scorecards
The initial preparation is completed by the Group Product Designer (groupcompliance @aregnery). When the preparation has been completed they will hand it over to the Heuristic Buddy (@dfosco) to complete the evaluation who will hand it back to the Group Product Designer when completed to add any recommendations. Read through the steps below for details.
@aregnery) - Due date 2021-08-20
Group Product Designer (Click to expand
-
Add this issue to the stage group epic for the corresponding UX scorecards. Verify that the "UX scorecard" label is applied. -
After working with your PM to identify a top job, write it using the Job to be Done (JTBD) format: When [situation], I want to [motivation], so I can [expected outcome]
. Review with your manager to ensure your JTBD is written at the appropriate level. Remember, a JTBD is not a user story, it should not directly reference a solution and should be tool agnostic. -
Make note of which personas might be performing the job, and link to them from this issue's description. Keeping personas in mind allows us to make the best decisions to address specific problems and pain points. Note: Do not include a persona in your JTBD format, as multiple types of users may complete the same job. - [-] If your JTBD spans more than one stage group, that’s great! Review your JTBD with a designer from that stage group for accuracy. Note: This stage group's designer cannot be your Heuristic Buddy.
- [-] Consider whether you need to include additional scenarios related to onboarding.
-
Ping your Heuristic Buddy and let them know it's ready for them to conduct the evaluation.
@dfosco) - Due date 2021-09-17
Heuristic Buddy (Click to expand
-
Review the current experience, noting where you expect a user's high and low points to be based on our UX Heuristics. Using an experience map, such as the one found in this template, capture the screens and jot down observations. - During the evaluation strive to wear the hat of the persona relevant to the JTBD and while doing so try to see the UI from their perspective as if they were a new user.
- As you progress through your evaluation this will be easy to forget so it's recommended to put a reminder somewhere in your view, such as a post-it stuck on your monitor that says "You're a new user!"
-
Use the Grading Rubric to provide an overall measurement that becomes the Benchmark score for the experience (one grade per JTBD), and add it to this issue's description. Document the score in the UX Scorecard Spreadsheet (fixed). -
Once testing is complete, create a walkthrough video that documents what you experienced when completing the job in GitLab. Begin the video with a contextual introduction including: - Your role, stage group
- Specify how you conducted the heuristic evaluation
- Add a short introduction describing the JTBD and the purpose of the UX scorecard (i.e. you're performing the evaluation in partnership with {stage group} and {product designer}.
- This is not a "how-to" video, but instead should help build empathy for users by clearly showing areas of potential frustration and confusion. (You can point out where the experience is positive, too.)
- At the end of the video, make sure to include narration of the Benchmark Score. Examples here and here.
- The walkthrough video shouldn't take you long to create. Don't worry about it being polished or perfect, it's more important to be informative.
-
Post your video to the GitLab Unfiltered YouTube channel, and link to it from this issue's description. -
Link to your video in the Engineering Week in Review (fixed). -
Once the evaluation has been completed ping the Stage Group Product Designer in this issue letting them know it's ready for their review.
@aregnery) - Due date 2021-10-15
Group Product Designer (Click to expand
-
Create a recommendation issue for this JTBD and add it to the same stage group epic as this issue. - Add a link to your recommendation issue(s) to this issue.
Edited by Austin Regnery