Understanding Minimum Viable Product (MVP)

Jarrod Lodge
Jarrod Lodge
May 12, 2026
Understanding Minimum Viable Product (MVP)
Understanding the Minimum Viable Product (MVP) is a critical step in developing your digital solution.

An MVP is an early version of a product or solution, such as a mobile app, which is designed to ensure that the product vision and strategy can meet both user needs and business outcomes. Your MVP has the absolute minimum functionality needed to test your idea.

We build something fast, with the minimum features to validate that people want our product.

http://localhost:3001/api/media/file/Validated_Learning_Loop_2f74cbe1c8.png?prefix=media
BML: MVP is a critical step in the Build, Measure, Learn loop.

What is the minimum?

The minimum differs for every product or solution and depends on the problem that needs to be solved and the desired business outcomes. Based on our extensive experience in software development, user experience and design we work with you to understand what the minimum is. Defining the smallest number of capabilities, features, functionality and packaging needed to get your solution out for validation is the first step in the BML loop.

http://localhost:3001/api/media/file/Viable_Product_890377c5bc.png?prefix=media
Viable: Product is viable through each stage of development. Top is not

What does it need to be viable?

Whether developing a commercial product or a digital solution for internal use, viability is defined by either delivering enough value that customers are willing to spend money or addressing pain points well enough to get buy-in and uptake from target users.

For it to be viable, people need to be able to use it.

An app product is ready to use

The MVP delivers value and starts gathering data on usability right away - avoiding significant investment in building a product or solution that doesn’t deliver on desired business outcomes or user needs..

Calo’s MVP Approach

  • Understand: We dive deep through workshopping your objectives and take you through our process to discover what the MVP needs to deliver. This means developing a shared understanding - we understand your goals and desired outcomes and you understand the digital landscape and what is possible and practical
  • Scope of works: We need to make sure we are on the same page, so by understanding the businesses objectives we can define features and deliverables for the MVP
  • Design / Mockup: We design and deliver a mockup to illustrate the visual presentation and the functionality of the product. These mockups can be used to visually test the ideas and confirm we have addressed the scope. This process is the first use of the BML loop in developing the solution
  • MVP built or extended: Once the design and mockup are approved the MVP/ prototype is built
  • Testing, validating: Initial users put the prototype through rigorous real-world testing. Using tools to measure use and performance, and user feedback we gather data to validate the MVPs premise

Persevere
If the testing shows that the MVP aligns with business and user needs the next step is to continue with the same goals and continue the feedback loop of build - measure - learn to continuously improve and refine the product or solution. There will come a point in this loop where there is enough data and functionality to build out the product and take it to a wider audience, however the BML loop continues throughout the lifetime of the product.

Pivot
The data gained from testing can tell a different story to the intended user experience or business outcomes. While this can be used to tweak the app to make it more aligned with the original plans, processing this data with an open mind can lead to a pivot to unexpected uses and opportunities.

For example, while Instagram wasn’t designed as a photosharing app, the innovative use of filters is what caught users' attention, leading to one of the most well-known examples of a pivot, building Instagram.

The pivot could be developing a single feature of the MVP, changing the customer focus, delivering through a different channel or using a successful feature as the basis of a different product.

Images used above are from a book I highly recommend called User Story Mapping by Jeff Patton. His website is here

Published May 12, 2026
Share:

Related Posts

Inspiring the Next Wave of Innovators at the Clutha Careers Expo

Inspiring the Next Wave of Innovators at the Clutha Careers Expo

Calo recently participated in the Clutha Careers Expo as the sole software development company present. The team focused on inspiring local students by demystifying the tech world, showcasing how a career in software is a creative, accessible, and impactful path focused on solving complex problems and helping people perform better.
Read More →
Hacking the Proposal: An AI Workflow for Developers Who'd Rather Be Coding

Hacking the Proposal: An AI Workflow for Developers Who'd Rather Be Coding

This AI-augmented process has cut my proposal drafting time from 2-4 hours down to less than one. But the real victory isn't just the time saved; it's about reclaiming my focus and energy. It allows me to get back to what I love doing: **writing code and solving problems**.
Read More →