Unfortunately, things do not always go as smooth as it would be expected. There are cases though when a product's launch goes exactly as scheduled, when the software functions perfectly, or when unexpected situations do not occur. Nevertheless, undesirable situations can be avoided, if not altogether, at least to a quite great extent.
Common Mistakes When Launching a Software Product
Rumor has it that "to err is human". Yet, errors made when launching or preparing to launch a software product can cost dearly. Any aspect that was neglected or treated superficially can have significant negative consequences. Following are some of the most common mistakes that are made during or before launching a product.
- Failure to perform an accurate, thorough market research. It is imperative that you find out as accurately as possible what segment of the market your software will be dedicated to, what needs there are on that particular segment and how you can meet them, what prospective customers expect to get, how the media sees the product you're envisaging, etc.
I also found an article you might find useful, "11 Questions Every Marketer Needs to Ask" , dealing with aspects like pricing, segmentation, product positioning etc.
- Not being realistic about the expenses implied by such an event. The budget must be well thought. Be realistic when assessing the costs of your product launch. If you don't plan everything well enough, you could end up spending much more than originally predicted. Even better, you could propose a bigger budget for the unforeseen situations; preventing is better that facing.
- Not dedicating enough time for planning a marketing strategy. It is important to give yourself enough time to plan ahead. You must be able to see into the future up to the moment when the product will be launched and establish a series of steps that you must go through prior to the launch itself. Such steps would include:
1. thoroughly investigating the market and attempting to find out where you stand
2. analyzing your past experience in conjunction with what you are planning to do and how
3. preparing information that will go to the media (e.g. press releases), as well as advertising campaigns.
- Ignoring the fact that it is the market that dictates your product. Always remember that you have to be objective. It's not about what you want, but what the people need. It is according to this need that you have to develop your software.
Not providing all the necessary data to the company that takes care of your software's launch. Of course, the best approach would be, if the budget allows it, to hire professionals that will handle all the process before and during the launch of your software. But be prepared to provide them with all the data that they need, both on your company and on the software you are working on.
Failure to do so can have catastrophic results, as insufficient data can lead to an unsatisfied audience, poor coverage in the media, negative comments, and, ultimately, in your failure to reach your goal.
- Failure to pre-launch or to announce your software's launching. Don't just organize the launching event, and, when that day comes, expect it to be all peachy. It won't. Create awareness about your new software some time in advance. Let your prospective customers know that you're going to have a software product launch by means of newsletters.
Tell them a few things about the new product, not too much so as to spoil the surprise, but enough to capture their interest. Make sure you have a demo available so that they can actually see what it will be about. I also recommend this article about online software marketing methods giving hints on pre-launching software methods.
- Not analyzing the feedback you get on your beta version. If you release a beta version of your software so that you can see what potential users/customers think about it, make sure you are open minded and prepared to receive a lot of criticism. Look at it constructively, and don't take it personally. Even if some comments will be rude, keep in mind that most of them will help you notice the flaws of your software and thus allow you to correct them before the actual launch.
Some ways to get feedback are:
1. feedback survey
2. contact form
3. when uninstalling software (the user is asked for the reasons for uninstalling the program)
4. support forum
5. testimonials, etc.
- Not testing the product yourself. You have to put yourself in the customer's shoes. See how you feel when you use the software. Does it respond well to commands? Does it answer your needs? Here is an article, "The Other Side of the Interface" , which I personally enjoyed a lot. It provides helpful information about the psychological impact that computer software have on the overall perception of humans.
- Choosing the bad time for the launch. Most experts say that it is preferable to choose a day when most of the people you target are free, such as weekends. Also, it's best not to choose a day that also corresponds to a significant national or religious holiday. Don't neglect the time of day when the launch is scheduled. Make sure it's not too early or too late into the day. Otherwise, you will not be able to capture your audience's attention, as you should.
- Failure to get all the necessary resources for a successful launching event. Make sure you have everything covered, from featured speakers to catering (if applicable), from technology (computers, video projectors, etc.) to sound systems.
- Not giving enough time to your prospective customers to prepare. Bear in mind that you have to let people know about this event at least 2-3 weeks before its scheduled date. Give them time to make arrangements and to check their agendas for that date. Failure to do so can result in less people attending your software launch than you initially predicted, and thus diminishing your chances to make yourself known to a larger public.
Conclusion
Launching a software product implies a lot of effort, focus and dedication. Details are as important as ever, and overlooking any of them can have disastrous results. Make sure you dedicate a significant amount of time to planning the launch of your new product. The key is to be patient, as it may actually take more time that initially estimated to have the software ready for launch.
Really consider if you have the resources (human and financial) and the time to take care of everything yourself. It is far better to make an effort and spend some money of a specialized company that will take care of everything for you. Think of it as an investment, not as expenses. What you give now can and will return to you eventually. Take into account the fact that such companies have the experience and the know-how for such events, and after all, the possibility of something going wrong decreasing significantly.
Software Product Development Companies
Many executives and investors are skeptical that software products can be developed using outsourcing. Even more skepticism is expressed at the idea of outsourcing version 1.0 of a product. Yet Accelerance clients are using outsourcing to create their products right now. What is the secret to using outsourcing to successfully develop a software product?
Many people believe outsourcing is useless when you are in the Fuzzy Front End - that fuzzy zone between when a market opportunity is known and when serious software development can begin. They think you need to slog through the Fuzzy Front End by coding a prototype of your product. If so, you need the development team here, not several oceans away.
Another false assumption is that you need to write a comprehensive specification for your software during the Fuzzy Front End. Many companies use a very formal product definition process, optimized to remove as much "fuzz" as possible. How long should it take to design a software product before development can begin?
Obviously time is of the essence when developing a new product, but before the development process can begin you must have some idea of what your software will do. It is best to find this out from your prospective customers. But how can you involve your customers early and often in a collaborative process, when both of you are not sure of what they need or want? And what does that have to do with outsourcing?
According to Steve Blank, founder of several software startups and now lecturer at the Haas School of Business at Berkeley, you don't need a product development process. You need a customer development process. You need a process to discover what ornery problem your potential customers have that will cause them to part with their hard-earned money to solve that problem by buying your software.
The first step of Blank's customer development process is Customer Discovery. Here are his steps of customer discovery:
* Create a product (or product demo)
* Meet with customers and answer these four questions of customer discovery:
1. Have you identified a problem customers want to solve?
2. Does your product solve these customer needs?
3. If so, do you have a viable and profitable business model?
4. Have you learned enough to go out and sell?
* Change your product to reflect what you learn
* Iterate until all questions can be answered positively
Is there a way to shorten these iteration cycles? The Accelerance answer is, don't code up your product or prototype at the start. Use an HTML editor to create screen mock-ups. Then link them together to tell the "user stories" of your software product. They show the major use cases of your product. Demonstrating the use cases this way is like putting your product requirements in motion. It simulates how the real product will be used.
HTML is easy to edit and requires no programming. You can make quick iterations before committing your product ideas to code.
Here is the five-step Accelerance formula you can follow to successfully design your product:
1. Describe your product idea and its benefits
2. Create a demo of the major use cases showing the biggest benefits of your software
3. Perform the Customer Discovery steps described above, iterating until you & customers are satisfied
4. Write an MRD using screen shots from your demo as illustrations
5. Develop and test your software
In modern business, you should focus on your core competency and outsource the rest. In the Accelerance five-step process, the first 4 steps of defining your product idea, completing the customer discovery process and documenting the requirements must be part of your core competency. The last step is not.
Anybody can develop software. But only you can figure out what your customers will buy. And that makes your software development a non-core process. Use this five step formula to take advantage of low cost outsourcing as an effective way to get your product developed quickly.
Both Adriana Iordan & Steve Mezak are contributors for EditorialToday. The above articles have been edited for relevancy and timeliness. All write-ups, reviews, tips and guides published by EditorialToday.com and its partners or affiliates are for informational purposes only. They should not be used for any legal or any other type of advice. We do not endorse any author, contributor, writer or article posted by our team.
Adriana Iordan has sinced written about articles on various topics from Marketing, The Internet and Software. . Adriana Iordan's top article generates over 18100 views. to your Favourites.
Chain Saw Saw Mill So why pay extra for them? You can flush out a lot of these sorts of issues just buy reading the manual for the saw before you buy it