What is an MVP? A worked example

We help you Validate, Distill and Build an MVP in 20days… but what is an MVP?

What is an MVP?

You want to get started, but where and how, let us explain what an MVP is…

Today, we’ll focus on the what and why of an MVP, or a Minimum Viable Product.

What is a Minimum Viable Product [MVP]?

It’s the first public iteration of your idea – specifically, your value proposition. It embodies the process and logic you use to solve your user persona’s problem.

To explain the process of building and launching a tech product, let’s use a real project as a running example.

Introducing So What?

So What? is a web app designed to automate analysis in specific areas of interest, we will walk through the Ideate, Validate, Distill and MVP build of this product.

The Problem So What? is solving: Information Overload

We constantly strive to stay informed, but the sheer volume of data and reading material can be overwhelming. What truly matters isn’t consuming all the information; it’s extracting the So What?, the insights that come from all that reading. Why not use automation to generate this analysis, saving you time and making you the most well informed and insightful person in the room.

The Ideation Process

The idea for So What? was driven by the need for a real-world example for this blog series. Finding a single-track app (rather than a multi-track platform, single-track refers to a our solution directly serving our users, unlike a multi-track platform that services and connects multiple different user groups) that could be built and iterated on quickly was key. Another consideration was building a solution for a problem Dave (the author) personally faced. While not essential, this approach can increase your own motivation and ensure you can test and iterate accurately.

Validation: Testing the Concept

Brief discussions with colleagues and some initial development work helped validate the single-track app concept. It was simple enough to build quickly but also had potential for further development. While we did validate the concept, the core purpose behind this product was to act as a vehicle to articulate the product development process. Validation when done correctly can save you a lot of time, effort and money, this is where NascentX can help you.

Distilling the Idea: Identifying the Core Value. Distillation involves identifying the core logic required to deliver the smallest unit of value to the target audience. The initial idea became building a newsletter that delivered automated analysis tailored to individual interests. Let’s break down the key components:

  1. User management
  2. Email sending and automation
  3. Data capture to understand user context and interests
  4. Analysis logic
  5. Analysis delivery
mvp architecture
The MVP Architecture, distilled to the core logic we need to market test

Looking at this list, components like email, capture, and delivery are well-established and don’t require significant testing. They also aren’t central to our value proposition.

However, the logic to develop the analysis is crucial. This is where the value lies. We need to provide specific, relevant, and fresh insights. If this can’t be achieved in a user-friendly way, it’s back to the drawing board.

Shaping the MVP: Focusing on the Core

The MVP concept started to take shape. We needed to focus on the core analysis logic, test its viability, and gauge market need. We needed to build something to get us to where we are today.

So What? MVP v1: Live and Usable

Let’s explore what was built. Keep in mind, Dave built this in just three evenings!

Data Model and Design. The initial design featured a simple data capture form with preset personas and the ability to add custom tags for specific interests.

This form underwent several iterations before launch. Testing revealed that a form with too many variables reduced usability and the consistency of results. We learned the importance of balancing specificity with ease of use. You can see an image of this form below, compare it to the form we have live to see the contrast.

From Information to Insights: Leveraging AI

We have data input, but how do we generate relevant analysis? Information is plentiful; analysis asks the “So What?”. It takes time and effort to extract true insights. We can’t just present information; we need to present the “So What?”. Fortunately, AI can help us generate insights, but it’s not magic.

Testing and Refining the AI Engine

Local testing (on Dave’s laptop) helped ensure the analysis output from the AI was reliable. Early iterations showed that AI can sometimes “make things up.” This can be dangerous!

Dave ended up using a four-phase process to develop insights:

  1. Generate user context
  2. Generate a reliable data source for the AI (feeding it random data leads to unreliable analysis)
  3. AI prompting and analysis generation
  4. Insights output and presentation (presenting the AI output in a readable and actionable format)

The Current Stage: Gathering Feedback

We now have a live site (the Sowhat? MVP is here) that allows us to test our analysis logic and most importantly get user feedback. While the output still needs refinement, user feedback will be crucial in to the next iteration.

Getting people to use the platform and providing feedback is vital. Building is fun, but our ultimate goal is a viable product.

The Importance of “Basic”.  It’s important for an MVP to be viable, but the real focus should be on “minimal.” “Basic” is a better term in this context. Building a basic viable product helps ensure we aren’t over-engineering anything too soon. In this space we often hear founders say I just want something simple. Don’t confuse simple and basic; simple is hard, and basic is quick. The difference between an experienced software developer and a junior or less skilled developer is the ability to deliver simple code and logic.

Pursuing simplicity is a high [and expensive] bar; for your MVP, aim for basic.

The So What? MVP: A Basic, Viable Product

The So What? MVP is basic, with minimal frills. It’s viable because it provides actionable analysis quickly, and it’s a product. What is a product? A tool that solves a problem for your target audience. This MVP does that. Have a look at it here SoWhat? Link.

This MVP for So What? helps you quickly get analysis on topics you’re interested in.

Lets get feedback so we can iterate.

MVP feedback exampleA core component, maybe the most important bit, is enabling some level of user feedback… we achieve this through a simple voting format with a space for some free text for the user to share specific feedback points. 

 

 

 

The Next Iteration: Reaction, learning and Automating the Analysis Engine

The next step [and blog] is to automate the analysis engine. This will make the product even more efficient and valuable.

Dont wait get something out in the world. Building an MVP is a crucial step in the building your business. By focusing on the core value proposition and creating a basic, viable product, you can test your idea and gather valuable feedback before investing significant resources. Remember, the goal is to learn and iterate, not to create a perfect product from the start.

At Nascentx we want to help you Validate your idea, Distill it and then Build it so you can get feedback. Book a Validation workshop below…