Failures and success of product development
During my career as a developer, and later as a CEO of my own company, I have seen good and bad strategies, incredible marketing tricks, and decisions that killed startups. But as a service provider, we often don’t have much influence on the client’s decisions and overall product strategy. So I was dreaming of our own product for a long time.
Improve your product development skills
At datarockets, we have developed many cool products for our awesome clients and partners: CRM systems, news portals, ERP systems, CPA networks, mobile apps for nightclubs, and unique products for startups that are going to change the world.
During the last year, I’ve read a number of books about management, marketing, modern development processes, leadership, negotiation, and investing, as I am trying to improve my product development skills. We motivate our developers to do the same – not just focus on coding. That’s why we position ourselves as a product development team, not just an outsource development resource. On the photo above, I’m telling the team how important it is to improve product development skills at one of our weekly meetups.
First attempt – failure
On our team, we have a Trello board where we record our ideas of products and discuss them. It so happened one day someone created a card with an idea to implement a password storage that might be comfortable for teams to use. At that moment, there were a couple of similar apps for personal password management but no alternatives for teams.
In development, we often need to share credentials for third-party services, ssh keys, and license keys for every project. So we decided to build a simple app to automate that process. We called it
YAPS (Yet Another Password Storage) – Don’t ask me why. I don’t remember 🙂
We described our idea and allocated three developers to work on the project.
After 2.5 months of development, we got the first version of the product. It was not what we wanted and the app had a bunch of bugs and was not comfortable to use at all. But at that moment, we had a bigger issue: we spent more money than expected.
Regardless of the poor results and budget issues, a popular company released a new product – 1Password for teams.
It was much better than our solution, and 1Password had a much bigger budget for development and marketing.
We decided just to switch to 1Password for teams and forget about our own product and considered our time and money investments as a good experience. BTW, we are still using 1Password I really like this product and it covers all our needs and is very comfortable.
Product development mistakes
In hindsight, we made a lot of mistakes. I see them now and would like to share with you, we paid a lot for this experience:
- The product was pretty complex. We had positive estimates in our minds and wanted to build too much in terms of MVP.
- What was the target audience? Developers? How many developers experienced the same issue with password management?
- Our CTO and I didn’t allocate enough time to participate and provide a feedback. We focused on client projects to earn money to invest into YAPS. There should always be a person on a project that has a clear vision of the product – a product owner. In our case, we didn’t have that person and it caused a lot of long discussions and no optimal decisions.
Our successful product development story
A year later, one of our skilled datarockers, Dima Chyrta, had two weeks between two projects and we decided to use this delay carefully to build something small and useful. We are big fans of a popular card game Munchkin. We know that this game has millions of fans all around the world. The game is really cool, but it’s hard to track player levels and strengths. We previously tracked that info on paper as the rest of Munchkin players. So we decided to create a simple app to resolve this issue – Munchkin Level Counter for Android.
Product development insights
This time, we knew much more than we did previously:
- The app was really simple.
- The target audience was absolutely clear and we were sure that the app could be helpful for the Munchkin community.
- We had an absolutely clear vision on what the app should do. Every datarocker knew Munchkin game and might play the product owner role. In our case, Dima was the only developer and product owner, and as far as the app, it was very simple.
- There is a competitor app, but it costs five dollars. We decided that to compete we can build an app with a better user experience, and we don’t want to earn anything on this. We can make it free.
After two weeks, we had the first version and published it to Google Play for free. I wrote a couple of posts on our social networks and that is how we got our first users. They provided a quick feedback and we made a couple of tweaks. After that, the app’s user base began growing:
We had 4.4 stars and 122 ratings on Google Play:
I’m excited every time when seeing new reviews and we pay a lot of attention to them. We have implemented a couple of new features and made some changes per user requests:
One of the advantages of our product is an open source code and is open for contributions. That is how we got a couple of improvements and translations to other languages. I want to thankGuillaume Husta, Niels van Asten and Christoph Schreyer for their contributions. You guys are awesome!
8 tips before starting a product development
I’m not going to say it is a big success story or that we have built something that can change the world. We created a small product which helps Munchkin players and we gained some small experience in our own product development. Here, I leave my notes, advice and a list of useful books that helped us.
- Before starting a product development, always question if it can help people.
- Define your exact target audience and think why your product could be interesting.
- Start with something simple. The MVP version of your product should be as light as possible.
- Be ready to allocate enough time. A product cannot exist without the product owner.
- Analyze your competitors. When competition is high, the product may require aggressive marketing efforts.
- Deliver a better user experience; do your best to fight your competitors. There are no silver bullets – if your product is shitty, nobody will use it anyway.
- Pay attention to user feedback. Answer users.
- If there is a possibility to make your product open source, or at least a part of it – do that. One day you will receive a pull request with a new feature or an improvement or a bug fix.
As I mentioned, I have read a bunch of books about product development and want to outline the two “must-read”: