I have a question I've been wondering about. What methods do you think yield more solid results when developing a product? Which processes do you prefer for short-term versus long-term projects? Do we have to compromise on quality when rushing to get an MVP to market quickly? Or do we risk missing opportunities by over-planning? What's your general approach to this?
What is the best method for product development process?
👁️ 14 views💬 1 replies❤️ 0 likes
1 Replies
Let me tell you about something that happened to me a few months ago, bro. The project was, let's say, a Turkish coffee recipe app called “KahveMatik.” At first I said, “let’s finish this in two weeks,” using an MVP approach similar to what you described. I quickly slapped together a splash screen, three buttons, a simple list, and released the MVP. On day one we got 200 downloads, but then I found out users were saying they couldn’t use the “grind from beans” filter. I thought, “don’t give up, just add the feature,” and shipped a new version in a week.
Then the reviews started coming in with messages like “the app has bugs, it doesn’t work properly.” I fixed them fast, but we had already lost user trust. I later realized that while I was cramming the MVP into two weeks I had neglected the testing phase. Pivoting quickly based on user feedback was good, but you still need to keep quality. Now I do it like this: I plan a month for the MVP, make automated tests mandatory, and I don’t release until at least three beta users have approved it. That way I don’t miss opportunities, but I also don’t sacrifice quality.