Going from insights to ideas, rather then the other way around

[Niels Wee]

Hey community,

I'm new to JPD and the product role. Going in, I had the expectation that the process would usually go from insights -> ideas rather than creating an idea and then attaching insights, which might just be carefully selected to support the idea. My company really suffers from confirmation bias; I'd rather not enable them.

Does anyone have a way that allows me to pool insights somewhere and ideally be able to spot emerging patterns, pains, contexts, personas, build assumptions, etc, that can mature into ideas?

And is there a good way to falsify the assumptions on which the ideas are built with the gathered evidence, to make the idea stronger? It seems that insights are primarily intended to support ideas, rather than challenge them.

Cheers

[Walter Buggenhout · Accepted solution]

Hi @Niels Wee and welcome to the Community!

Your observation on this topic is quite correct. Insights have initially been conceived to enrich ideas. However, there is an ongoing initiative to rethink this, which may very much be worth following. You can find it on the public JPD Roadmap (JPR-16), currently being explored.

Hope this helps! 

[Niels Wee]

Yep. Something along those lines would be good. We don't need anything too fancy, but at the moment, we'd have to change our current workflow to accommodate the JPD. Hopefully, there will at least be a light version of this for free plan people. 🙏