A mobile app can be beautifully designed and still solve a problem people do not have often enough. Validation is the work of finding evidence before committing to a large build. It is less about asking whether people like an idea and more about observing what they already do.
Describe one repeated moment
Name a specific person, situation, and desired outcome. “Field staff need to record completed visits while travelling between locations” is easier to investigate than “we need an operations app.” It suggests a journey, an environment, and possible constraints.
Write down what the person uses today. They may rely on phone calls, paper notes, WhatsApp messages, or a spreadsheet. Those workarounds show where effort, delay, or uncertainty already exists.
Ask for recent behaviour
Talk to likely users about the last time the problem happened. What triggered it? What did they do first? Where did they get stuck? What was the consequence? A concrete story is more useful than asking “Would you use an app that does this?”
Be careful with enthusiastic answers. People may agree that an idea sounds useful without making room for it in their daily routine. Look for frequency, cost of the problem, and whether they have already tried to solve it.
Interest is a signal; repeated behaviour is stronger evidence.
Test the core journey cheaply
Choose an experiment that isolates the riskiest assumption. A clickable prototype can test whether the workflow makes sense. A manual service can test whether people value the result. A small mobile-friendly web flow can test whether users will return for the task.
Define the evidence you need before running the experiment. For example: can five target users complete the main task without guidance? Will they come back next week? Does the new flow remove a measurable delay?
Decide what the first build must prove
Once the core problem is credible, pick a first version that completes one valuable loop. Include the states that make it trustworthy: loading, empty data, errors, and clear confirmation. Leave unrelated features for later.
An early decision checklist:
- Is the problem frequent or costly enough to matter?
- Can you identify a reachable group of users?
- Have you seen the current workaround in real use?
- What observation would cause you to change course?
Keep learning after the decision
Validation cannot guarantee adoption. It can make the first investment more informed. Continue watching actual use after release, especially where people abandon the key journey or invent a workaround inside your new product.
Have something similar in mind?
Tell us what you are trying to make better. We can help you find a practical first step.
Start a conversation