Minimum Viable… for Who?

Dr. Candace Hayden

IT'S ME — THINKING OUT LOUD!... Who buys something that isn’t finished? I don’t ask that as a gotcha. I’m not trying to be clever with it. I’m asking because it’s one of those questions that sounds simple, and then the longer you let it sit there, the more uncomfortable it becomes.

Dr. Candace Hayden

In technology, we’ve gotten very used to a certain kind of language that softens reality. We say beta. We say early access. We say version one. And maybe most commonly, we say MVP — minimum viable product. That phrase has been around long enough now that people hear it and almost stop interrogating it. It sounds reasonable. Practical, even. Responsible.

Dr. Candace Hayden

And sometimes it is. I’ve worked through enough product cycles to understand why the idea took hold. You don’t want to overbuild. You don’t want to sink time and money into something nobody wants. You want signal before scale. All of that makes sense to me.

Dr. Candace Hayden

But what I’ve been thinking about lately is not the original idea. It’s what the term has come to mean in practice. Because in practice, MVP has drifted. Not everywhere, but enough that I notice it. Enough that it affects how products are built, how they’re sold, and how expectations get managed — or not managed.

Dr. Candace Hayden

So this is really a reflection on that gap. The space between what MVP was supposed to protect us from and what it sometimes now permits. I’m not against iteration. I’m not against moving quickly. I’m definitely not arguing for perfection before release. That’s not realistic either.

Dr. Candace Hayden

I’m just trying to look at the word honestly. What are we actually describing when we call something viable? Viable for whom? The team building it? The investor funding it? The market testing it? Or the person paying for it and trying to rely on it?

Dr. Candace Hayden

IT'S ME — THINKING OUT LOUD!...

Dr. Candace Hayden

At its best, MVP is a discipline. It’s a way of testing an idea quickly without pretending you already know the answer. You build enough to learn. Not enough to perform certainty — just enough to see whether the thing solves a real problem in a real setting.

Dr. Candace Hayden

That original logic is solid. Reduce risk. Shorten feedback loops. Avoid overengineering. Learn what matters before you commit to scale. I mean, that’s not bad thinking. That’s mature thinking. Especially in environments where resources are limited and assumptions are expensive.

Dr. Candace Hayden

A good MVP, in that sense, is not sloppy. It’s selective. It says: we are choosing the smallest expression of this idea that can still teach us something useful. There’s restraint in that. There’s humility in that too, because you’re admitting you do not fully know yet.

Dr. Candace Hayden

And feedback is part of the point. Not abstract feedback, not people saying they like the concept in theory, but actual interaction. What do users do? Where do they hesitate? What did we assume incorrectly? What needs to be changed before this becomes something more durable?

Dr. Candace Hayden

So no, I don’t think the concept itself is flawed. I think it’s often one of the more sensible ideas product culture produced. It recognized that learning has value. That speed can be useful. That smaller bets are often wiser than dramatic launches built on confidence alone.

Dr. Candace Hayden

The issue, for me, starts later — when the language stays the same, but the intent changes.

Dr. Candace Hayden

Somewhere along the way, in a lot of settings, MVP stopped being about testing and started becoming a way to sell. That’s the shift I keep noticing. What was meant to be a stage in development gets presented as the thing itself.

Dr. Candace Hayden

And that changes the ethical shape of it. Internally, an unfinished product is a learning tool. Externally, it becomes an offer. A promise, even if nobody says the word promise out loud. Once you put a price on it, once you ask someone to depend on it, you’re in a different kind of relationship.

Dr. Candace Hayden

I’ve seen this move happen gradually. First it’s, we just need to validate the idea. Then it becomes, let’s put it in front of a few users. Then, well, maybe we can charge a little. Then suddenly the MVP is not a prototype with boundaries. It is the product in the eyes of the buyer.

Dr. Candace Hayden

That’s the part that feels off to me. Not because early versions should never be seen. They should. But because the framing changes quietly. The incompleteness remains, while the positioning becomes more confident. The caution stays on the inside. The certainty goes to market.

Dr. Candace Hayden

And when that happens, MVP stopped being a stage and started being the offering. That’s a very different use of the term. It sounds similar on paper, but operationally, and relationally, it is not the same thing at all.

Dr. Candace Hayden

