Taste matters more than ever for product teams. Building is cheap now, so what separates good work from bad is deciding what to make, how to show it, and which format to use. Skip bloated PRDs, but don't skip thinking.
Chapters
The taste to know what to work on, how to present that information, like how to achieve the goals, what medium to use is emerging as like the most important thing to do. Anybody can build anything, right? Starting from scratch, if you talk to these models, ours, anybody else's really, you can stand up whatever feature you want. Because implementation has gotten so cheap across every medium, it's very tempting to jump straight to a prototype. It's really tempting to say like, PRDs are dead. Let me just show you what I mean, right? What I've also noticed though, is that for engineers, it's really tempting to write a lot of documents, a lot of documents that are not worth reading. If implementation is abundant, then it's really important to pick the right format for the point you're trying to make. And now there's, there's like a curation process that needs to happen.