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

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

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.

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

I think that 'system think' is a mindset.

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

The thinking needs to shift from being less about the actual things, to being about the individual user.