PRD contract process - stop teaching product

Situation

Stop trying to teach product how to write PRDs. Define acceptance criteria for PRDs, respond within 24-48 hours, rearrange and cut scope ourselves, and hand back a contract. They can accept or negotiate, but no endless back-and-forth. Engineering restructures the work and presents how we will deliver.

Reasoning

Teaching hasnt worked - product still doesnt deliver clean PRDs after months of coaching. A contract-based approach creates clear accountability. When engineering says here is how I will deliver this, product can accept or negotiate, but the ball is clearly in one court or the other. Good fences make good neighbors.

Additional Context

Brian Dawson was offended by Maxs simplified fill-in-the-blank PRD template. Peter response: I dont care if hes offended. We dont have time for them to be bent out of shape. Focus on what we need to move forward.

Observed Evidence

Peter: "I want to teach them, heres your scoreboard product. Heres how you win. Fill in this contract. And when engineering says contract accepted, well figure out the rules for how we say contract accepted" and "Its not even cutting scope, its rearranging... if I do it differently than you asked, itll get you a better result" and re Brian Dawson being offended: "I dont care if Im offended. I just dont care anymore, and I dont want us to care"

Confidence Breakdown