Geoff Charles: recommendation

Transcript context

…What about the product experience itself? Is there design review that happens? How do you stay on top of just like, "I'm proud of this product that we're shipping as a team?" I'd say we're iterating. I think when the first couple of years, it was more asynchronous and ad hoc process. And once you hit 10, 15 PMs and 20 or 30 different mini pods shipping constantly, I think you need a bit more of a process by which you have high-risk decisions that are being surfaced. So we're iterating. I think we're relating now is any large rock that we have on the roadmap needs to be brought into the product review process, where myself and the head of design are present and giving feedback, but it needs to be structured in a way where you are asking specifically for what type of feedback you need and you're highlighting the key risks and tradeoffs that you're making implicitly in that review. So that's one way we're able to scale, but I would say largely people ship and it's the difference between a beta and the GA, that's where we really get plugged in. When we make the decision to go live to the rest of the customer base and asking sales to start selling, that's where I'll really come in and stress test the hypotheses and the decisions. It's further downstream so it's more risky, but because we move so fast, you don't waste that much time if you have to pull it back. Yeah, that came up actually. I just had a chat with Nicole Forsgren, who's world expert on developer productivity and developer experience, and they've done all this research on quality and speed of engineering and the engineering team. And they find that quality goes up as your product velocity goes up. You'd think it'd be the opposite. The faster you move, the lower quality ends up being. But exactly to your point, because you can fix things really quickly and you can get things out the door and there's not this huge chunk you have to wait for people to review and release and break things, ends up being higher quality. So it's very much aligned with our experience.…

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