Problem definition

Value proposition
Blame is a heavily used feature (data baseline would be good here) that customers frequently mention or have feedback on. Fixing the below user problems will help to get our blame to parity with industry standards and improve our blame UX.

User problems
It's difficult to understand when blame is associated to multiple lines of code.
It's not apparent at first glance what blame is most relevant and/or recent to me.
The current blame has poor scannability between the blame components: datestamp, user name, and blame text.
The blame column is too narrow and cuts off most of the blame text and requires the hover to understand the blame.

Measure of success
TBA

Design process

• Estimate: One day to a week
• Weighting factors:
  • Note: Medium risk, High clarity

Discover

• Existing customer feedback - Link
• Engineering provided feedback in Code exploration brainstorming doc, and Slack thread on recency colors

Define

• Github issue
• Design challenge (defined in issue)

Design

• High fidelity design using design system - Figma
• Non-visual design guidance captured in the issue
• Designer review

Testing

• Hallway testing - Link
• Usertesting.com task based evaluation - Link

Deliver

• Loom - Link
• Team review
• Design team review
• QA - Link

Measure

• Metrics defined in the Figma file (i) - Link
• Followup task will analyze metrics to ensure successful completion - Link

/cc @felixfbecker