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

I think that 'system think' is a mindset.

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

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

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

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.

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