# Minimum Viable Product: Start Small on Your Next Technology Project

Strategy · September 11, 2025 · Updated  · November 11, 2026 · 4 min read

Many technology projects at venues and arts organizations fail slowly. A new website, a custom purchase path, or a CRM integration takes months to build, and the first time real users touch it is the day it launches. By then the budget is spent and every wrong assumption is built in.

A minimum viable product, or MVP, is the way around that. It is the smallest release that solves one real problem for real users, built so you can learn from it before you commit to the rest.

## What an MVP is

An MVP is the simplest version of a product that does one job well enough to be useful. “Minimum” means you cut everything that job does not need. “Viable” means what remains has to work in real conditions, with real data, for real people.

An MVP is not a mock-up, and it is not a rushed, half-finished version of the full build. The term was popularized by Eric Ries’s book [The Lean Startup](https://www.penguinrandomhouse.com/books/210088/the-lean-startup-by-eric-ries/), which treats it as a way to learn what customers actually want before building everything.

## Why it suits venue and arts technology

Technology projects in this world carry their own pressures:

-   **Fixed dates.** An on-sale, a season launch, or a gala does not move, and a late project misses it.
-   **Shared systems.** The ticketing platform, CRM, website, and payment tools all connect, so one change can affect the others.
-   **Small teams.** Staff have limited time to test, train, and give feedback.
-   **High stakes at peak moments.** A failure on an on-sale morning is public and costly.

A smaller first release lowers all four risks. You can try it with one show, one audience segment, or one department before it touches the whole organization.

## What a small first release looks like

-   **One job, done well.** The connector we built for [The Hanover Theatre](https://lockdata.com/case-study/the-hanover-theatre/) does one thing: it pulls the classes on sale in AudienceView into the website as drafts for staff to review. It replaced a process of typing the same information twice.
-   **MVPs inside a roadmap.** On a large manufacturing modernization, we started with discovery, built a roadmap, and defined MVPs before executing the wider work.
-   **One data type first.** A CRM integration can start by syncing new ticket buyers, then add donations, memberships, and event attendance once the first sync is trusted.
-   **One show first.** A branded checkout can launch for a single production and expand to the season after you have watched real buyers use it.

The last two are illustrations of the approach, not specific client projects.

## How to scope one

1.  **Name the one problem, and who has it.** “Box office staff re-key class listings” is a problem. “Improve our digital experience” is not.
2.  **Decide how you will know it worked.** Pick a measure before you build: hours saved, abandoned carts, time to publish.
3.  **List the features, then cut.** Keep only what the problem needs. The MoSCoW method (must have, should have, could have, won’t have) is a simple way to sort the list.
4.  **Build it on real data.** An MVP that runs on sample data teaches you little. Connect it to the real system, even if the scope is narrow.
5.  **Release it to a small group.** One team, one show, one segment. Watch how they use it.
6.  **Decide what happens next.** Expand, change, or stop. Set that decision point before you start, so the pilot does not drift into an unfinished product.

That is how we approach pilots, including our AI work: one problem worth solving, a clear measure of success, and a decision point before anything larger is built.

## Where an MVP is the wrong tool

Some parts cannot be minimal. Payment handling, security, and anything that has to hold up on an on-sale morning need to be complete and tested before launch, whatever else you cut. A small scope also does not excuse a weak foundation. Build the first release so it can grow, with sound data and integration choices underneath.

The other common failure is scope creep. An MVP that quietly collects every request from every department stops being minimal, and you lose the learning that justified it.

## Next step

If you have a project that feels too big to start, our [discovery work](https://lockdata.com/services/discovery-consultancy/) is built for this: finding the first release worth building and a plan for the rest. For the build itself, see our [custom software development](https://lockdata.com/services/custom-software-development/). Or [tell us what you have in mind](https://lockdata.com/contact/).

-   Brian Davailus
-   Patrick Joyce
-   Peter Prigge
-   Cody Dosch

Employee-owned team

## Got a question about something you read? Ask the people who wrote it.

Every article comes from the team building this work every day. Tell us what you’re working on and an expert will reply within one business day.

[Talk to an expert](https://lockdata.com/contact/)

[hello@lockdata.com](mailto:hello@lockdata.com)[570.226.7340](tel:+15702267340)

## Keep reading.

[All insights](https://lockdata.com/blog/)

-   Ticketing

    ### [How to get your website ready for a big on-sale](https://lockdata.com/blog-post/on-sale-readiness-checklist/)

    4 min read

-   Ticketing

    ### [Fixing the Ticket-Buying Experience: A Four-Step Approach](https://lockdata.com/blog-post/fixing-the-ticket-buying-experience/)

    4 min read

-   Company

    ### [LockData Is Now Employee-Owned](https://lockdata.com/blog-post/lockdata-employee-owned/)

    4 min read

Source: https://lockdata.com/blog-post/the-power-of-mvp-why-launching-small-can-lead-to-big-wins/
