. We should avoid overusing instructions and security mechanisms. Instead, we can select key risks and periodically remind the user of them while working with the product.
. Instead of abstract messages about risks, we can show the user the potential consequences of his inattention to work. This can be an illustrative example where the user will see and evaluate his “current status” and “what might happen” next to each other.
, , . We can change the wording in our communication with the user to push him to some actions.
. If users systematically ignore some action that we expect from them in a specific workflow, we can change the process itself. Even small changes in standard workflows in which users have ingrained habits will significantly grab their attention.
. In our communication with the user, we can appeal to the majority of our users, demonstrating through their example the benefits of following our advice.
, . We can place an extra button which, according to our instructions, will need to be pressed at the end of a series of actions (workflow).
. In our communication with the user, we can appeal to the social desirability of the requested action. If we emphasize that this action will be visible to others at the same time, this can significantly increase the user's responsibility.
. When it comes to a B2B product, users' irresponsible approach to using the product can result from a combination of arrogance and incompetence. In such cases, we should not appeal to the professionalism of our advice, but to something that will not hurt their egos.
#51.What causes users to make mistakes when using our product?
#58.How can we make sure users notice the information that matters most to us?
#11.Users blame us for their own mistakes
#13.Why don’t our users follow the safety rules?
#24.How do we nudge users to take the actions we want with minimal cost?