We can dream a lot faster than what's possible.

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

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.

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

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

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