Hey Thomas, the risks are included in the product scope. They are tackled as part of continuous discovery.
If needed, you can adjust this template to your specific needs and context.
The AI PRD might seem large, but if you strip it down to just "example responses" and headers, it's actually quite minimal. Most sections are only 2–3 paragraphs! 😊
As visualized in the post, the PRD evolves as you learn more. The goal is to build alignment, not to document every possible detail (e.g., User Stories).
And frankly, for standard features that can be tackled in 1-2 Sprints, I have never considered writing a PRD. In many cases, sharing a design and a loom video or/and a Slack message was enough.
But when building a broad alignment becomes both challenging and critical, like with Auto Write, documenting, communicating, and aligning around the key assumptions and learnings becomes essential.
Thanks for sharing with our PM community!
Real-life based on Shopify also very valuable.
A few comments:
- Where do you capture « risks » (internal/external) in this approach?
- Based on experience, producing a full AI PRD early in product Life is time consuming:
- What is the right time / prerequisites to launch this work ?
- What would be a lighter version of it, if relevant?
Hey Thomas, the risks are included in the product scope. They are tackled as part of continuous discovery.
If needed, you can adjust this template to your specific needs and context.
The AI PRD might seem large, but if you strip it down to just "example responses" and headers, it's actually quite minimal. Most sections are only 2–3 paragraphs! 😊
As visualized in the post, the PRD evolves as you learn more. The goal is to build alignment, not to document every possible detail (e.g., User Stories).
And frankly, for standard features that can be tackled in 1-2 Sprints, I have never considered writing a PRD. In many cases, sharing a design and a loom video or/and a Slack message was enough.
But when building a broad alignment becomes both challenging and critical, like with Auto Write, documenting, communicating, and aligning around the key assumptions and learnings becomes essential.