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

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

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

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 think that 'system think' is a mindset.

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

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.