You have an idea for a product or service, and at first glance it makes sense. Perhaps it solves a problem you know firsthand, you were inspired by a similar project elsewhere, or you have noticed that people around you do something in an unnecessarily complicated way. But one of the biggest mistakes often happens before the work even begins: assuming that what seems useful to you will matter just as much to other people.
Entrepreneurial thinking is not only about having the courage to get started. It also means questioning your assumptions, gathering information, and testing a small version of your solution before investing a lot of time or money. This is where innovation and critical thinking naturally come together.
Separate the idea from the problem
A first-time creator may start with the product: “I want to build a learning app.” A more critical starting point turns the question around: “What specific learning problem do I want to solve, and for whom?”
The distinction matters. An app is a possible solution, not proof that the problem exists. If you discover that students do not need another tool but a simpler way to plan their work, your original idea may need to change significantly.
Write down what you are assuming
Every new project rests on assumptions. Some are obvious; others are easy to overlook. Those hidden assumptions can cause the biggest problems later.
For a simple business idea, try listing things such as:
- Who has the problem: the specific group of people affected by it.
- How often it occurs: every day, once a month, or only occasionally.
- How they deal with it now: whether they use another service, improvise, or ignore the problem.
- Why they might try your solution: what it would make easier, cheaper, faster, or more enjoyable.
- What might put them off: cost, habit, lack of trust, time, or a complicated user experience.
This list is not about pessimistically looking for flaws. It helps you identify which claims to test first.
Test the riskiest assumption first
Not all questions matter equally. If you do not know what colour the logo should be, the project can still move forward. If you do not know whether people want to use the solution at all, that is a much more fundamental issue.
A simple comparison can help:
| Assumption | What happens if it is wrong |
|---|---|
| People really do have this problem | The project may lose its main reason for existing |
| They are willing to change how they do things now | The solution may go unused |
| You can create a basic version | The idea may be too demanding technically or in terms of time |
| The name or visual design will appeal to people | These can be changed later |
Start with the question whose wrong answer would most seriously undermine the project.
Talk to people to learn, not to confirm your view
If you ask a friend, “Would you use an app that helps you study better?”, it is easy to get a polite yes. But that answer may reveal little about what they would actually do.
Questions about specific experiences are more useful:
- What was the biggest challenge you faced the last time you studied?
- How did you deal with it?
- What frustrates you about the way you do it now?
- What do you already spend time or money on?
- When did you last look for a different solution?
Past behaviour cannot guarantee what someone will do in the future, but it is often a more useful guide than a general expression of support.
A small test is worth more than a big presentation
With a new idea, it can be tempting to start by creating a logo, website, name, and lengthy presentation. These things can feel like progress, but they may not answer the most important question: does the solution actually help anyone?
A small test can be much simpler. If you want to create a service for planning study sessions, you do not need to build an app straight away. You could try a simple manual system with a few people and see whether they keep using it after the initial excitement wears off.
Your test should answer a clear question. For example: “Will users return to the planner after three days?” or “Does this approach reduce the time they spend organising tasks?”
Criticism is not automatically a reason to stop
When people around you have doubts, two equally unhelpful reactions are common. One is to abandon the idea immediately. The other is to ignore all criticism and decide that other people simply do not understand your vision.
A more practical approach is to sort feedback into three groups:
- A specific problem: The person can explain what would stop them from using the solution.
- An unanswered question: The feedback points to something you have not tested yet.
- A personal preference: The solution is not right for that person, but they may not belong to the group it is designed for.
Not every objection means you should change the product. But every specific objection can be a useful prompt for another test.
You do not have to simply accept or reject risk
People often talk about being willing to take risks when making business decisions. A more useful question is which risks you can reduce before you decide.
If you do not know whether people are interested in the product, try a small version. If you are unsure whether you can handle the technical side, build a prototype. If you lack experience, discuss the problem with someone more experienced. If the potential financial loss would be too high, set a limit on how much you are willing to put into the first attempt.
In a team, do not reward whoever argues the loudest
When each team member has a different idea, discussion can turn into a contest to persuade everyone else. That does not mean the best proposal will win.
It is more useful to agree on shared criteria, such as:
- What problem does the proposal solve?
- Can we test it on a small scale?
- How much time and what resources will it require?
- What could we learn from the test?
- What is the biggest risk?
If two proposals seem equally promising, you do not have to debate them at length. It may be more efficient to create two very small versions and compare people’s reactions.
A failed test can still be a good result
If a small experiment shows that people are not interested in the solution, it may feel like a failure. But from a critical-thinking perspective, you have learned something important before investing much more.
After a test, do not ask only, “Did it work?” These questions are more useful:
- What did we assume?
- What did we actually observe?
- Which assumptions were supported, and which were not?
- What should we change in the next attempt?
- Should we continue, adjust the solution, or set the idea aside?
This turns a mistake from a reason to judge yourself into information about the project.
Watch out for evidence that only supports your original view
When we like an idea, it is easy to notice the reactions that support it. One enthusiastic friend can seem more significant than five people who do not need the solution.
Before you run a test, write down what result would make you change the idea. For example, if most of the people you speak to do not consider the problem important, revisit how you have defined it. If people try the solution but do not return to it, find out why.
This kind of rule helps prevent you from explaining every result afterwards as proof that your original idea was right.
A simple framework for testing an idea
For a school business project or your own idea, you can follow these six steps:
- Define the problem: Who do you want to help, and in what situation?
- List your assumptions: What needs to be true for the idea to make sense?
- Find the riskiest assumption: Which one, if wrong, would most undermine the project?
- Design a small test: Get useful information without making a major investment.
- Compare expectations with results: Do not look only for confirmation.
- Choose the next step: Continue, adjust the solution, or redefine the problem.
This approach does not turn entrepreneurial thinking into endless analysis. On the contrary, critical thinking helps you act sooner, while taking a smaller and more carefully chosen risk. The goal is not to prove that your first idea was right. It is to find out as early as possible what is worth developing next.
