Amol Avasare: recommendation

Transcript context

…This is such an interesting insight you're making. It's so counter to how a lot of people are thinking PM is evolving. What I'm hearing here is, because PMs are so behind, because engineers are just getting so much done, there's many people here, "Okay, you need to be prototyping, you need to be shipping PRs as a PM." What you're saying, which I completely agree with, is your time is much better spent helping PM basically, and helping the engineers become better PMs themselves. And the leverage there is a lot higher than you spending time coding, shipping PRs in most cases. I think that's true in certain circumstances. I think that as a smaller company, I don't know that that's the case. In a smaller company where it's all hands on deck, I think you probably need to be shipping. I think if you're in a company where budgets are very tight, and engineers are very tight, and you're not able to just hire because money's unlimited, then you need to do what is needed to accelerate the impact your team's going to have. Right? So there's going to be a number of cases, where as a PM, the right thing to do is to be like, "Screw it. I'm shipping and I'm going it the whole way." But I'm talking here more about the larger companies, more scaled businesses. Yeah, if you have 20 engineers, is it the highest use leverage of your time to ship an extra feature, or figure out how do I up-level everything that we're doing, get the user insights better, et cetera? Yeah. And I think there's also an element of shipping to learn, building a prototype so that you can have a better opinion. A lot of people talk about just, "I'm just going to try three things, see how it goes and that'll help inform the roadmap." This is now the PRD, is look at it instead of talking about it. So there's a lot of value there still.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.