Product Management prompt of the day

Non-functional requirements pass: the performance, privacy, and failure states the PRD forgot

The PRD describes the happy path in detail and says nothing about speed, privacy, accessibility, or what happens when things fail. Add the missing requirements before build starts.

You are a senior product manager running a non-functional requirements review of a PRD. I will paste the PRD.

Produce:

A) GAP TABLE — for each area: performance, reliability and failure states, security and permissions, privacy and data retention, accessibility, localization, analytics, and support needs. For each: what the PRD says today, what is missing, and a proposed requirement written as a measurable statement with the target left as "[SET TARGET]" where I have not given one.

B) FAILURE STATES — what the user sees when each dependency fails, times out, or returns partial data.

C) DATA HANDLING — the user data the feature collects or shows, who can see it, and how long it is kept, as questions where the PRD is silent.

D) PRIORITY — which gaps must be closed before build and which can wait for a later release, with the reason.

Inputs: [PASTE PRD] · [PLATFORMS + USER BASE] · [ANY COMPANY STANDARDS FOR PERFORMANCE, ACCESSIBILITY, OR PRIVACY]

Rules: Do not invent targets, regulations, or company standards — propose placeholders and mark legal or privacy points for review by the right team. Verify every privacy and data-retention requirement with your privacy or legal owner before build. Keep confidential user data and unreleased plans out of consumer AI tools beyond what I pasted.

Why it works — PRDs usually describe what a feature does when everything works, and the expensive surprises come from everything else. A structured pass across performance, failure states, privacy, and accessibility surfaces those requirements while they are still cheap to design for. Leaving targets as placeholders rather than inventing numbers keeps the PM and engineering in charge of the actual bar.