How to launch in a market with strong negative associations?

How to launch in a market with strong negative associations?

Possible answers (13)

. If the project is still at the development stage, we should allow outside observers to evaluate our thoughts and ideas. Perhaps the idea we want to implement is not good enough to avoid all the market risks.
If we have already conducted some surveys of potential users, we should consider .
, . We should carefully study the stereotypes prevailing in the market and understand the ones that play into our hands as well as the ones that should be avoided by all means.
. When working in such a market, we should be specific in everything that is generally possible. The audience will interpret any discrepancy in our communication in an extremely negative way.
, . Any mistake we make in communication or product functionality will be greeted sharply negatively (as something expected).
. We must take care of our product's image from the very beginning and clearly distinguish our difference from other products on the market. The use of this bias should be a mandatory component of our communication.
. When talking to our audience, we should do it as clearly as possible. We must exclude the possibility of any discrepancies.
. To be "clean" in such a market, we must be careful with our news release frequency. In addition to this, it is important that our communication is consistent and does not fall out of the context (our "storyline") that we adhere to ().
. In such a market, it may be risky to use objects familiar to the audience for promo campaigns. We can know the attitude of potential users to the market. We can know the relationship of users to an object. But we cannot calculate how users will interpret their combination.
. When launching on such markets, as well as publishing some updates, we should time it with the conjuncture (world, market, region). We should make sure that people do not have any additional stress because of external events (covid, war, revolution, etc.).
, . Before creating content/communication that will affect people personally, we need to understand their relationship to the market, product, and the fact that they relate to our audience. So, in some cases, despite the competent use of the self-reference effect, we may fail because of the ideological values/beliefs of users ().
. It should be understood that working in troubled markets implies a constant presence in the risk zone. We will always be expected to behave badly because of market stereotypes (, ). Moreover, the audience will react very sharply to our every mistake.
We will undoubtedly make mistakes. However, it should be understood that most of them will be forgotten much faster than we might think ().

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.