There are times when you should start with the problem you are aiming to solve and there are times when you should not.
What that being said, there has not been a time over the last 20 years of my career where starting with a solution was the right choice.
Why?
Because when you create a solution that doesn’t solve anyone’s problem and we all have problems to solve; you end up with a solution that no one wants.
That, or you run around looking for a problem to solve with your solution … imagine a person with a hammer and a not a nail to be seen.
Think about the software as a service industry, aka SaaS. There are many people creating software solutions, as you are reading this, that no one wants.
Why?
Are they poorly coded? Not necessarily.
Are they poorly designed? Not necessarily.
Do they address a need in the market?
Aha! The right question!
Specifically, was the software designed to solve a problem for a group of people who share similar characteristics?
If the answer is no, than stop building it.
If the answer is yes, than ask yourself how many people can this software potentially help?
And to what degree can you help them?
Can you solve 100% of their problem with your solution?
Or only 50%?
Is anyone else presently solving this problem, i.e. your competitors?
The best solutions out there start with the best problems out there.
The gnarly, uncomfortable, agitating, festering problems that no one else is trying to solve either because they don’t know how to solve them and or they don’t think its worthwhile.
What problems do you encounter every day?
Maybe there is a founder’s heart latent with you …
Want to read more?
MattRebeiro.com™ is a trademark of the Process Design Institute Ltd.
Copyright Process Design Institute Ltd. © 2024
Created with
