Design Template: Large

Estimate: Two weeks to a month
Notes:
- When creating the issue, use the label design-estimated-L
- Ideally, design should be given sufficient time in the problem space to explore and research.
- Design should be happening at least one iteration before engineering is planned. If user testing is required before or after design, this should be factored into the design time.
- These efforts require close collaboration with the Product Manager to scope and define the user problems being solved.

✂️ -------------------------

## Design process

  - Estimate: Two weeks to a month
  - Weighting factors:
    - HIGH|MEDIUM|LOW risk
    - HIGH|MEDIUM|LOW clarity

  ### Discover
  - [ ] RFC
  - [ ] Existing customer feedback - Link
    - [ ] NPS scores
    - [ ] Feedback submissions
    - [ ] Customer support requests
  - [ ] Quantitative analysis - Link
  - [ ] Surveys - Link
  - [ ] Analogous / competitive research - Link
  - [ ] Internal users - Link
  - [ ] External users - Link, Link

  ### Define
  - [ ] Product document or RFC - Link
  - [ ] Design challenge - Link
  - [ ] Github issue

  ### Design
  - [ ] user journey map - Link
  - [ ] User flows - Link
  - [ ] Low fidelity design - Link
  - [ ] High fidelity design using design system - Figma
  - [ ] Prototype - Link
  - [ ] Designer review

  ### Testing
  - [ ] Hallway testing - Link
  - [ ] Usertesting.com task based evaluation - Link
  - [ ] User testing with 2 customers - Link

  ### Deliver
  - [ ] Announce in #progress
  - [ ] Loom - Link
  - [ ] Team review
  - [ ] Design team review
  - [ ] QA - Link

  ### Measure
  - [ ] Metrics defined in the Figma file ([i](https://handbook.sourcegraph.com/departments/product-engineering/product/design/metrics/defining-metrics/)) - Link
  - [ ] Followup task will analyze metrics to ensure successful completion - Link

✂️ -------------------------