What’s a Minimum Viable Opportunity (MVO)?

July 7, 2025

DSA Team

Most teams obsess over the MVP — the smallest version of a solution they can ship to test if customers will use it. The Minimum Viable Opportunity (MVO) is the name for the question that comes before that: what is the smallest, clearest version of a problem actually worth solving now? This article explains what MVO means as a piece of vocabulary, how the term changes the conversation in a senior leadership room, and where it sits alongside the methods that produce one.

You will leave with a working definition of MVO, the side-by-side framing against MVP, the case for why senior leaders should care about having a name for the upstream filter, and the language to defend the spend on the work that produces it.

🧰 Want everything you need to find your team's MVO? Get the 4U Workshop Kit — the complete program for running the two-hour 4U Workshop with your stakeholders.

The question senior leaders should be asking before "what should we build?"

In most product and innovation conversations, the question on the table is some version of what should we build, and how fast can we ship it?

That question has its place. It is the right question once a team has agreed on the problem. The frameworks built around it — MVP, RICE, ICE, Impact–Effort matrices — are all designed for the moment after the problem has been chosen.

But they all share an assumption that, in our experience, frequently does not hold: that the team has actually agreed on the problem in the first place.

Most have not. They have agreed on a vague theme, a senior leader's hunch, or a backlog that has accumulated rather than been chosen. The room moves into solution mode anyway, because that is where the energy is. By the time anyone notices the problem was never properly framed, the budget is committed and the team is three sprints in.

The move that prevents this is a different question, asked one step earlier: Are we even solving the right problem?

That question is what the Minimum Viable Opportunity is designed to answer.

What is a Minimum Viable Opportunity (MVO)?

A Minimum Viable Opportunity (MVO) is the name for the smallest, clearest version of a problem worth solving now — based on urgency, business impact, and user need.

It is a piece of vocabulary, not a method. The MVO is the outcome a senior leadership team agrees on when they take the time to filter many possible problems down to the one worth committing real resources to. It is the pre-MVP filter: the decision that should sit before any team commits to building a solution.

MVO is taxonomy, not methodology. There is no "MVO framework" or "MVO workshop." Think of MVO the way you think of north star metric — the term names a thing senior leaders already work toward; it does not prescribe how to get there. The MVO names what the leadership group is trying to identify. The method that produces it is the 4U Workshop, covered further down and in the linked companion articles.

The word opportunity matters. An MVO is not a problem the organization happens to have. It is a problem the leadership has examined and decided is worth real investment — timely enough to act on, important enough to fund, and clear enough to hand off to a delivery team.

Four questions tell you whether a candidate problem qualifies:

Is this a real problem — something customers or the business actually feel, not just an internal hypothesis?
Is it strategically important — does solving it move a metric the leadership team is accountable for?
Is it urgent or unavoidable — is now the moment to act, or can it wait?
Are we in a position to do something about it — do we have the team, the access, the data, and the political authority to commit?

A candidate that lands cleanly on all four is an MVO. A candidate that lands on two or three of the four is a candidate for deeper investigation. A candidate that misses on most is a problem the team should not be solving yet — regardless of how loudly any individual leader is pushing it.

The MVO is what the team should agree on before anyone draws the wireframe.

MVP vs MVO: what's the difference?

The two concepts sound similar. They do different work. Most teams who skip the upstream filter are not making a bad MVP — they are making a perfectly good MVP for a problem nobody validated as worth solving.

A simple way to hold both in mind:

The MVP asks: What is the smallest version of this solution we can build to test whether people will use and pay for it?
The MVO asks: What is the smallest, clearest version of a problem we have agreed is worth solving now?

The MVO sits one step upstream. It chooses which problem the team is going to validate. The MVP then validates the proposed solution to that problem.

Run in sequence, the two work together:

MVO — the leadership group identifies a problem clearly worth investing in.
Problem Framing — a deeper one-day workshop turns that problem into a validated problem statement.
MVP — a delivery team builds the smallest version of a solution that tests whether the framed problem can be solved.

Skipping the MVO step is what produces well-built MVPs that nobody needed. The product works. The metrics are reasonable. But the team has tested a solution to a problem the business never confirmed was worth the investment in the first place.

Naming the upstream filter — calling out the MVO as the thing the leadership group still needs to agree on — is what prevents that failure mode.

Why most teams skip the upstream conversation

The pattern is familiar to anyone who has been in a leadership room when priorities are being set.

The team jumps from brainstorm to backlog. They score features using RICE or ICE. They run Impact–Effort matrices. They debate trade-offs and feasibility. The conversation feels productive — there are frameworks, the room is engaged, decisions are being made.

But all of those tools share a starting assumption: that the team has already agreed on which problem they are solving. None of them tests that assumption. They organize the work inside the problem. They do not validate the problem itself.

The practical consequence is what most senior leaders eventually learn the hard way: the most expensive mistakes inside well-funded organizations are not failed projects. They are well-executed projects that should never have started. The team shipped on time. The product worked. The metrics moved a little. But the underlying problem was never serious enough, urgent enough, or strategically important enough to justify the resources behind it.

Three dynamics make this hard to catch in the moment.

The people closest to the work are often disconnected from the business reality. They are smart, creative, and eager to move — but thinking creatively is not the same as thinking strategically. Holding both lenses at once is rare. Without business context in the room, the team optimizes the wrong thing well.

The loudest voice tends to win. Whoever pitches the problem with the most conviction often sets the agenda. That voice is rarely calibrated to the business. It is calibrated to the leader's own KPIs, their own function, their own pressure to deliver visible activity this quarter.

