Why don’t our users follow the safety rules?

Why don’t our users follow the safety rules?

Possible answers (9)

. We underestimated the complexity of complying with the safety regulations we have made.
, . We may have relied too heavily on our users' common sense and did not explain the potential risks well enough. We were unable to convey the instructions' significance and present them in a user-friendly way.
, , , . In our communication, we haven’t emphasized the risks and consequences of user actions (or inaction) well enough.
. We have chosen a bad place/moment to ask a user for a security action. Perhaps the request falls out of context.
. We did not take care of the reminders for the required actions or the request wasn’t matched with the emotions experienced by users when receiving the reminder.
. Users avoid safety-related materials because of the emotional discomfort they feel when they think of the required action.
. Users rely too heavily on system advice.
. Most people in the user group do not use security rules, and they never discuss them. The user, in turn, considers following the rules something unnecessary.
. Users do not understand the importance of the rules because of their low qualifications. Or, they think the rules are unnecessary, thereby exaggerating their professional skills.

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.