In the hardware world, you've got to take your time because your iteration cycles are much more deliberate.

No one is going to tell you what to build. If they did, then they should do it, not you.

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 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?

It has to go to the level of emotional connection, where you feel without it you're lost.

You have to have the definition of what you're trying to do across the system.