Sharkes Monken

I'll start: I'm prepping for my PH launch, so I'm working on having ready the product video and images, first comment, and answers to common questions. Also improving the onboarding and updating help docs and video guides. Your turn

In the mean time we have many tools in our that interrupt my work: Slack, Gitlab, Email, Trello, etc. All these plattforms are always open in my computer and send me constant interruptions. On the one hand I rely on them for stuff like alerts and failed software integration pipelines, on the other hand I don't have hours of uninterrupted work anymore. What are your strategies? How do you find a middle ground of being reachable and being focused?

The concept of testing product ideas before building a fully-functional product is a new normal. From 3-person startups to 1000+ people enterprises everyone is building MVPs now Product owners at almost every team can evaluate what would be "nice-have" and what would be "must-have" MVP features, backing their findings with some data. But with millions of MVPs released, how can your stand out? What will make it a "fail" or "success"? When browsing Product Hunt, we see such a strong competition but only a few MVPs get people's love. And I'm not talking about magic product-market fit. I'm talking about something as simple as .... making people go open your website from all PH hunts and try that thing you build for the last 2 months. How to achieve it? Here are my learnings: 1 Start with the user and competitors' research. If you don't know for whom you are doing your product and how you are better nothing will save your MVP from the fiasco. I bet, most of the first-time founders skip research because "we already know what to build". It's so wrong. 2 Make that value prop clear and loud. Your Product Hunt headline, description, value prop on the website if it doesn't resonate with the user needs, then no one will even bother to open your website. Even for a creepy MVP, do your homework with value proposition and positioning. Don't make it "the last thing to put together from copied parts of competitors' offerings". 3 MVP is not "it works somehow" It's not 2012, it's 2022. We all work with tons of apps and we are used to a certain level of comfort when using something. If MVP is hard to register, hard to navigate via the website, hard to use, buggy, slow well, we will close that app and will write the founder under his PH post "good job, congrats" and will never use it again So, yes, it's"minimum" but "minimum good" comparing to other products. 4 Good UX is a must. MVP can not look horrible and feel horrible unless it's someting as important as medicine which saves people's lives. 5 Attracting early adopters is your job. Building a good MVP is important but "good MVP" does not guarantee that people will pay attention to it. Product-led growth is a real driver BUT for products that nailed a huge market need on a growing market with a low/zero competition and viral elements inside the product itself. And even those companies spent a lot of attention to marketing. So successful MVP of 2022 goes with GTM plan 6 Customer service from day 1. At this point, you probably think that my concept of MVP goes again the concept of "minimum". However, the "good service" can be done by a caring founder who replies to all requests and honestly tries to help all MVP users navigate to the product value. This list can go on, so please add your thoughts on what makes "MVP of 2022" successful And if you need help with building MVPs with no-code, fast and affordable, our team can help: http://welovenocode.com/