When I started to use notion to organize my life, I came across many people who stated that they stopped using notion for many reasons, and to be honest, I’m not here to discuss them; I’m here to explain, as a designer, why people like you and them stopped using this app and what my explanations are for the bad experience for you.
Many ex-notion users said that they found using the product unproductive, and they found themselves spending days and even weeks building systems without making any kind of progress toward their goals, goals that led them in the first place to use the product.
Notion was built in this way to convey a sense of value to the users and increase retention and loyalty. This is known as the “IKEA Effect.” The implementation of this effect was brilliant, and it worked for many people, including me. My engagement with the product increased significantly when I made my own systems, and at the end, I found myself kind of emotionally attached to it. On the other hand, there were a decent number of people who hated it, but if this effect was good, why are there users who have had bad experiences with the product?
Well, the IKEA effect is good; nobody can deny it, but only if the ecosystem of the product supports it, in which case it doesn’t, with simpler terminology. Notion was for the sake of providing productivity to people; they created on-demand complexity, and what I mean by “on-demand complexity” is If you want to build complex systems with databases and connect them in a way that nobody understands and sometimes even you don’t, then go for it, and if you just want simple task lists, check boxes, and a place to write without any distractions, you can also go for it. Both approaches are supported by the product, and this will put us in the second problem.
Some users started using notion and in their minds the goal of only achieving productivity by the it’s simplest means, but they end up getting overwhelmed in learning “the basics of Notion” and they may purchase courses, tutorials, guides and templets that costs them hundreds of dollars, the problem exists because of how the onboarding for newcomers works, it lacks for the proper guidance and it misses the ability to apply the customization concept in the product experience based on the user preferred approach causing them to think they are using the product in the wrong way when they see other people making esthetically pleasing systems with complexity in the backend, or they will end up paralyzed and not able to make any decision or any sort of actions in the product due to the huge amount of options they can do and have, at the end they will bounce away when they realize how much mental calories and energy it will costs them to use notion while there are simpler and convenient alternatives like obsidian.
When you first met notion, you expected that it would help you increase your productivity, but when you started using it, it failed to satisfy your needs. According to Aron Walter’s hierarchy, which is a modified version of Maslow’s hierarchy of needs but for product design.
Every product should fulfill three layers of user needs. ”It should be functional, reliable, and usable,” so you can get to the final layer, “feeling the pleasure.”. The product’s experience and how it was built made it hard for you to learn, and learning a tool is a cornerstone to making you able to handle any kind of problem that could happen to you while you are using it. If you don’t learn how to use the tool, it won’t be functional nor reliable to you, and at the end, you will bounce away to continue your journey to find better alternatives.