I once audited our Notion workspace and counted 47 documents tagged PRD. I then counted how many were actually finished. The answer was nine. The other 38 were ghost towns: a filled-in problem statement, maybe a goal or two, and then the cursor of doom blinking in section six of a fourteen-section template, where the author had clearly given up and gone to a meeting. Our blank PRD template was not helping people write PRDs. It was a fourteen-section guilt machine.
The real reason nobody finished
Here is the thing I had wrong for two years: I thought the problem was discipline. People did not care enough about documentation. But the actual problem was that staring at a blank fourteen-section template is genuinely demoralizing, and the empty cursor punishes you for not already knowing the answer. Writing is the hard part. Editing is the easy part. The template forced everyone to do the hard part with zero momentum.
So we flipped it. Now the first draft is never blank. A PM pastes whatever they have, even a half-coherent feature description, into the Turn a Rough Idea or Slack Thread into a Team-Ready PRD prompt, and the output becomes the starting document. The PM's job changes from 'write a PRD from nothing' to 'react to a draft and fix what is wrong,' which is a task humans are genuinely good at and even enjoy. We went from PRD-to-review-ready taking about two days to taking about two hours.
I tested this theory before I rolled it out, because I did not want to inflict another process on my team based on a hunch. I took six recent feature requests that had been sitting in various states of doc-rot and ran each through the prompt. Five of the six produced a draft that a PM could turn into a finished PRD in under an hour. The sixth was a genuinely gnarly platform migration that the model could not meaningfully scaffold, which honestly was useful information too: it told me which work was actually complex versus which work was just suffering from a blank-page tax. That five-out-of-six ratio held up once the whole team adopted it.
How we actually wired it into the workflow
I did not want this to be a 'cool trick one PM uses.' I wanted it to be the default. So we made the new-feature template in Notion start with a single instruction at the top: paste your idea into the prompt, run it, paste the output below, then edit. That is it. The friction of the blank page is gone because step one produces words you can argue with.
- Success metrics now appear in basically every PRD. They used to be missing in roughly 60 percent of our docs, because by the time you got to that section your energy was gone.
- Non-goals force the scope conversation at the start, where it is cheap, instead of mid-sprint, where it is a fight.
- Open questions come out numbered and owner-tagged, so they actually get answered before kickoff instead of haunting the project.
- New PMs ship a competent first PRD in week one, because the prompt encodes the structure a senior PM would have insisted on.
An honest caveat about the edit pass
The output is a first draft, not a final one, and treating it as final is how you get a confident, well-structured, completely wrong document. The model will happily write a plausible success metric that is subtly the wrong thing to measure. It will sometimes propose a user story for a persona that does not exist in your product. The ten-minute edit pass is not optional. But ten minutes of editing beats two hours of writing every single time, and an edited draft is a thing that gets finished.
There is a cultural side effect I did not expect. When the first draft is cheap, people write more PRDs, and they write them earlier, for smaller things. We used to skip the PRD entirely on 'minor' features because the overhead was not worth it, and then those minor features would balloon into messes precisely because nobody had written down the boundaries. Now a two-minute prompt run produces a draft worth having even for a small feature, so the boundaries get written down, and the small features stay small. Lowering the cost of starting changed what we were willing to start.
The Notion graveyard is shrinking. We are at maybe a dozen abandoned PRDs now, down from 38, and most of those are genuinely dead features, not abandoned writing. If your documentation problem is actually a blank-page problem in disguise, grab the Turn a Rough Idea or Slack Thread into a Team-Ready PRD prompt on Prompt Dock and make it the first step of your template. When the PRD turns into real tickets, I hand each feature to my Write a User Story and Acceptance Criteria from a Plain Feature Description prompt and the handoff stays clean the whole way down.