UX CORE GUIDE
(UXCG)
DescriptionWelcome
UXCG is a free tool that allows you to look at the most popular issues in product and project management from the perspective of cognitive science and behavioral economics.
Consider this tool as "Stackoverflow" for managers. Just instead of people's opinions, here we have 896 examples of how to approach abstract, management-specific problems scientifically, away from personal opinion and closer to the science and data.
How to use UXCG
Find the question that you're interested in (manually or via search). Read the answer of how a specific bias addresses your question. Since you fully understand how you have this question, you can simulate the answer with the actual situation. This tool is not providing you with solutions because each situation is unique, and for an exact, proper solution, there are hundreds and thousands of factors to consider. This tool allows you to see the paths that you haven't seen before and act more confident, as you're backed by science.
You can find the article describing this tool here, and another one explaining how we built this tool (geek content) here.
To use UXCG offline please visit the page "Using UXCG in Education". You can also download printable version of all UXCG questions by clicking here.
Label description
Team
Questions related to in-house team members cooperation (product, development teams and others).
Development
Questions related to product development stage (from concept to first public release).
Pre-SignUp
Questions related to sales, marketing funnels, prospects and leads communication, and overall product packaging.
Post-SignUp
Questions related to user interaction with actual product and its features.
Analytics
Questions related to product analytical data analysis.
All questions
Pre-SignUp
#1.
Our product/company has a reputation issue. How did this happen?
Post-SignUp
#2.
What could be the reason for our users’ dissatisfaction with the product quality?
Post-SignUp
#3.
Our users do not use the product features they have requested. What could be the reason?
Pre-SignUp
#4.
We are unable to create the correct associations with our product on the market. What could be the reason?
Post-SignUp
#5.
Our users are complaining about product updates. What could be the reason?
Pre-SignUp
Post-SignUp
#6.
New users complain that the product does not meet their expectations. What could be the reason?
Post-SignUp
#7.
Our users are gradually becoming disappointed with the product. What could be the reason?
Post-SignUp
#8.
What could be the reason for users’ high sensitivity to product changes?
Post-SignUp
#9.
Our users accuse us of being obsessive. What could be the reason?
Team
Pre-SignUp
Post-SignUp
#10.
Users complain about the quality of our support.
Post-SignUp
#11.
Our users accuse us of problems that have arisen because of their carelessness.
Pre-SignUp
#12.
Potential users exaggerate the risks of using our product. What could be the reason?
Post-SignUp
#13.
Our users do not follow the safety rules. What could be the reason?
Pre-SignUp
Post-SignUp
#14.
We were accused of a careless approach to business. What could be the reason?
Post-SignUp
#15.
Users say the product has become boring. What could be the reason?
Pre-SignUp
#16.
Our promotional activities are not bringing good results. What could be the reason?
Post-SignUp
#17.
Our users use only one feature of the product among many others. What could be the reason?
Post-SignUp
#18.
Our users pay too much attention to the secondary components of the product. What could be the reason?
Pre-SignUp
#19.
Potential users only see the weak points of our product. What could be the reason?
Pre-SignUp
Post-SignUp
#20.
How to stimulate sales on our project?
Pre-SignUp
Post-SignUp
#21.
Users do not like our communication. What did we do wrong?
Post-SignUp
#22.
Our users have not appreciated or downplayed the latest product updates. What could be the reason?
Development
Pre-SignUp
#23.
How to popularize one of our products among others?
Development
Pre-SignUp
Post-SignUp
#24.
How to nudge our users to take the actions we need at the lowest cost?
Development
Post-SignUp
#25.
How to reduce the amount of money withdrawn by users from our project?
Development
Pre-SignUp
Post-SignUp
#26.
How to make bonuses and promotions more attractive to users?
Development
Analytics
#27.
We want to launch a product in a market full of negative associations. What should be considered?
Pre-SignUp
Analytics
#28.
What mistakes do we make when evaluating the effectiveness of marketing?
Development
Pre-SignUp
Post-SignUp
#29.
How to provide the best purchasing experience for users?
Team
Analytics
#30.
What mistakes do we make when working with product analytics?
Development
Pre-SignUp
#31.
How to protect yourself from information wars (e.g. Disinformation)?
Development
Pre-SignUp
Post-SignUp
#32.
How to make the product as comfortable as possible?
Post-SignUp
#33.
What to do if user tells us about a case that according to the system never happened?
Pre-SignUp
Post-SignUp
#34.
How to give the product a more modern look at minimal cost?
Development
Post-SignUp
#35.
How to work with gambling in a product?
Development
Post-SignUp
#36.
How to create an atmosphere of trust in a social project?
Post-SignUp
#37.
What are the risks of significantly changing the product (ideology/functionality)?
Development
#38.
What to consider when creating moderation mechanisms?
Development
Post-SignUp
#39.
How to increase the responsibility of our users when using our product?
Development
Post-SignUp
#40.
How to efficiently show the content to our users?
Team
#41.
The stubbornness of our colleagues is damaging the teamwork process. What to do?
Development
Post-SignUp
#42.
How to create new products/services “out of nothing” with minimal costs?
Team
Analytics
#43.
What to consider when planning releases?
Development
Pre-SignUp
Post-SignUp
#44.
What to consider when working with user feedback?
Team
#45.
What to do if our team members do not share their opinion?
Post-SignUp
#46.
How to simplify our product?
Development
Post-SignUp
#47.
What to consider when contacting a user directly?
Post-SignUp
#48.
User involvement in product development.
Post-SignUp
#49.
What to do if our users are asking for changes that we cannot do?
Team
#50.
How to deal with an incompetent colleague/manager?
Post-SignUp
#51.
Why our users make mistakes when using the product?
Development
Post-SignUp
#52.
How to involve users in the beta testing of our product/feature?
Post-SignUp
#53.
What should be considered when removing unnecessary functionality from the product?
Post-SignUp
#54.
What should be considered when adding new functionality to the product?
Development
Post-SignUp
#55.
Which components of the product are most sensitive to change?
Development
Pre-SignUp
Post-SignUp
#56.
What to consider when working with lists (any)?
Development
Pre-SignUp
Post-SignUp
#57.
How to add additional value to a product “out of nothing” at minimal cost?
Development
Pre-SignUp
Post-SignUp
#58.
Work with users’ attention. How can we make sure that users see information that is important to us?
Team
Development
Analytics
#59.
What to consider when mentioning political, social, or economic events in a company’s texts/product?
Pre-SignUp
Post-SignUp
#60.
Users have difficulties on the product/service selection page. What to do?
Team
#61.
Our team spends too much time discussing irrelevant/minor details. What to do?
Development
Analytics
#62.
What to consider when creating a “Persona” for a product?
Post-SignUp
#63.
What to do if we made a big mistake in the latest release?
Be Kind. Do Good.