abbott567 / p_test Goto Github PK

This part of the template focuses on the design process. Please make sure to follow these steps and mark them complete once done:

### Review and Gather Information
- [ ] Review the Epic, user stories, problem statements, and Jobs-To-Be-Done to ensure a clear understanding of the user's needs and the problems we are solving.
- [ ] Review the success criteria. Ensure they align with the project's objectives and are measurable.
- [ ] Identify any gaps in information or areas that require clarification. Seek necessary clarifications to ensure a clear understanding of the project requirements.
- [ ] **Docs**: Assess whether the proposed changes will require updates or creation of help documentation. If so, create a new issue to track this task.

Project kick-off

- [ ] **Stakeholders**: Make sure stakehodlers list represtnts all relevant individuals who needs to contribute and be aware of this project.
- [ ] **Project kicks off**: Run a session with all stakeholders to review the project together, identify gaps and addition tasks if applicable.

Discovery and Research

- [ ] Plan and conduct necessary research. This could include user interviews, surveys, market analysis, etc. 
- [ ] If no new research is needed, identify the existing information, assumptions, or data that will be used. Ensure this information is up-to-date and relevant to the project.
- [ ] Analyze and synthesize the research findings. Document key insights that will guide the design process.
- [ ] Share research findings with the team and stakeholders. Ensure everyone understands the key insights and implications for the project.

Design Execution

Break down of design work. Keep/add only relevant tasks:

- [ ] Creating workflows
- [ ] Journey maps 
- [ ] Wireframes
- [ ] Final mockups
- [ ] Prototypes
- [ ] UX Copy review
- [ ] additional work? add tasks

Feedback and Validation

- [ ] Review design with stakeholders: such as PMs, UX and Docs writers, Engineers and etc
- [ ] Creating prototypes for usability testing
- [ ] Usability testing

Handoff and Check Activities

- [ ] Review EUI Components with EUI team
- [ ] Documenting and Preparing Figma files for development handoff
- [ ] Handoff to development 
- [ ] Create docs artifacts
- [ ] Design QA 

Design Task Completion Checklist

- [ ] **EUI Design Compliance:** The design adheres to the EUI design system, including its UI components, typography, colors, logos, etc. Design should support dark theme.
- [ ] **User Experience Compliance:** The design provides a satisfying, easy, and effective user interaction. It incorporates insights from user research, and/or applies best practices and prior knowledge. The design should be reviewed through user flow diagrams, wireframes, and prototypes. The design maintains consistency across the product, anticipates potential user errors, and is part of a holistic design that considers various workflows within the product. 
- [ ] **Accessibility:** The design complies with accessibility standards, ensuring it can be used by people with various abilities.
- [ ] **Design Documentation:** The design decisions are documented and available to the team. This might include design rationales, personas, or user journey maps. The documentions can be done in Figma, Google docs and other relevant documents
- [ ] **Stakeholder Approval:** Key stakeholders (e.g. product manager, engineering lead, design lead.) have reviewed and approved the design.
- [ ] **Testing & Evaluation:** If feasible, the design has been tested and validated through methods like usability testing. If these methods are not possible, alternative evaluation techniques, such as expert reviews or heuristic evaluations, congitive walkthroughs should be used to ensure the design meets user needs and expectations.
- [ ] **Design Handoff and Asset Delivery:** All necessary design assets (such as icons, images, fonts) have been delivered in the correct format to the development team, and the design itself has been communicated clearly, with an opportunity for questions and clarification. Tools like Zeplin, Figma, or Adobe XD can assist with this.
- [ ] **Design QA Check in Development:** During the development phase, design QA check performed to ensure that the development aligns with the original design. Check for discrepancies between the design and the developed product, and ensure any differences are justified and approved. This helps in catching and fixing any design implementation issues early.

Include links to all relevant documents, such as Figma files, Google docs, research data, etc.
Main Figma: link
Docs design sssets: link