Product Specification
A feature specification that covers states, edge cases and accessibility rather than only the happy path.
Definition
A specification defines what will be built precisely enough to implement and to test. Most specifications fail by describing only the successful case.
Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.
Fill it in
Loading your draft…
Saved in this browser only. Nothing is sent anywhere.
Definition
One paragraph. If it takes more, the scope is probably too large.
What the user achieves, and how you would verify it in a test.
Explicit boundaries prevent scope drift during build.
Behaviour
Steps, with the system's response at each.
Empty, loading, partial, error, success, offline, permission denied.
Zero, one, many, maximum, longest content, slowest response, permission variations.
Requirements
Keyboard, focus, labels, announcements, contrast, motion.
Every string the interface needs, written out, not described.
Anything requiring a decision before build. Assign each one.
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Applies when you are designing
Often used with
These usually appear in the same screen or the same decision.
- Feature Idea to UX SpecificationAI workflow
- PRD to User FlowAI workflow
- Jobs to Be DoneResearch method
- Design BriefTemplate
- Story MapTemplate
- User FlowTemplate
- Axure RPTool
- ConfluenceTool
- NotionTool
- ZeplinTool
- Visual StatesUI foundation
- Design HandoffWorkflow
- DiscoveryWorkflow
Short definition
The one-paragraph version, for when that is all you need.
- Acceptance CriteriaTerm
- Edge CaseTerm
- HandoffTerm
- Happy PathTerm
- User StoryTerm