Product Development (part 4); "further development" (English Version)
The Show must go on ....
Finally the time has come. After a long time of testing, changing and fine-tuning, we can start with the unveiling. After months of working on the product, the world will get to know it. How do you handle that. In this fourth part of the series I want to go into more detail.
Product Development, Part 4, “The Show Must Go On”.
You face a big decision; “Reveal the product and show it to the world. After all, you can only introduce your product once, right? I think it can be done better in phases. Small steps. Just think; You also learn to walk first and only then can you train for a marathon. Introduce your product within a limited group first. Call it "Beta Version" and collect feedback. Make sure you have good contact with the users. You will be amazed at how well the words 'Beta Version' works. Users feel involved in the development, especially if they are listened to. The feeling of being part of an exclusive group is still appealing. This group has the opportunity to become an ambassador for your product in the early days. Don't be afraid to make mistakes, but above all to admit them. If something doesn't work, acknowledge it, change it and move on.
During the pilot or 'Beta' phase you can already make plans to roll out the product to a larger audience. Important factors to consider are:
- Planning: When is it useful to release? Are there other major events that overshadow my product launch?
- Availability: When I launch the product, can the new users start using it right away?
- Accessibility: Is the product directly accessible or do other aspects have to be arranged by the user first? A good example was the introduction of a government website, but to register on it you first need DigiD.
- Scalability: Is there enough capacity? If it's a success (and you hope it does), don't spoil the fun because the system can't handle the demand.
Then you want to add new options, the further development of the product. There was no time or space for that in the MVP. It is important to create a program. Not everything can be done at once. Make it clear, transparent and alternate visible things with less visible improvements. It would be nice if there were themes in the program. This helps to set and maintain the focus of the teams. The user group will then also understand better that other features outside the theme will have to wait a while.
One of the major pitfalls is that organizations only start thinking about further development after the MVP. This creates a gap between the first (MVP) release and the subsequent second release. There is a chance that users will drop out because the MVP product offers too little added value. In practice, it is very difficult to get these users who have dropped out 'on board' again. So plan well and work ahead where possible. Make sure new options are added quickly. Rather in small steps than waiting a long time for a major release, after all “The Show must go on”.
Above all, don't forget to put the spotlight on the people who have worked hard for months on this. Those are the real stars in the show, give them credit and appreciate them. Make it a party. You're going to need them during the program.
Casper.
https://www.casperotto.nl/en-gb/home
https://www.casperotto.nl/en-gb/blog
Blog
