. We must make sure that all interactions between the user and the product are simplified as much as possible throughout the entire purchasing process. We should remove unnecessary text, optimize button names, and generally reduce the semantic load along the whole user journey.
. The most sensitive part of any working system is the user steps in the purchase workflow. We must avoid severe changes in this part of the product.
. When it comes to any purchase, users don't like the unexpected behavior of the system. It is necessary to build a purchase workflow in advance that will not change for as long as technologically possible (Best example: Amazon one-click purchases).
Another point associated with this bias is informing users about upcoming changes. Most people don't expect any change in how a product functions today and often underestimate inaction ().
. In our communication with the user, we should, wherever possible, emphasize that we share common humanistic values (). If our product involves making any decisions (arbitration, moderation, public presentation of our position on any issue), then we must emphasize the aspect of universal justice ().
. All parts of our product must be coherent. Not a single page and not a single element of communication (content, text, letter) should fall out of the context.
. We should, wherever possible, create content where the user "sees himself" to remove any doubts from the category "What if this does not suit me?"
. In order for the user not to feel discomfort, we should provide an opportunity to compare goods/services.
. If we know which elements of the product can cause emotional discomfort to the user, we should determine which ones can be removed and which ones can be made less noticeable. So, after the actual purchase, we can focus the user's attention on the benefits of his choice and not on the fact that he spent money.
. If our project involves selling personal belongings (e.g., auctions, classifieds, etc.), then the main risk may be excessively high prices set by sellers-owners. To ensure that prices do not cause significant discomfort to potential buyers, we can create a mechanism that will suggest the price based on the item's market price. Such a mechanism, made with the , will help reduce price dispersion for a product category.
. Depending on our product's specifics, we can provide the user with some kind of button/link where he can see the transaction's status (something like "Transaction completed successfully!").
. We should ensure that we have a comfortable starting point of the purchasing workflow in the product.
. The purchase mechanism should be transparent and understandable for the users, as well as the rest of the pages that the users see/interacts with during the purchase workflow. The challenge is to avoid emotional ups and downs in the workflow. The more transparent and understandable everything is for the users, the more stable they will feel.
. We must create mechanisms to ensure a quality user experience after the actual purchase. An example of such mechanisms: a thank-you letter with an invoice + additional product information to highlight the user's successful choice. At some point after the purchase, we can send the user additional positive information about his purchase to finally extinguish his doubts about the choice ().
#9.Why do our users find our communication overwhelming?
#24.How do we nudge users to take the actions we want with minimal cost?
#32.How can we maximize the comfort of the product?
#46.How to simplify our product?
#62.What to consider when creating a “Persona” for a product?