Build learning into every step, not just the output

It's not a engineering milestone or a design milestone, it's a learning milestone. So we build something and along the way we actually grow the scope of what we build.

There's always like a trade-off between speed of delivery and speed of discovery, and that actually leads to the next layer of how do we combine the two? Because people tend to think it's an either/or.

I want to see someone be able to get those inputs, be able to say, 'This is the path. This is how I learned why I put this path together.' And then... what are the little milestones that make you say, 'Hey, is this working? Is this not working?' And then make you either make a different decision.

Keep making bets. In parallel, start doing some discovery so that eventually those bets get better.

You're always delivering and you're always discovering. The more you build this discovery habit, the better those bets are going to get with time.