You sort of have to separate what are questions you can ask that are going to help make you smarter about your thesis versus... trying to get somebody to validate it for you.

You have to take those concepts and prove them, a little bit like you do a PhD thesis.

Think about where does this stand in the experience continuum that you've been imagining, where the world's going to go.

It turned out that building mobile software was a lot more like building hardware... where you had 1 shot and you had to get it right, right out of the gate.

The thinking needs to shift from being less about the actual things, to being about the individual user.

You gotta think about your category, your replacement cycle, usage, how these things come together and the dynamics are different.

What is the user problem that once we solve users can't live without?