The Uncomfortable Truth About Running A Tech Start-Up
Your Great Idea Is Not Evidence That Anyone Wants It Every founder has a story. They experienced a frustrating problem, saw an opportunity that others had missed and decided to build something to solve it. It is one of the most familiar origin stories in entrepreneurship. There is just one problem. Experiencing a problem yourself […]
Black News 
Your Great Idea Is Not Evidence That Anyone Wants It
Every founder has a story.
They experienced a frustrating problem, saw an opportunity that others had missed and decided to build something to solve it. It is one of the most familiar origin stories in entrepreneurship.
There is just one problem.
Experiencing a problem yourself does not prove that enough other people have the same problem, care about solving it or are prepared to pay for the solution.
That is the uncomfortable gap between having an idea and validating one.
We Often Validate With the Wrong People
Innovation has a tendency to attract people who already believe in innovation.
Founders speak to investors, who naturally want to know whether an idea could become a high-growth business. Engineers speak to other engineers about whether something can be built. Academics discuss whether an approach is novel or scientifically interesting.
All of those conversations matter, but they answer different questions.
An investor can tell you whether a proposition sounds investable. An engineer can tell you whether the technology is technically feasible. An academic can tell you whether the underlying research is novel.
None of them can necessarily tell you whether a nurse will use the product during a busy hospital shift, whether a small business will pay £100 a month for it, or whether a frontline worker will abandon the spreadsheet they have relied on for the past decade.
Technical feasibility is not market need. Academic novelty is not customer pain. Investor enthusiasm is not adoption.
Ask the Right Person the Right Question
The quality of validation depends partly on who you ask.
Asking someone whether they “like” an idea produces relatively weak evidence. Asking whether they would change their behaviour, spend money or fight to keep a product begins to reveal whether the problem genuinely matters.
| Right Person | Better Question | Warning Sign |
|---|---|---|
| Practitioner / Daily User | “Would solving this save you meaningful time every week?” | “Maybe” or “I’d probably try it.” |
| Customer / Buyer | “Would you pay £X to solve this problem?” | “Perhaps after version two.” |
| Frontline Operator | “Would you fight to keep this tool if it disappeared tomorrow?” | Indifference or a shrug |
| Academic / Expert | “Is there credible evidence behind this problem and approach?” | Interesting theory, weak real-world need |
| Supply Chain | “Can this be produced and delivered reliably?” | Technically possible, operationally unrealistic |
| Internal Champion | “Is this important enough for you to drive adoption internally?” | “Someone else would need to own it.” |
The purpose is not to find people who will tell you that your idea is brilliant.
It is to find evidence strong enough to tell you whether you should continue.
Six Conversations Before You Build
At the UKBlackTech Institute, we think innovation should begin much closer to the problem.
Practitioners can establish whether the problem exists in everyday life. Customers can establish whether solving it has sufficient value to justify paying for it. Academics can interrogate the underlying evidence and scientific opportunity. Supply-chain partners can determine whether the solution can actually be produced and delivered reliably. Internal champions can establish whether an organisation cares enough about the problem to drive adoption. The wider market can help determine whether the timing is right.
Each stakeholder therefore answers a different question.
| Stakeholder | What You Need to Discover |
|---|---|
| Practitioners | Do people genuinely experience this problem regularly? |
| Customers | Will somebody exchange real money to solve it? |
| Academics | Is the underlying evidence, science or domain opportunity credible? |
| Supply Chain | Can the solution be sourced, produced and delivered reliably? |
| Internal Champions | Does somebody care enough to drive adoption inside the organisation? |
| Market | Is the market ready, or are you arriving too early or too late? |
These stakeholders are not interchangeable.
Each sees a different part of the problem. That is precisely the point.
Collaborate Before You Experiment
The first stage of the UKBlackTech Institute model is therefore Collaborate.
Before writing significant amounts of code or spending significant amounts of money, innovators should bring the people surrounding the problem into the room.
The objective should not simply be to secure six enthusiastic endorsements. A disagreement between stakeholders may be more valuable than six people saying yes.
A practitioner might desperately want a solution that procurement cannot purchase. A customer might be willing to pay for something that cannot yet be delivered economically. An engineer might be able to build something technically impressive that frontline workers simply do not need.
Those contradictions are not failures.
They are information.
Discovering them before building is considerably cheaper than discovering them after launch.
Experiment Before You Build
Once there is evidence that a meaningful problem exists, the temptation is to start building the technology.
That can also be a mistake.
The next question should be: what is the cheapest experiment that could prove us wrong?
Sometimes that means a prototype. Sometimes it means a no-code service. Sometimes it means manually delivering the proposed solution to ten customers before automating anything.
The objective is to maximise learning while the cost of changing direction remains low.
Clicks, likes and expressions of interest can be encouraging, but behaviour provides stronger evidence. Did people return? Did they use the service repeatedly? Did it save them meaningful time? Did somebody actually pay?
The closer an experiment gets to real behaviour, the stronger the evidence becomes.
The UKBlackTech Institute Framework
This thinking is captured in four stages: Collaborate, Experiment, Build and Scale.
| Phase | Core Principle | What Happens | Evidence You Are Looking For |
|---|---|---|---|
| 1. Collaborate | Never skip a voice | Validate the problem across practitioners, customers, academics, supply chain, internal champions and the market. | Strong agreement that the problem is real, important and worth solving. Disagreement becomes a reason to investigate or pivot. |
| 2. Experiment | Test simply before building technology | Run low-cost, high-learning experiments using prototypes, concierge services, paper tests or no-code tools. | Real behaviour: repeated use, retention, time saved and willingness to pay rather than clicks alone. |
| 3. Build | Co-create, don’t dictate | Develop alongside practitioners and customers rather than disappearing into a development team. | People incorporate the solution into everyday work and actively want to keep it. |
| 4. Scale | Share and learn | Expand what works while publishing evidence, learning from failure and bringing new collaborators into the ecosystem. | Adoption grows, others participate and the solution continues creating measurable value. |
The framework deliberately makes Scale the final stage rather than the ambition at the beginning.
Scaling an unvalidated idea does not solve its weaknesses. It simply makes those weaknesses more expensive.
Build With People, Not For Them
Once there is sufficient evidence to build, practitioners should become more than research participants. They should become collaborators.
Products built in isolation tend to encode the assumptions of the people building them. Products developed alongside the people who will actually use them have a better opportunity to reflect the complexity of the environment in which they must operate.
The ultimate signal is not that users say they like the product.
It is that the product becomes part of how they work.
If removing it tomorrow creates a genuine problem, you may finally be approaching something valuable.
The Uncomfortable Truth
Founders are supposed to believe in their ideas. Without conviction, very little innovation would happen.
But conviction and evidence perform different jobs.
The founder’s job is to see what might be possible.
Validation asks whether anybody else cares.
That distinction sits at the heart of the UKBlackTech Institute’s approach to innovation.
The difference between innovation that scales and innovation that dies is rarely just the idea, the technology or the funding. It is whether the people expected to use it, buy it, deliver it and live with it ever wanted it in the first place.
