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

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.

What is the user problem that once we solve users can't live without?

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.

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.