So, you want to build an app, but you’re not sure if anyone will use it. This one is for you. Here are six simple steps I personally use on my own projects before I build anything.
1. Write a clear statement of need
Start with one sentence that says who has the problem and how your idea helps. It should look something like this:
I believe that content creators nowadays struggle to come up with ideas for their content, and my solution can solve it.
If you can’t write that sentence yet, you’re not ready to build.
2. Define five potential users
Right after that, name five people who could benefit from your solution. Not “everyone”. Five real people you can actually reach.
3. Talk to them
Reach out and try to understand the real pain points they face. Find out which part of the process takes up a lot of their time, and which part they would most like to improve.
4. Identify the pain points
From those conversations, write down the pain points as they described them. This is your evidence, so keep it in their words where you can.
5. List your unique selling points
Once you have the pain points, list your unique selling points (USPs). They could be features that solve a pain point directly, or features you think might suit these users, because sometimes the pain points are not as obvious as the users think.
6. Pick one or two features to build first
With your USPs defined, pinpoint the one or two features that would bring the most value to your users. Build those first. Keep the other USPs in view, but leave them out until you’ve developed your first MVP.
What this gives you
Validation doesn’t guarantee that people will use your app. What it does is reduce the guesswork. Instead of building on an assumption, you start with a solid problem that real people told you about, and that gives your first version a much better chance.