Product Spec Examples
Three spec shapes for different kinds of work — feature, experiment, and platform.
Feature spec (user-facing)
Example: "Add CSV export to reporting." Problem: customers manually copy data for board decks. Goal: reduce weekly export requests to support. In scope: CSV for standard reports. Out of scope: scheduled exports, API access.
Experiment spec
Example: "Test onboarding checklist vs. video." Hypothesis: checklist increases activation by 10%. Duration: 2 weeks. Kill criteria: no lift and higher drop-off on step 2.
Platform / enabler spec
Example: "Migrate auth to OAuth2 provider." Problem: security audit findings. Success: pass pen test; zero user-facing regression. Consumers: all teams using auth — link to migration checklist.
More detail when...
- Many teams depend on the output
- Rollback is expensive
- Compliance or security involved
- Novel UX or domain logic
Less detail when...
- Single squad owns end-to-end
- Easy to revert
- Discovery still active
- Prototype is the spec