I don't write PRDs as a PM!

So designs basically become the source of truth for the project rather than a prd. And then that's complemented by like a set of strategy docs which span multiple products, not just a single product.

So you basically just write the words next to the design. Like if there's some edge case or something you have to capture, you just write it next to design.

Yeah, I also think that like PRDs are oftentimes like incredibly prescriptive, which I think doesn't work if you have like a very product minded designer or very product minded engineer. Like, like you might have something like there is a button that does this, but then like a designer reading that might be like why is it a button? Why isn't it this like other form factor that I thought of that's actually like a way better solution to this space, you know. And so like either you end up with like a PRD that is so vague in specifications that someone reading it doesn't really know what it is, or you end up with something that's too prescriptive on top of it, like almost always being out of date.