I think that’s why some people feel uneasy around the phrase now, even if they can’t quite explain why. They’re not reacting to iteration. They’re reacting to a mismatch between what’s being built and how it’s being represented.

Dr. Candace Hayden

And underneath all of this is a pretty basic question: who is carrying the risk? Because that’s really the tension.

Dr. Candace Hayden

On the builder’s side, there is still uncertainty. They’re still figuring things out. The logic may not be stable yet. The workflows may still be shifting. The edge cases probably are not understood. That’s normal in early development. I’m not criticizing uncertainty itself. Building always contains uncertainty.

Dr. Candace Hayden

But on the buyer’s side, the experience is different. They’re paying money, investing time, adjusting process, maybe even changing behavior around a tool they assume is ready enough to trust. They may not need perfection, but they do need some reasonable alignment between what is claimed and what is actually there.

Dr. Candace Hayden

So the issue isn’t that one side knows everything and the other doesn’t. The issue is that the uncertainty is often retained by the builder while the consequences are transferred outward. The builder gets learning. The buyer absorbs friction.

Dr. Candace Hayden

Again, I don’t say that accusingly. Sometimes this happens because teams are moving fast. Sometimes because language gets reused without much thought. Sometimes because everybody in tech has become so accustomed to incompleteness that they forget not everyone interprets it the same way...

Dr. Candace Hayden

Still, the mismatch matters. One side is saying, in effect, we’re still discovering what this is. The other side hears, this is ready enough for me to integrate into my work, my business, maybe my decision-making. Those are not equal expectations.

Dr. Candace Hayden

And if we don’t name that clearly, trust gets stretched in ways it probably shouldn’t.

Dr. Candace Hayden

This gets sharper when real money enters the picture. Not symbolic money. Not a nominal fee that obviously signals experimentation. I mean substantial money. The kind that creates expectation whether anyone intends it to or not.

Dr. Candace Hayden

What does it mean to charge ten thousand dollars — or any significant amount — for something still being developed? I think that’s the question people often avoid by staying inside startup language. Because startup language can make nearly anything sound provisional and strategic at the same time.

Dr. Candace Hayden

But buyers do not experience invoices as theory. They experience them as commitment. If they’re paying serious money, they are usually buying more than access. They’re buying confidence, or at least they think they are. They’re buying the expectation that someone has already done enough thinking to justify the ask.

Dr. Candace Hayden

And maybe that’s where the tension between trust and experimentation becomes unavoidable. Experimentation says: we are still learning. Trust says: you can rely on us. Those two things are not always incompatible, but they do require honesty. Real honesty. Not just careful wording.

Dr. Candace Hayden

I’ve been in enough rooms to know how easy it is to blur readiness. Teams convince themselves that because something basically works, it is commercially ready. Investors want momentum. Founders want proof. Customers want solutions. Everyone has a reason to move one step faster than the product probably deserves.

Dr. Candace Hayden

And sometimes that works. Sometimes the gap closes quickly enough. But sometimes the sale happens before the thinking is mature, and then the customer is funding discovery they did not knowingly agree to fund.

Dr. Candace Hayden

To be clear, there are places where MVP works very well. I don’t want to flatten this into a blanket rejection, because that would be inaccurate.

Dr. Candace Hayden

Internal prototypes make sense. Controlled testing environments make sense. Small pilots with clear boundaries make sense. If the purpose is to explore feasibility, surface issues, and gather feedback before broader release, MVP can be exactly the right tool.

Dr. Candace Hayden

It also works with informed users — and I think that word informed matters a lot. If people understand they are part of an iteration cycle, if they know what is stable and what is not, if the relationship is explicit rather than implied, then the incompleteness is not hidden. It becomes part of the agreement.

Dr. Candace Hayden

In those contexts, MVP can actually build trust instead of draining it. Because honesty has structure. You’re not pretending the product is further along than it is. You’re saying, this is what it does today, this is what we’re testing, this is where we need signal. That’s a very different posture.

Dr. Candace Hayden

I’ve seen early versions be incredibly useful when the context is honest. People can be remarkably generous with imperfection when they feel respected. Most users do not require polish as much as they require clarity. They can work with rough edges if the rough edges are named.

Dr. Candace Hayden

So yes, MVP has a place. It just needs the right container. Without that, the same approach that supports learning can start looking like outsourcing quality control to the customer.

Dr. Candace Hayden

