Return to Question

This is my first post here, and what I am searching for has not been found yet, so I must be very innovative (jokes aside). I have gotten a mission at my current company from the C-level to test through all of the components and patterns of our design system. This is everything from input components, badges, tables, cards, panels, etc. Our design system is structured based on atomic design.

I am however not familiar with testing on specific components alone. I have always done it through scenarios and cases where we have whole layouts with components that will support our users in their work. Is there any way of performing smaller usability tests without specific cases?

Here's what I was thinking:

1. I could test each component against certain criteria.
2. I could perform the 5-second test (identify how it is being perceived after 5 seconds)
3. The break-it-method, where users and test participants try to find errors and problems in the functionality and usability
4. Test participants will compare our components one by one with those of material design or lightning
5. Evaluate the components through CBUQ (Component-Based Usability Questionnaire)
6. Have small tasks for each component to see how easy they are to use and navigate, e.g. Task1 - enter data, Task2 - remove entered data, Task3 - Navigate using keyboard etc.

Are any of these ideas good? Are there any others? Please help! Any input is valuable! :)

This is my first post here, and what I am searching for has not been found yet, so I must be very innovative (jokes aside). I have gotten a mission at my current company from the C-level to test through all of the components and patterns of our design system. This is everything from input components, badges, tables, cards, panels, etc. Our design system is structured based on atomic design.

I am however not familiar with testing on specific components alone. I have always done it through scenarios and cases where we have whole layouts with components that will support our users in their work. Is there any way of performing smaller usability tests without specific cases?

Here's what I was thinking:

1. I could test each component against certain criteria;
2. I could perform 5-second tests (identify how each component is perceived after 5 seconds);
3. The break-it-method, where users and test participants try to find errors and problems in the functionality and usability;
4. Test participants will compare our components one by one with those of Material Design or Lightning;
5. Evaluate the components through CBUQ (Component-Based Usability Questionnaire);
6. Have small tasks for each component to see how easy they are to use and navigate, e.g. Task1 - enter data, Task2 - remove entered data, Task3 - Navigate using keyboard etc.

Are any of these ideas good? Are there any others? Please help! Any input is valuable! :)

This is my first post here, and what I am searching for have not been found yet so I must be very innovative (jokes aside). I have gotten a mission at my current company from the C-level to test through all of the components and patterns of our design system. This is everything from input components, badges, tables, cards, panels etc. Our design system is structured based on atomic design.

I am however not familiar with testing on specific components alone, I have always done it through scenarios and cases where we have whole layouts with components that will support our users in their work. Is there any way of performing smaller usability tests without specific cases?

Here's what I was thinking:

1. I could test each component against certain criterias.
2. I could perform the 5-second test (identify how it is being percieved after 5 seconds)
3. The break-it-method, where users and test participants try to find errors and problems in the functionality and usability
4. Test participants will compare our components one by one with those of material design or lightning
5. Evaluate the components through CBUQ (Component-Based Usability Questionnaire)
6. Have small tasks for each component to see how easy they are to use and navigate, e.g. Task1 - enter data, Task2 - remove entered data, Task3 - Navigate using keyboard etc.

Are any of these ideas good? Are there any others? Please help! Any input in valuable! :)

This is my first post here, and what I am searching for has not been found yet, so I must be very innovative (jokes aside). I have gotten a mission at my current company from the C-level to test through all of the components and patterns of our design system. This is everything from input components, badges, tables, cards, panels, etc. Our design system is structured based on atomic design.

I am however not familiar with testing on specific components alone. I have always done it through scenarios and cases where we have whole layouts with components that will support our users in their work. Is there any way of performing smaller usability tests without specific cases?

Here's what I was thinking:

1. I could test each component against certain criteria.
2. I could perform the 5-second test (identify how it is being perceived after 5 seconds)
3. The break-it-method, where users and test participants try to find errors and problems in the functionality and usability
4. Test participants will compare our components one by one with those of material design or lightning
5. Evaluate the components through CBUQ (Component-Based Usability Questionnaire)
6. Have small tasks for each component to see how easy they are to use and navigate, e.g. Task1 - enter data, Task2 - remove entered data, Task3 - Navigate using keyboard etc.

Are any of these ideas good? Are there any others? Please help! Any input is valuable! :)

This is my first post here, and what I am searching for have not been found yet, I must be very innovate, joke aside. I have gotten a mission at my current company from the C-level to test through all of the components and patterns of our design system. This is everything from input components, badges, tables, cards, panels etc. Our design system is structured based on atomic design.

I am however not familiar with testing on specific components alone, I have always done it through scenarios and cases where we have whole layouts with components that will support our users in their work. Is there any way of performing smaller usability tests without specific cases?

Here's what I was thinking:

1. I could test each component against certain criterias.
2. I could perform the 5-second test (identify how it is being percieved after 5 seconds)
3. The break-it-method, where users and test paricipants try to find errors and problems in the functionality and usability
4. Test participants will compare our components one by one with those of material design or lightning
5. Evaluate the components through CBUQ (Component-Based Usability Questionnaire)
6. Have small tasks for each component to see how easy they are to use and navigate, e.g. Task1 - enter data, Task2 - remove entered data, Task3 - Navigate using keyboard etc.

Are any of these ideas good? Are there any others? Please help! Any input in valuable! :)

This is my first post here, and what I am searching for have not been found yet so I must be very innovative (jokes aside). I have gotten a mission at my current company from the C-level to test through all of the components and patterns of our design system. This is everything from input components, badges, tables, cards, panels etc. Our design system is structured based on atomic design.

I am however not familiar with testing on specific components alone, I have always done it through scenarios and cases where we have whole layouts with components that will support our users in their work. Is there any way of performing smaller usability tests without specific cases?

Here's what I was thinking:

1. I could test each component against certain criterias.
2. I could perform the 5-second test (identify how it is being percieved after 5 seconds)
3. The break-it-method, where users and test participants try to find errors and problems in the functionality and usability
4. Test participants will compare our components one by one with those of material design or lightning
5. Evaluate the components through CBUQ (Component-Based Usability Questionnaire)
6. Have small tasks for each component to see how easy they are to use and navigate, e.g. Task1 - enter data, Task2 - remove entered data, Task3 - Navigate using keyboard etc.

Are any of these ideas good? Are there any others? Please help! Any input in valuable! :)