Whether you’re a startup that is working on a new game-changing innovation or an established company adding a product to your growing portfolio, you likely experience a very common and real issue: \u00a0You’re not quite sure if the product you’ve been working on is ready to be launched.<\/p>\n
On one hand, many people feel that getting their product out into the real world as early as possible is the best route, as it allows you to replace internal hypotheses with fact. \u00a0After all, once people start using your product and giving you real feedback, any assumptions you’ve made can actually be tested. \u00a0You can truly understand whether your product is solving the problem you set out to alleviate.<\/p>\n
Of course, you can only launch a product once. \u00a0Therefore, there are many that feel that every last detail should be ironed out before launching. \u00a0Every potential issue or possible problem should be thought about and planned for. \u00a0Then, and only then, should a product even be considered ready for prime time.<\/p>\n
While these are two ends of the spectrum, neither is necessarily right or wrong. \u00a0It’s true that you should have a well-thought out product plan and your launch should be green-lighted when you’ve accomplished your plan. \u00a0However, you should also realize that not every detail can be resolved or even imagined\u00a0before launch. \u00a0As the quote by Mike Tyson goes, “Everybody has a plan until you get punched in the face.” \u00a0You should realize and even assume that once your product is launched, there are going to be times where it feels like you’re getting punched in the face. \u00a0No matter how many times you’ve thought through certain scenarios, know that certain issues will arise that will simply never have been thought of before.<\/p>\n
Regardless of what end of the spectrum you feel like you fall on when considering a product launch,\u00a0there are three things that you absolutely should do before considering launching any product — whether it’s physical or digital:<\/p>\n
1. \u00a0Understand the real problem you’re trying to solve.<\/strong><\/p>\n This may sound very basic, and it is. \u00a0But so many times products are launched without actually solving a problem that exists in the real world. \u00a0Instead, they are solutions first — without a real problem to solve. \u00a0If you’re unsure if the product you’re developing is actually solving a real problem,\u00a0ask yourself this question: \u00a0What was the genesis for the creation of this product in the first place? \u00a0How did it actually begin<\/em>? \u00a0Was it an issue or roadblock that somebody kept running into? \u00a0Or, was it a brainstorm of “Hey, what’s the next new cool thing we could launch?” \u00a0If it’s the latter, you may want to take a giant step back and do some soul-searching. \u00a0If your product isn’t alleviating a problem for somebody, it may be very difficult for people to see through to your value proposition. \u00a0This doesn’t mean that you should scrap that product. \u00a0But you may take some different approaches with design or consider different features once you’ve realized the true problem you’re solving.<\/p>\n 2. \u00a0Get face to face with customers.<\/strong><\/p>\n The only way that you can understand if you’re solving a real problem is to talk to the very people with<\/em> that problem. \u00a0Identifying your target base of potential customers and literally talking to them is critical, and no launch should take place unless you’ve had several conversations with these potential customers. \u00a0Also, by talking with customers — I mean just that. \u00a0I’m not talking about holding a formal focus group or sending out surveys. \u00a0Those things could be helpful, too. \u00a0But regardless, you should have real-life conversations with actual, real-life customers. \u00a0Understand where they’re coming from. \u00a0Learn more about the problem that your product is trying to solve for. \u00a0You’ll learn so much more about the context of their problem once you have a real conversation with them. \u00a0Have the conversation in a setting that they’re comfortable with — ideally, with context to the problem you’re trying to solve. \u00a0For instance, if you’re developing a new detergent — perhaps the conversation could be in their laundry room. \u00a0If you’re developing a mobile app for travelers, perhaps you could have the conversation in a city’s visitor center. \u00a0Regardless of where you have the conversation, be sure that you have the conversation. \u00a0<\/em><\/p>\n 3. \u00a0Put a\u00a0prototype in your customers’ hands.<\/strong><\/p>\n Now that the lines of communication are open between you and real-life customers, open it back up once you get to the prototype stage. \u00a0After all, it’s not enough to know that your product is intending to solve a problem that actually affects your customers. \u00a0You should get feedback on whether your solution is just that — a solution. \u00a0Allow customers to give you this feedback well before you launch into the real world. \u00a0When you put a prototype in your customers’ hands, you’ll quickly get a sense of where they’re gravitating towards. \u00a0You’ll see first-hand what features and attributes actually resonate with them, and which are overlooked. \u00a0These nuances are important, as you could quickly see if you need to go back to the drawing board, or if you’re on the right track.<\/p>\n Yes, it’s true that some things can\u00a0only be learned once you launch your product into the real world. \u00a0And getting to that point\u00a0requires a lot of focus and dedication. \u00a0But don’t do it in a vaccum. \u00a0If you ensure that you’re doing these three things before<\/em> you launch your product, you’ll be in a much better place once your solution is out in the real world.<\/p>\n","protected":false},"excerpt":{"rendered":" Whether you’re a startup that is working on a new game-changing innovation or an established company adding a product to your growing portfolio, you likely experience a very common and real issue: \u00a0You’re not quite sure if the product you’ve been working on is ready to be launched. On one hand, many people feel that […]<\/p>\n","protected":false},"author":3,"featured_media":14953,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[208,209,207],"yoast_head":"\n