 So, when you think about understand identifying execute, one of the most important foundational framework pieces I think is executing law. There's this way of thinking about execution that I've thought about for a while, which is speed as the primary execution strategy, a.k.a. good execution equals speed in execution. And this is very relevant in a bunch of different ways. Speed allows you to experiment, refine, and have the margin of error in your execution. To a certain extent, if you have speed, you can make mistakes and that's okay. It doesn't mean that you should just be very reckless about it. You should still be thoughtful, you should still prioritize, but there are a lot of things you can do to dramatically increase the speed at which you build products. Speed is also very important because it allows for more outputs from you for your team. Now, the thing that you guys probably have seen from product management function is we're multipliers. Like everything that a product manager can do cascades through the entire team. So if you are able to get more meaningful output out of yourself, it has a cascading multiplying function from the output of the team.