Should I validate or build first?
I am building a Inventory management software for specific industry. The industry only option right now is to use a solution that’s was built 10 years ago.
I know people have the problem because they are already paying for the old solution. I am pretty much creating a new version of it. Such as connecting to modern marketing tools and bring them online.
I am wondering if I should validate the problem. I will still be doing customer interviews - Steve blank style so I can stay very close to the customer and there needs.
But I am deciding if should also build the
product. There have been a few people (2of5 interviews) that had asked me about using the product as well (I built designs), even though I never showed them the product or pitched them the product. They just went on the site from my email footer and asked.
Thanks
Menan
Validate Validate Validate!
Serious you can waste so much time and money.
Talk to 10 people using the old system. Do they like it? What do they like about it? What do they hate about it?
Who pays for it? Who do they have to convince to upgrade? Are there laws that prevent them from upgrading? What have they already tried to improve it.
Don't write any code until you at least talk to one person.
Like Joshdance said, you need to validate. That being said having a mock-up to show the value proposition may help get quality answers but you shouldn't do any real heavy-lifting until you know it is needed.