In 1985, Coca-Cola made one of the most studied decisions in modern business history. After months of consumer research, thousands of taste tests, and genuine confidence that the data supported their conclusions, they replaced the formula that had defined their brand for nearly a century. The product they launched, New Coke, was by several measures objectively preferred in blind tests. People genuinely liked the taste.
The market response was immediate, visceral, and almost entirely negative.
Within weeks, Coca-Cola was receiving thousands of complaint calls per day. Protest groups formed. Stockpiles of original formula Coke were hoarded. Three months after the launch, the company reversed course and brought back the original formula under the name Coca-Cola Classic. The episode is still taught in business schools as a cautionary tale about the gap between what research appears to show and what customers actually value.
The lesson that gets quoted most often is about brand loyalty. But there is a quieter lesson underneath it, one that is more relevant to small business owners facing a new project: the difference between validating a preference and validating a decision.
What Validation Actually Means
The word gets used loosely. Founders say they have validated their idea when they mean that people responded positively in a conversation. Owners say the market has confirmed their direction when they mean that nobody told them it was a bad idea.
These are not the same as validation. They are, at best, early signals. At worst, they are a form of confirmation bias dressed up in the language of due diligence.
Real validation answers a specific and uncomfortable question: will someone exchange money for what you are proposing to build, before you have finished building it?
This is the standard that separates genuine market feedback from social courtesy. When you describe your idea to a friend, a colleague, or even a prospective customer in a casual conversation, the social contract of the interaction works against honest feedback. People are inclined to be encouraging. They do not want to discourage you. They may genuinely find the concept interesting without having any intention of paying for it.
The moment money enters the picture, the conversation changes. Suddenly the question is not "does this sound interesting?" but "is this worth what you are asking?" That shift in stakes is where real information lives.
The Three Questions Validation Must Answer
Structured validation, the kind that actually reduces risk before a project begins, is built around three questions. They are not complicated. What makes them valuable is the discipline of insisting on honest answers rather than comfortable ones.
Does the problem actually exist?
This is the foundational question, and it is where many projects begin to drift from reality. Owners often confuse their own experience of a problem with evidence that the problem is widespread. A consultant who has spent years frustrated by a particular inefficiency in her industry assumes that other consultants share the frustration. A retailer who has struggled to find reliable local suppliers assumes that the problem is universal.
Sometimes they are right. Often they are right about the category of problem but wrong about its intensity. The difference between a problem that is genuinely painful and a problem that is merely inconvenient is the difference between a customer who will pay to solve it and a customer who will simply live with it.
The way to find out is to talk to people who are not personally connected to you and ask them not whether your solution sounds good but whether the problem you are describing costs them anything. Time, money, lost revenue, missed opportunities. If the problem does not cost them something measurable, the solution may be a solution in search of a problem.
Will people pay to solve it?
This is the question that most owners are reluctant to ask directly, because the answer has real consequences. It is much more comfortable to operate in the space of hypothetical enthusiasm than to discover that a well-liked idea does not translate into actual purchase decisions.
The most reliable way to test willingness to pay is to ask for a commitment before you are ready to deliver. This does not mean deceiving anyone. It means being transparent about what you are building and asking, explicitly, whether someone would be willing to pay a specific amount for it once it exists. A deposit, a letter of intent, a pre-order, an agreement in principle. The form matters less than the act of asking for something real in exchange for something that is not yet available.
The number of people who say yes, and what they are willing to pay, is your market signal. It is not a guarantee. Markets are complex and commitments made in anticipation of a product sometimes evaporate when the product arrives. But it is considerably more reliable than a room full of people nodding along to a presentation.
Are you the right person to solve it?
This question is the most personal, and the most commonly skipped. It sits at the intersection of honest self-assessment and strategic thinking, which makes it uncomfortable for reasons that have nothing to do with the market.
Being the right person does not mean being the only person capable of building the solution. It means having a meaningful advantage in building it. That advantage might be technical knowledge, industry relationships, geographic position, existing infrastructure, or a proprietary insight that others do not have access to. It might simply be timing, being positioned to move faster than anyone else because of where you already are.
The danger of skipping this question is not that someone else will build the same thing. It is that you will build the right thing in the wrong way, or the right thing at the wrong cost, because you lacked the specific advantage that would have made the project efficient to execute. Markets reward advantage. Projects without inherent advantage tend to be expensive in proportion to their returns.
A Framework Worth Borrowing
The startup world developed a concept called the minimum viable product, and while the term has been somewhat diluted by overuse, the underlying logic is sound and directly applicable to small business project planning.
The principle is this: before investing fully in building something, build the smallest version of it that allows you to learn whether the core assumption is correct. Not a prototype for its own sake, but a deliberate experiment designed to test the one thing that, if wrong, would invalidate the entire project.
For a restaurant owner planning a catering operation, the minimum viable version might be a single corporate lunch booked through personal contacts, delivered at cost, with a structured debrief afterward to understand exactly what worked and what did not. The goal is not revenue. The goal is information.
For a software consultant planning to productize her methodology, the minimum viable version might be a paid workshop delivered to three companies before a single line of code is written. If the workshop sells, the demand is real. If it does not, the product probably will not either.
The discipline here is in resisting the urge to build the full thing before testing the core assumption. This is genuinely difficult for people who are energized by building. The satisfaction of creating something complete is real, and it can override the uncomfortable patience required to test before committing.
What the Market Is Telling You Right Now
There is a pattern visible in the current business environment that makes this conversation particularly timely. Across industries, consumer and business purchasing behavior has become measurably more deliberate since 2022. Interest rate increases, inflation, and general economic uncertainty have made buyers at every level more careful about discretionary spending.
This matters for small business project validation because it means the bar for genuine commitment has risen. Ideas that might have attracted casual interest and early adoption in a more expansive economic moment now need to clear a higher threshold to generate actual revenue. The people you talk to during validation may be genuinely interested and genuinely cautious at the same time, which means reading their responses requires more precision than it once did.
The practical implication is straightforward: in the current environment, validation needs to be more structured, not less. The informal coffee conversation has always been an unreliable signal. Right now it is even less reliable than usual. Build the validation process deliberately, ask for concrete commitments, and weight the results accordingly.
The Honest Conversation With Yourself
Before any of the external work of validation begins, there is an internal conversation that experienced project practitioners tend to have and newer owners tend to skip. It is a simple audit of the assumptions baked into the idea.
Write them down. Every belief you hold about the project that you have not yet verified. The assumption that customers will pay a certain price. The assumption that the problem is felt widely enough to support the business you are imagining. The assumption that you can deliver at the quality level required. The assumption that the timing is right.
Each of these assumptions is a risk. Not necessarily a fatal risk, but a risk that will cost something to resolve, either before the project begins or during it. The ones you identify early can be tested cheaply. The ones you discover late tend to be expensive.
This exercise does not require a consultant or a framework or a spreadsheet. It requires honesty and a willingness to sit with uncomfortable uncertainty for long enough to examine it clearly.
What Comes Next
Assume for a moment that your validation work comes back positive. The problem is real. People will pay. You have an advantage. The timing is reasonable.
You now have something more than an idea. You have the beginning of a business case.
A business case is not a business plan. It is not a document produced for a bank or an investor, though it can serve that purpose. It is, at its core, a structured argument for why this project is worth pursuing. Why the opportunity is real. How the money works. What it will take to execute. Why you are positioned to succeed where others have not.
Building that argument with clarity and honesty is the next step. And it turns out that the process of building it has a way of revealing things about the project that even rigorous validation does not surface.
That is where we are going in the next article.