Cihan Demir // Allianz Türkiye - Çevik Takım Üyesi
We've all experienced it: when we spend money or time on something, we naturally have a hard time giving up on it. It is possible not to fall into this situation called the Sunk Cost Fallacy, thanks to the MVP, a.k.a. Minimum Viable Product. Let's look at the details...
Imagine a product or a module. Let it be developed with great effort and belief. Moreover, a considerable amount of time and budget has been spent on this product or module. But things did not go as expected, expected results or returns were not obtained. Just then, Morpheus appears in front of you with a red and a blue pill in his palms. Time to decide: On the one hand, to continue because so much effort and cost has been spent, and on the other hand, to give up by saying "okay." Which one do you choose?
This scenario probably sounds familiar. Even if you are not the person who made this decision directly, you may have experienced or heard of a similar situation in your team or project. This can happen not only at work, but also in your daily life, for example, when you order a meal just to try it. You may not have liked the taste of the food or guessed that it would upset your stomach after taking a fork. But you wanted to "finish" because of the "cost." So, what is it that pushes you to take the decision "We've spent so much, we should finish it"? Why, even when you understand this, can't you just say "stop" to yourself, bear the cost and give up?
The answer to all these questions is hidden in the concept of "Sunk Cost Fallacy".
A sunk cost is a cost that has already been incurred and is no longer recoverable. You can kiss it goodbye! The mistake is to continue this investment persistently. In this perspective, we can clearly see that this is not a good situation, more so unreasonable, right? However, we can fall into this error both in our business and private lives, because we are irrational by nature and – except in exceptional cases – without realizing it.
The situation we are in can lead us to dead-end streets by “myopicizing” us due to our experiences from the past or our emotional states with different triggers. It’s a perfect example of "human nature."
Let's continue with a dramatic scenario that can have an equivalent in everyday life:
At first, we trusted and believed in the product, we had great dreams, instead of asking the user or the consumer, we made assumptions by thinking on behalf of the user that "they will use these features" or "they will definitely like these features" and we started to develop the product. In the meantime, we have progressed by adding countless screens, functions, features, and we coded as if we’re pulling a rabbit out of the hat. Our admiration and love for the product was increasing day by day. We were proud.
A considerable time passed, we spent a serious budget and when the day came, we brought the product to the user. But what is that? For some reason, all the features and functions that we found useful or necessary and admired from our own perspective did not find a response. There was an awkward silence. We couldn't see the effect we expected, as if the user was unresponsive to it...
The button, which we are proud of as “a very important button, not found in any other product,” was not given much importance by the user, even not noticed, never clicked.
The interfaces, on the backend of which a lot of effort has been made and on which you can perform a thousand kinds of actions, were returned with "difficult and very complicated to use, isn't there something simpler?"
"I click 7 times before I can reach X, can't this be done with a single click?" questions upset you. After all, you had designed the information architecture very well and you could argue relentlessly that 7 clicks should be required to reach that part.
You thought that if only they knew what was happening on the backend of the interface that made users says "It's taking a long time", which made them wait for 3.56 seconds (it was milliseconds while testing), what state-of-the-art technologies are used, what services are running, and if only they had a little patience.
Do these sound familiar? What I mentioned above are the unpleasant situations. I hope you haven't experienced any of these. But if you have, I am sure that you have seen these experiences as a learning opportunity and turned them into an advantage.
So how can we use the agile working model to avoid this misconception? The answer is hidden in three letters…
First of all, we go to the HEY! Dictionary for the definition of MVP (Minimum Viable Product):
MVP: A viable, valid, practical product that has the functions that the user can experience in the agile working model and that the manufacturer can get feedback from the user, has the core features that are really needed. It is derived from the initials of the words Minimum Viable Product.
MVP proposes a process that aims to get you to a product in a practical way. It is recommended that we develop prototype products with user stories written from the user perspective, step by step, by getting feedback, by seizing the opportunity for empathy, by trial and error in a short time, by learning fast and by determining the priorities well.
Imagine that you have produced an uncomplicated and simple, practical product that has the most vital and value-creating core features, truly responding to the highest priority needs, and most importantly, that the product develops with the feedback received from and listening to its users! And that you've come up with it in a short time, without spending a lot of time or a significant budget… It looks extremely easy, doesn't it?
I wish all of us processes where we do not fall into the sunk cost fallacy and produce products that work exactly as we imagined with these simple but extremely useful tips in the agile working model like MVP.
P.S. You can contact us by clicking here to share your experiences and ask questions about the agile working method.
Comments