4. Feedback. (Feedback can be painfull at first but it will be your best allied.)
4.Feedback. (Feedback can be painfull at first but it will be your best allied.)
Now the fun really begins. Your product is ready and you will present it to users and customers. Here you will read about how to launch your web product, how to receive feedback about which indicators to follow and how to improve these indicators.
The purpose of these article is to help you reflect a little on your real goals in having a startup. This is a very difficult path, which takes a lot of work, but can bring many rewards. The reward will not necessarily come in the form of money, so it is very important to reflect a lot before starting this journey.
The first good practice we will cover is the ongoing development.
This form of development is opposed to the model known as waterfall. In waterfall development, the product development phases are clearly defined and, once a phase has ended and one cannot start back.
For example, if you want to develop a web product, in waterfall development you need to specify absolutely all the functionality that you want in these software, as software development is seen as a project with beginning, middle and end that happens in sequence: definition of requirements, detailing and specification of the product, coding, test and production. In the ongoing development of software, this cycle is reduced to a maneuver that is possible and repeated several times using the previous cycle feedback to improve the next cycle.
Jeff Patton, a renowned software development consultant, made a comparison between waterfall and iterative software development.
Making an analogy with the process of painting a frame. Which of the two processes below appears to be more natural?
To recap: make the web product fast = know what to do + good professionals + good software engineering practices
In the last two chapters, we talk about why we should make a web product fast and not get enough professional banners, good equipment and methodology, it is essential to define the minimum product, that is, what features among the features that are out of the first version of your web product and what are the best practices for using this software.
If you are not ashamed of the first version of your product, you have longed to stop.
–ReidHoffman founder of LinkedInd
Receiving feedback from your product:It is the “Moment of Truth”
You have just launched your product, if you have left some easy way for your users to contact you, you are starting to receive general user emails. This is a very important moment. It is the “Moment of Truth”
You start real users using your product. You showed up to your page when you campaigned on Google AdWords, used a few keywords and made an ad describing the problem and its solution so that users could identify themselves with the problem and click on your ad. It is these emails that will tell you whether or not you are headed in the right direction to solve these users' problems.
Dealing with users' emails Here are some tips to consolidate these emails:
Respond quickly It is important to respond quickly to your emails. This will create an awareness of who is receiving your responses that whoever is behind the web product cares about the comments and users of your system.
This helps to create a positive image of your product.Non-inventor Don't tell us that you are going to implement some specific functionality and some future features that you have no plans to do, or if that is a remote possibility.
Be educated These people who are e-mailing you are giving you very valuable information. Even if they are not very educated with you, what they are doing is to help you understand how they are perceiving your product.
- Your polite way of treating them can eventually help to reverse the impression that your user has of your product.
- Do not implement any suggestions you might receive Especially at the beginning you will receive a lot of functionality suggestions.
- Mobile version. More predictive operation, knowing the user is filling the data automatically.
- And so it goes. In this beginning the recommended thing is not to implement anything, you are still getting to know your users and understanding their application solves a problem with them.
- If you implement all the suggestions you want to receive, you can ruin the solution that created and, worse, you will start to make your web product complicated, with many unnecessary features.
- To deal with all suggestions, it is not necessary to create a system for writing them down.
After some time getting suggestions, you will remember which ones are the most popular. If you want to implement a suggestion system, there is UserVoice (http://uservoice.com) that has a free version.
Don't use e-mail as a form of feedback
Although your users who send you feedback via e-mail already tell you a lot, you shouldn't consider them as your only source of feedback. You should use your web application usage statistics as a tool to understand how your product is being used.
How many times people access it, how much data people use within the system, after how long people come back. All of this you should be able to extract from your database because of the statistics of access to your site and the web application.
Interact with your users by other means
There are other ways besides email for you to interact with your users. Your website has a blog for you to tell us about your product, right? In the comments of the posts you will certainly receive a lot of cool information. You can also create a Facebook page, which can be placed where users of your product and find themselves experiencing experiences. If you have the opportunity, chat live with the people using your system. Live conversations are automatic because they allow greater interaction and retro information.
Be careful when launching a minimum product to early.
Previously we talked about the importance of rapidly developing the first version of your web product. Also mention that, in order to get fast, don't beat great professionals with the best software development methodologies.
As I explained in previous article, you need to know how to define the minimum functionality required for your product.
Be prepared to keep walking fast as soon as you launch your minimal product with the feedback that you get for not developing any suggestions your first users give you does not mean doing nothing. Look:
- You have launched a minimal product.
- You have made choices and left out several features to be able to launch your first version of logos.
- You must have a list of next features that you need to implement in your product and the web can bring you into the category of at least.
- You must compare this list with feedback that you get from your users as well as the product to be able to prioritize the development of these features.
- You must be extremely careful in choosing the next features to be implemented to make sure that you are investing in the features that help you make the most out of your product.