Product & Delivery · Chapter 2 of 8
Writing that makes engineering able to start
The product manager's real output is not the roadmap. It is the document that removes ambiguity.
Whatever your organisation calls it — PRD, one-pager, spec, brief — the test is the same: can a competent engineer read this and begin, without a meeting? Most cannot, and the resulting meetings are the tax.
What a usable document contains
| Section | What it answers | The failure when it is missing |
|---|---|---|
| The problem | Who has it, how often, what it costs them | Engineering optimises the wrong axis |
| Why now | What changed to make this the quarter | It gets deprioritised the moment something louder arrives |
| What success is | The metric and its current value | You cannot tell afterwards whether it worked |
| Scope — and non-scope | What is explicitly excluded | Scope grows silently and the date slips |
| Constraints | Latency, cost, compliance, data residency | Discovered in week five, after the design |
| Open questions | What you do not yet know, and who decides | Engineers guess, and guess differently from each other |
| Rollout | Flagged, staged, measured, reversible | It ships to everyone on a Friday |
Three habits that raise the quality immediately
- Write the non-scope list first. It is harder and it is where the real thinking is. If you cannot name five things you are deliberately not doing, you have not scoped anything.
- Put the open questions in, honestly. A document that pretends certainty it does not have gets found out in week two and costs you credibility. A document that says ‘we do not know how the vendor rate-limits this; I am finding out by Thursday’ is trusted.
- Write for the engineer who joins in month three. They were not in the meeting and cannot ask you, because by then you are on something else.
The test to run before you circulate it
Give it to one engineer who was not in any of the conversations and ask them to tell you what they would build. Where their answer differs from your intention, the document is ambiguous — not them.
This takes fifteen minutes and it is the highest-return fifteen minutes in product management.