What to consider when working with lists (any)?

What to consider when working with lists (any)?

Possible answers (9)

. The order of the components in the list affects the quality of the content perception. Each subsequent element of the list should be a logical continuation of the previous element. For example, if I placed this item in the middle of the list, it might be less comfortable to read.
. A correctly selected number of items in a list increases the likelihood of reading/completing it.
. If the list consists of different events (e.g., a list of alerts), then when prioritizing them, we should consider the effect of primacy.
. By adding features such as system prompts, we reduce users' attention while increasing their comfort in working with lists. We need to find the line where the system will support users, but at the same time, it will not lead them to entirely depend on this support (of course, if this is not our goal).
. Lists are especially sensitive to different object types that "fall out" of the standard. This can be used when we want to draw the user's attention to something specific.
. By setting a negative tone at the very beginning of the list, we significantly affect the user’s perception of it. This factor can be used in completely different ways, depending on the product's specifics and goals.
. Depending on the positioning and order of items in the list, we can control the user's level of attention and the number of differences noticed by them.
, . When regularly working with lists, users quickly create small habits to keep the number of actions minimum. We should be aware of these habits and do not let our changes affect those.
. We can underline the most important items in the list by placing them at the beginning or end.

Related questions

How useful you found this?
Not useful
1
2
3
4
5
6
7
8
9
10
Not useful
Very useful
Thank you for your contribution!
previous bias
next bias
keepsimple logo
picLog In
My ProfileSettingsLog Out

UX CORE GUIDE

arrow downHow to use

UXCG is a free tool that helps teams detect cognitive bias-related UX problems across all product stages, whether you're prototyping, testing, or improving a live product

How to use UXCG

  1. Choose your product stage below;
  2. Find your question (either manually or through search);
  3. Read possible answers.

Each answer explains how cognitive biases relate to your specific situation. Since you understand your context best, you can apply the insights directly. While the tool doesn't provide ready solutions due to each case's uniqueness, it reveals new perspectives backed by cognitive science.

Label description
Questions related to in-house team members cooperation (product, development teams and others).
Questions related to product development stage (from concept to first public release).
Questions related to sales, marketing funnels, prospects and leads communication, and overall product packaging.
Questions related to user interaction with actual product and its features.
Questions related to product analytical data analysis.
search icon
Select your product stage
#10.

Why do users complain about the quality of our support?

#30.

What common mistakes do we make when dealing with product analytics?

#41.

What should we do if our colleagues’ stubbornness is hurting teamwork?

#43.

What to consider when planning product releases?

#45.

What to do if our team members do not share their opinion?

#50.

How to deal with an incompetent colleague/manager?

#59.

What should we consider when referencing political, social, or economic events in our messages?

#61.

What should we do if our team wastes too much time on minor details?

Be Kind. Do Good.