Before you say "nope," let me try to add some context...
My first idea I tried, I validated. But when I validated with surveys, I derived the wrong answer or asked the wrong question. Without getting into too much detail, the product was a coaching product to help the buyer. The buyer had the problems, but they were the source of them, whether they wanted to believe it or not. I have had success helping this group realize "oh it's me!" and fix the problem, making their entire system better. But, it really takes work to work it through their heads that it's them, and not everyone else.
I asked people who I had already successfully coached, and I asked others who I hadn't worked with with non-leading questions - which I think allowed them to interpret it as I'd help them fix their outside problems. In the end, either the market wasn't there, or I wasn't the person to perfect this recipe and the project ended up going nowhere. Learned a lot.
This new project I'm working on, I'm struggling with validating the topic again. It's basically helping programmers with security concepts. Think of it like locksmiths. People who are locksmiths, love it, are good at it, and you need them. But you really don't think about them until you need them. That's my fear with my new product idea. I know the need is there, but I don't know if people know they need it.
That sounds to me like I need to validate it. But I'm not sure if that information would be useful. It's like locksmiths again. I would think most of you would say I don't really need a locksmith in my area. Or you'd answer yeah I'd use a locksmith, but never actually then need to. But the few people who get locked out or get a key broke off in their lock, they'd be way out of lock if that locksmith hadn't launched their business.
So I'd love the community's thoughts on this :)