We start to try to live in tomorrow and the future, and start to think about what we build today as a stepping stone to graduate users.

I have a daily call thats 2.5 hrs with the entire team: from materials, sourcing, manufacturing, design, sensor, firmware... mechanical engineering - all together and they all have to sit through each other's updates... but then understand what those tradeoffs are and I sort of force that communication.

I think that 'system think' is a mindset.

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 have to have the definition of what you're trying to do across the system.

Everything for us is a system. We don't think about it discretely as just as a piece of hardware, or discretely as an application... or discretely as a platform. We think about it across the whole thing.

We start to try to live in tomorrow and the future, and start to think about what we build today as a stepping stone to graduate users.