Where it breaks is when the product is sold as complete — or complete enough in a way that suggests more maturity than really exists. That’s one failure point.

Dr. Candace Hayden

Another is high-stakes environments. If a tool affects decisions with real consequence, if failure carries more than inconvenience, then the tolerance for ambiguity should be lower. I don’t think that’s controversial. Some settings simply do not leave much room for foundational uncertainty.

Dr. Candace Hayden

And foundational logic matters. If the core of the product is still unstable, if the basic reasoning underneath it hasn’t been stress-tested, then speed stops looking disciplined and starts looking premature. A simple interface can hide deep instability. That happens more often than people admit.

Dr. Candace Hayden

This is the point where MVP becomes an excuse. Not for iteration, but for unfinished thinking. That’s different. Iteration refines something coherent. Unfinished thinking asks the market to compensate for gaps that should have been examined earlier.

Dr. Candace Hayden

I might be overstating that a little — or maybe not. But I do think there’s a difference between a narrow first version and a product whose creators have not yet done enough conceptual work. One is disciplined scope. The other is avoided rigor.

Dr. Candace Hayden

And once those get confused, the term MVP starts covering too much. It becomes less a method and more a shield.

Dr. Candace Hayden

I also think this connects to a broader pattern we’re seeing with no-code tools. And I say that carefully, because no-code itself is not the problem. Like MVP, it can be useful. It lowers barriers. It makes experimentation faster. It allows ideas to be expressed without waiting on a full engineering cycle.

Dr. Candace Hayden

That can be valuable. But when no-code speed gets paired with shallow validation, something else happens. Products can be assembled quickly enough that the act of building starts to feel like proof. It isn’t proof. It’s just construction.

Dr. Candace Hayden

And if that quick construction is wrapped in MVP language, there’s a temptation to move straight from rough build to marketable offer. Rapid building, limited testing, early monetization — that sequence is increasingly common because the tooling makes it possible.

Dr. Candace Hayden

Possible is not the same as wise, though. That’s the quiet distinction I keep returning to in a lot of AI and no-code conversations. The distance between “I can make this” and “someone should rely on this” is still real, even if the tools compress development time.

Dr. Candace Hayden

So when people combine no-code and MVP thinking, I think they need to be extra careful about validation depth. Fast assembly can create false confidence. A working demo is persuasive — sometimes too persuasive. Especially to the person who built it.

Dr. Candace Hayden

What I actually believe is pretty straightforward. Iteration is necessary. Speed is useful. Learning matters. I don’t think thoughtful product work happens without all three.

Dr. Candace Hayden

I also don’t believe everything needs to be fully mature before anyone sees it. That would be another kind of distortion. Early exposure teaches you things private development never will. There is value in releasing before you feel entirely comfortable. Sometimes that’s the only way to learn what the thing really is.

Dr. Candace Hayden

But — and this is the line I keep coming back to — incomplete should not be confused with acceptable.

Dr. Candace Hayden

...Those are not the same standard. Something can be unfinished and still responsibly framed. Something can be early and still honest. Something can be limited and still worthy of trust, if the limits are clearly understood. But incompleteness by itself is not a defense. It doesn’t automatically justify exposure, pricing, or claims.

Dr. Candace Hayden

Maybe that’s my real concern. Not that we build quickly, but that we sometimes lower the meaning of acceptable in order to protect the speed. And then we call that discipline. I don’t think it is. I think discipline is being precise about what stage you’re actually in, and what others are being asked to absorb.

Dr. Candace Hayden

I’m not offering a rule here. Just a standard I’m trying to hold in my own thinking as these tools and product habits keep accelerating.

Dr. Candace Hayden

So if I reduce all of this down to something simple, it’s probably this.

Dr. Candace Hayden

If you’re experimenting — call it that.

Dr. Candace Hayden

If you’re building — understand it.

Dr. Candace Hayden

If you’re selling — stand behind it.

Dr. Candace Hayden

That feels, to me, like a cleaner way to think about responsibility. Not slower for the sake of being slower. Not more polished for the sake of appearances. Just more honest about what the product is, what it isn’t, and who is being asked to carry the uncertainty.

Dr. Candace Hayden

Anyway... that’s where my head is right now. I’ll probably keep turning this over a bit, because the language we normalize ends up shaping the decisions we excuse. And that’s usually where I start paying attention.