Improving component testing and user research - Process Definition

[ashifalinadaf]

Based on Process Definition Workshop

WIP file

Improving component testing and user research

User testing for components

• [x] • Create a group of product designers to test and provide feedback on early iterations of components.

Staging files for testing

• [x] • Test components before pushing them to the main library by staging files.
• [x] • This allows for testing of components with breaking changes.

Full page templates for testing

• [x] • Use a similar approach to the user testing done for the Table component.
• [x] • Build out full page templates as a testing ground for components with breaking changes.

More user research and usability testing

• [ ] • Conduct more user research, surveys, and usability testing to gather feedback and improve the user experience.

Success criteria:

• [x] Define the testing group
• [x] Create templates
• [ ] Better user research

[ashifalinadaf]

For initial review:

Figjam file

Full page template

@SeamusLeonardHPE Please have a look and see if it is in the direction.

[ashifalinadaf]

Inputs from the discussion with designers,

• Office hours/design critique announcement: Ask people to test components in office hours to announce testing, announce Friday as testing day?
• Getting people onboard is difficult: Need to tackle the issue of convincing people to test the component.
• Known issues / guidelines: Have guidelines, lesson learnt / known issues conveyed to the users before testing.
• Template requirements: Creating the templates based on the requirement.
• Evaluating the design: Define the evaluations criteria for better feedback.
• We cant control on user behaviour
• Ask questions before testing/ ask grommet part/ ask the experts

From Seamus,

• What are we testing ?
• User facing - does it solve the problem statement/use cases
• Component build - does it help product designers & align with grommet
• How do we solicit focused, useful feedback
• What level of fidelity is the design, will this impact the type of review we want

[ashifalinadaf]

• [ ] What are we testing? -

• Various testings we can consider based on different methods -

• For now we can consider the most used testing -

  • Component testing External (once it is built, confident that it meets most of our success criteria)
  • Component testing Internal

• [ ] User facing - does it solve the problem statement/use cases

• Once the component has been built - testing with designers/devs will help fill in the gaps of known issues/ meet the success criteria

• [ ] Component build - does it help product designers & align with grommet

• It does help the designers to understand how it aligns with grommet by letting them understand the constraints and guidelines that has been set by Design system.

• [ ] How do we solicit focused, useful feedback

• Gathering the focused feedback by asking use case specific questions, - questionnaire that helps not to deviate from the main testing criteria. however general feedback on components can be welcome for refining/adopting innovative solutions.

• [ ] What level of fidelity is the design, will this impact the type of review we want

• 3 types of fidelity can be made for now,

  1. During the build (internal)
  2. Once the component is ready to test with other teams (external)
  3. Final review before merging (internal)