I think that 'system think' is a mindset.

It is a little bit science project-y sometimes, and we talk about it that way.

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

You sort of have to separate what are questions you can ask that are going to help make you smarter about your thesis versus... trying to get somebody to validate it for you.

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

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.