Brand Design Template: Extra Large

  • Estimate: More than a month

  • Notes:

    • When creating the issue, use the label design-estimated-XL
    • All phases for this project should involve a higher level of fidelity. Examples include additional test participants, multiple versions of designs, and more revision, and refinement than designs for smaller projects.
    • 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: More than a month
  - Weighting factors:
    - Note: a project of this size requires resources that increase its risk profile.
    - [HIGH|MEDIUM] risk
    - [HIGH|MEDIUM|LOW] clarity

  ### Discover
  Extra large projects should entail more comprehensive research efforts.
  -[ ] Contribute to project brief (owned by PM) in the following areas:
    -[ ] Constraints (what we can't do)
    -[ ] Deliverables (site nav, mood board, content strategy)
    -[ ] Timeline
    -[ ] Distribution channels
    -[ ] Resources
    -[ ] Relevant feedback including user testing results
    -[ ] Analogous/competitive research - Link

  ### Define
  -[ ] Creative direction via moodboard and/or half-page conceptual mocks
    -[ ] Stakeholder review
  -[ ] GitHub issue

  ### Design
  -[ ] Site architecture/User journey
    -[ ] Review with stakeholders
  -[ ] Wireframes
	  -[ ] Review with stakeholders
    -[ ] Designer review
  -[ ] Half-page conceptual mocks (if not already completed)
    -[ ] Review with stakeholders
    -[ ] Designer review
  -[ ] Complete desktop mockups based on initial concepts
    -[ ] Review with stakeholders
    -[ ] Designer review
  -[ ] Mobile mockups
  -[ ] Prototype - Link
    -[ ] Review with stakeholders

  ### Testing
Testing should use the prototypes
  -[ ] Hallway testing - Link
  -[ ] Usertesting.com task-based evaluation - Link

### Building
Building should use the prototypes
  -[ ] Loom
  -[ ] Meeting with implementation team for review
  -[ ] Github issue
	  -[ ] Prototype
	  -[ ] Design assets
	  -[ ] Form code
	  -[ ] New URLs
	  -[ ] Meta information
  -[ ] QA (PR + preview)
	  -[ ] Test accross browsers
	  -[ ] Test on different screen sizes
	  -[ ] Test links

--

  ### Deliver
  - [ ] Announce in #progress
    - Consider announcing in a company meeting
  - [ ] 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

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