What is the single most important factor you look for when building an MVP?

Function over form

Usability.

For MVP/MLP(Minimum Lovable Product) I usually don't prioritise or build first class features which can be executed manually with people involved. Think of MVP like a cool electric truck but driven by pedals. This improves go to market speed considerably for us.

When I'm building the MVP, I'm looking for a factor that can give enough value and get traction.

Learning from real users using your MVP in every phase to verify the direction of the product is key. Do not go to far if your users do not want that

great responses here... as far as lmbk + wtfh products we've worked to build community (discord) around prelaunches and conduct discovery w/ many of the community members who are engaged from the earliest stages of our prelaunch this guides the design/prod decisions we make always geared towards increasing velocity to 🚀 + cohort retention

Delta E: Change in Efficiency.

I define the problem, and I make sure my MVP solves that problem in the fastest, cheapest way possible. The thought process goes: Ok this is one way to solve the problem, what's a faster, cheaper way? On repeat, ask people around you, then ask the question again.

The adaptability of processes. How quickly and cheaply can you change how things work is super important I'd be curious to hear what people think on low vs high fidelity of a product Cheers!

I recently heard a different version of this term that I really like: Minimum Buyable Product. What is the smallest thing you can build and get people to buy? Nothing else really matters and is conjecture until you get other people giving you money, so use that as your north star.

iterative feedback at every step along the way. finding out how your potential customers actually experience your MVP will be the light at the end of every tunnel when it isn't clear what to do next. listen to them, let them guide you, and don't ever build too much before you get their take on the matter.

Definitely the value - once we have defined the problem, the MVP has to provide enough value for early users to adopt it and give the right inputs & feedback to move to the next stage.

When building an MVP, the most important factor to consider is to create a product that solves a real problem for your target audience. This means understanding the customer's pain points and creating a product that addresses them in a meaningful way. By focusing on the most critical features that solve the problem, you can get your product to market faster, test your assumptions, and validate your product's market fit. It's also important to gather feedback from users and stakeholders throughout the development process to ensure that the MVP is meeting their needs and expectations. By staying flexible and responsive to feedback, you can make the necessary adjustments to improve your MVP and set the stage for future growth and success.

Speed to launch

Business Value. It can have flavors based on your backlog and customers. But you will need to define the value for your business first so that your MVPs are also valuable.

Data understanding

When I'm building an MVP (Minimum Viable Product), the most important thing for me to consider is value. I want my MVP to offer enough value to users that they'll actually want to use it, even if it's not fully finished yet. Other things I think about include whether it's feasible to build within my available resources, how quickly I can get it to market, and how risky it is to build and launch. The goal of an MVP is to test and validate my product idea, get user feedback, and iterate based on that feedback. So I focus on delivering the core value proposition of my product as fast as I can.

What does the "V" stand for in MVP? "Viable - capable of working successfully." - which I think is just simply not enough for what we know an MVP should be. Just because something works, it doesn't mean it will either solve a problem, or anyone would want to buy it. You want to build that one solution that solves a problem big enough for someone wanting to pay for it, even if it's just cents; if you find enough people to buy it, you've got cash flow! Focus on that one thing, and your product will grow.

When it comes to building a Minimum Viable Product, I believe the most important factor is iteration. This goes beyond simply developing a product as fast as possible; instead, I think it’s critical to build something that solves the customer’s core problem but also allows for testing and gathering feedback to make sure you are on the right track as you develop additional features and services. Iterating over time not only reduces risk since you can test out different assumptions quickly, it also ensures the product or service is well-tailored to what the customer needs and wants. Building an MVP with iterations in mind is essential for any successful venture!

There can be many answers to this. But "launch quickly" is step one Michael Siebel says in his talk on Y-combinator. link: https://www.ycombinator.com/libr...