Product Requirement
A documented condition, capability, or constraint a product must satisfy to address a need or objective.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/product-requirement/
01What it means
A product requirement states what a product or service must do, provide, or constrain in a context. It may describe behavior, quality, compliance, integration, or an outcome boundary; it is broader than a feature request and should remain separate from implementation design.[1][2]
02Why it matters
Explicit requirements expose assumptions and give product, design, engineering, operations, and quality collaborators a common basis for decisions and verification.
03When to use it
Use requirements when a condition needs shared understanding, traceability, or validation. Keep them proportional to uncertainty and avoid freezing speculative detail before discovery.
04How it works
- Identify the user, business, policy, or system need.
- State the required condition and context.
- Separate required behavior from proposed solution.
- Define measurable acceptance or verification conditions.
- Review, prioritize, trace, and revise as evidence changes.
05A practical example
A fintech requirement says eligible customers must be able to export transaction history in a usable machine-readable format, while leaving the file format and interface open for discovery.
06Where it breaks
Requirements can encode outdated assumptions, conflict with one another, or be mistaken for a guarantee of value; they do not replace research or design.
Common mistakes
- Copying stakeholder requests without identifying the underlying need.
- Specifying implementation instead of required behavior.
- Writing vague adjectives without observable thresholds.
07Sources
- ISO/IEC/IEEE 29148:2018ISO · International standardISO/IEC/IEEE 29148:2018
- Writing user needsGOV.UK Service Manual · Government service guidanceWriting user needs