Design Handoffs/Review - Solution Validation

What's this issue all about?

After a round of internal research (#609 (closed)), we created and reviewed an Opportunity Canvas related to challenges in design handoffs and review in GitLab.

These interviews resulted in the following MVC feature proposals:

  1. ❌ Did not validate - Designs in Browser Extension: gitlab#199760 (closed)
  2. ✅ Validated - Designs in the MR: gitlab#199758 (closed)
  3. Needs more research - Designs in the Review App: gitlab#198092 (closed)
  4. ✅ Validated -Designers attach comments to DOM elements in the Review App - Visual review feature: gitlab#216148 (closed)

What are the overarching goals for the research?

Evaluate feature proposal(s) and understand challenges/opportunities associated with each proposal.

What hypotheses and/or assumptions do you have?

  • Challenges are finding Design users as we don't have as many users yet. Also differentiating between types of Designers in screening.
Core questions
  • Browser MVC: Do Designers what pixel perfect inspection?
  • MR MVC: Do Designers want to see their Designs in the MR?
  • Review App MVC: Do Designers want to see their Designs in the Review App?
  • Visual Review with DOM: Do Designers want to attach MR comments to DOM elements?
Additional questions
  • Get a feel for the workflows of our users
  • Validate the bigger concept of having Designers use other stages and it be useful for them

What persona, persona segment, or customer type experiences the problem most acutely?

  • Product Designer (more high fidelity handoffs)
  • Frontend Engineer
  • Product Manager

What business decisions will be made based on this information?

  • We may look at investing in or acquiring code that solves these needs

What, if any, prior research have you done?

What timescales do you have in mind for the research?

  • End of 2020, Q2

Who will be leading the research?

What is the link to your prototype/design artifact?

  • Each individual issue has their links and the designs are on the design tab.

Progress Checklist

  • Christen, Matt: Discuss MVC proposals and choose a solution to test.
    • Identify target users for testing
  • Matt: Finalize designs or prototype
  • Katherine: Schedule participants
    • Session 1: 8:30am PST
    • Session 2: 10:00am PST
    • Session 3: 10:30am PST
    • Session 4: 11:00am PST
    • Session 5: 12:00pm PST
  • Matt: Create script for usability testing based on prototype
  • Matt, Christen: Conduct usability testing sessions
  • Matt, Katherine: Analyze notes and synthesize findings
  • Matt: Document insights as issues in the Insights Repository

Links

Edited by Christen Dybenko