[DRAFT] DORFD Design Issue Template Redesign

The following concept template was derived from discussions in this issue, this MR, and from this DoD.

Problem and Idea

❓ What's the problem as you see it now, and what's your idea to solve it?

Problem:

Idea:

Jobs to be Done

Job Performer

❓ Who will be using this?

Persona(s)

Main Job

❓ What are they trying to accomplish?

Outcome(s)

❓ How are they measuring the progression of accomplishment?

Outcome Statement Importance Satisfaction Overall Score

Business Objective

❓ What will the business get out of completing this work?

User Needs/Requirements/User Stories/Scenarios/Tasks

❓ What are the functional needs of the job performer and what solution we are building?

Foundational/Background Info

Product Hierarchy

❓ What level of GitLab will this project exist on? i.e., Instance, Namespace, Group, and/or Project

❓ Link to example page in GitLab and a screen capture of the area where this update/change is needed.

Tier

❓ What tier will this be available to users?

Product Roadmap Area Being Addressed

Supporting Resources

Technical Constraints

❓ What are any technical issues we need to be aware of or work around?

Research Links

❓ Provide all links to research that has been done to support this issue.

Other Related Work Links

❓ What else has already been done to move this project forward; competitive analysis, journey mapping, etc.

Ready For Design Checklist

  • Main Job has been validated.
  • Job Story(ies) is based on validated Job Canvas(es).
  • Outcome statements + scores have been added to measure success against.
  • Business Objective aligns with company goals.
  • User Stories and User Needs affectively define what this project needs to entail, allowing design to be done.
  • Delivery Timing and Technical Constraints are feasible, allowing design to be done.
  • Location this UI will reside (i.e. Product Hierarchy) is defined
  • The product Tier this UI will be accessible under is defined and user needs/requirements to align with this level are defined.
  • There is a High Confidence in understanding the overall Job Performer needs (derived from research or other data-gathering techniques).
    • If Medium or Low confidence, additional Problem Validation is necessary to progress to Design Phase.

Design Phase

  • Ready For Design checklist has been completed (all items checked)
  • Ideate and Iterate on High-level Vision
    • User flow diagram generated
    • Low-fidelity wireframes of the entire vision created
    • Feedback requested and incorporated into flow diagram and wireframes
  • Validate
  • Refine
    • Research findings incorporated into vision design
    • All micro-interactions are defined
    • All edge-cases are accounted for and defined to the best of your knowledge
      • Error cases
      • Extra long strings
      • Empty states
      • Disabled states
    • All copy has been reviewed by Technical Writing counterpart
    • Accessibility guidelines have been considered
    • Dark-mode
    • Responsive design
    • High-fidelity designs posted to issue for team feedback
      • Copy reviewed by Technical Writing counterpart
      • Feedback requested from counterparts
        • (If necessary) Validate high-fidelity vision design in a 2nd round of user testing
    • Refine final design from feedback and user research (if done)
  • Build Phase
    • Designs broken down based on their ability to stand alone while continuing to provide value to the user.
    • MVC plan agreement reached
    • Planning breakdown complete
  • Continue to collaborate with engineering counterparts during Build Phase (i.e., development/code is being written).
Edited by Justin Mandell