Kyle Evans retweeted
I hate the word "requirement" in a PRD.
The advice from popular websites on adopting a heavy, waterfall approach only deepens this frustration. They insist on documenting every detail:
- Requirements
- User stories
- Acceptance criteria
- Data flows
- Dates and milestones
...all supposedly crafted solely by the PM.
Where to start?
The name ”Product Requirements Document” might be misleading. Because it’s not about documenting the “requirements.”
Empowered product teams are led with the strategic context, given problems to solve, and are held accountable for the outcomes, not the output (features).
They start with a generic problem, perform product discovery together, explore the problem and solution space, and run experiments to validate their assumptions before the implementation.
To product people, the idea of waterfalling requirements from stakeholders to the product team or from PMs to other team members by writing detailed documents should sound absurd.
Of course, I get that some initiatives need to be summarized.
But a good PRD is a living document that captures your product discovery journey. It explains why the initiative matters, the objective, and how the success will be measured (key results).
It's not a rigid contract. And it shouldn't replace open communication and building alignment.
Actually, collaboration is key.
And it’s way more important than documentation.
---
What do you think about replacing the term PRD with something that better captures its essence?
Product Initiative Brief? Product Discovery Canvas? Something else?
Let me know in the comments.
🧵


