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

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.

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.

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.

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.