Stop Writing PRDs
Why are you still writing PRDs?
I've spent a large part of my career writing product requirement documents. Writing them, updating them, and maintaining them as they "evolved" was a real time sink.
The goal was always the same: make sure you're building the right thing for customers, and that your team understands what to build and what matters most. But that understanding isn't static. It changes as you learn and as tradeoffs surface. Keeping a document in sync with all of that is just brutal.
Tools like Figma Make have made this largely obsolete.
I recently tried it for the first time. I spoke into a prompt for about five or six minutes describing everything I wanted: features, flows, the whole thing. I hit enter and it generated a solid initial mock. Then I clicked through to the next page and realized it hadn't just made a wireframe. It had built a working prototype of everything I'd described. I had to make some adjustments, but once I got it to a place I liked, I just thought — why would I ever write this out in text again?
Instead of a document that everyone has to interpret, I had something the whole team could click through and react to. My designer took it and styled it properly. Our sales lead said he could use it himself for future products. No engineering time spent. No long alignment meetings. Just a working thing people could see and respond to.
If you're still spending hours writing PRDs only to then need long meetings to make sure everyone interpreted them the same way, stop. Build a working prototype instead. The tools are finally here.