Saying no is harder than saying yes. Every initiative has a sponsor. Saying no to a sponsored initiative is politically expensive. So the team says yes — let's add it to the backlog, and the backlog grows until nothing on it gets the depth of resourcing it actually needs.

Naming the upstream filter is what cuts through all three. When the leadership group has a shared term for what they are trying to find — an MVO, the problem worth solving now — the conversation reorganizes itself around that target. The business context comes back into the room. Structured scoring replaces the loudest voice. And the group gets a defensible basis for the things they decide not to do.

What does naming the MVO unlock for a senior leader?

Having a shared term for the upstream filter is not just an editorial improvement. For a senior leader carrying responsibility for what the team builds next, the MVO label produces three things that are difficult to get without it.

A defensible decision the leadership group co-owns

The scored opportunity is no longer one leader's bet. It is a decision the leadership team built together, with visible criteria, in a structured session. When the CFO, the VP, or the board asks why this and not something else, the answer is we identified this as our MVO — a specific, named outcome on the wall — not a deck someone built afterwards to justify a decision already made.

Fewer initiatives, with more depth of investment

Sessions oriented around finding an MVO almost always produce a shorter list, not a longer one. Two or three opportunities co-owned by the room is a stronger position than fifteen low-conviction initiatives competing for the same budget. Naming the target forces the conversation about what the organization is not going to do — which is where the time and money for the few high-impact problems gets freed up.

Faster validation downstream

A properly identified MVO produces a Problem Framing workshop that runs cleaner, an MVP that tests the right thing, and a delivery team that knows why the work matters. The two hours invested upstream pay back across every workshop, every sprint, and every roadmap conversation that follows. Most leaders measure this as a reduction in time from idea to validated decision — and the gain is usually significant.

How do you find an MVO?

You find an MVO by running a 4U Workshop. The 4U Framework — Unworkable, Unavoidable, Urgent, Underserved — is the named method. The MVO is the named outcome. A two-hour session, six to eight senior stakeholders, two to four candidate problems scored against the four lenses; the pattern across the scores reveals whether one of the candidates is an MVO.

Not every 4U session yields an MVO. The workshop has three possible outcomes:

A clear MVO emerges — one or two candidates score strongly across multiple dimensions, the room co-owns the decision, and the top problem moves into Problem Framing or focused validation.
Candidates worth investigating, but no clear winner yet — problems score high on some dimensions, but the room cannot yet commit. The output is a research agenda, not an MVO.
Nothing strong enough — no candidate clears the threshold. The session has just saved the team months of misdirected work, and the right next move is to bring better candidates to a future session.

All three outcomes are useful. Only the first is an MVO.

The four lenses, briefly:

Unworkable — if the organization does nothing, what breaks?
Unavoidable — is this problem one external pressure will force onto the business anyway?
Urgent — is this the right moment to act, or can it wait?
Underserved — is there a real gap in current solutions, or is the market already well served?

Leaders score each dimension individually, before the room discusses anything. The pattern across the four scores tells you whether the candidate is an MVO — usually a problem strong on three or four dimensions, owned by a leader who can commit resources to it next.

Three things make the session work:

The right people in the room. Six to eight stakeholders who hold budget authority, decision-making power, and a real interest in the candidates. Cross-functional perspective matters — product, technology, marketing, sales, operations, customer, or strategy. A single-function room produces a single-function answer that the rest of the organization will quietly ignore.
Structured scoring, not open debate. Every leader scores individually before anyone speaks. The loudest voice should not anchor the room. The disagreements between scores are where the real conversation lives.
A documented decision within 48 hours. The MVO is fragile in the days after the workshop. A one-page summary of what the room scored, what the top opportunity is, and what the next step is — sent to every participant within 48 hours — is what hardens the decision before it can quietly drift.

The full mechanics of running the 4U Workshop, the facilitation moves that protect it, and a worked example of a $1.75 billion failure the workshop would have caught are covered in the companion articles linked at the end of this piece.

Where the MVO fits in the broader product workflow

MVO is not a replacement for strategy. It does not redefine the company's north star, restate market positioning, or rebalance portfolio-level bets. Those decisions sit above the MVO and shape which candidate problems are even in the running.

What MVO does is make strategy actionable at the level of what the team is going to invest in next. It is the bridge between strategy (where we are going and why it matters) and delivery (what the team is building this quarter).

The sequence looks like this:

Strategy sets the direction — markets, segments, big bets.
MVO picks the next problem to investigate — using the 4U Workshop to score candidates.
Problem Framing validates the chosen problem — a full one-day workshop turning the MVO into a clear, evidence-backed problem statement.
Design Sprint or MVP validates the solution — testing whether the team can solve the framed problem in a way customers will adopt.
Delivery executes — building the validated solution at scale.

Most organizations have strategy in place. Most have delivery in place. The gap that consumes the most resources is in the middle — the place where strategy is supposed to become a specific bet, and rarely does. Naming the MVO is what closes that gap, by giving the leadership group a shared target to look for.

Start by identifying your MVO

If your team is sitting on too many priorities, debating a big bet that keeps getting postponed, or about to commit budget to a problem that has not been properly examined, the lowest-risk first move is to propose a two-hour 4U Workshop. Identify the right six to eight stakeholders. Curate three or four candidate problems. Score them against the four lenses. Walk the room out with at least one high-impact opportunity the leadership group co-owns — your MVO — and a defensible reason for parking or killing the rest.

The value of the session is not the scored output. It is the upstream conversation it forces — about whether the problem is worth solving in the first place. That conversation is what separates organizations that ship real impact from organizations that quietly ship things that do not matter.

Your Cart