Framework
Ambiguous PRDs lead to rework. Score every PRD for ambiguity:
| Element | Clarity Score |
|---|---|
| Problem statement | 1-10 (1=vague, 10=crystal clear) |
| Success criteria | 1-10 |
| Edge cases | 1-10 |
| Constraints | 1-10 |
| Acceptance criteria | 1-10 |
If any element < 7, PRD needs clarification before engineering starts.
Quick Check
- Can two people independently read this PRD and build the same thing? If no, it's ambiguous.
- Does this spec answer every question an engineer might have? If not, ambiguous.
Key Takeaways
- Ambiguity in PRDs = rework later. Invest 2 hours clarifying upfront vs. 20 hours reworking mid-build.
- Score and iterate until clear. This forces discipline.