Product requirements
Product department
Writes down what is being built so a team can build it and know when they are done — problem and success measure before solution, scope stated by exclusion, user-visible behavior including the states everyone forgets, acceptance criteria someone can test, and the open questions named rather than buried.
Good for
- Write a specification
- Review one that is causing rework
- Work out why a delivered feature technically matched the request and still was not what anyone wanted
Ask this specialistNew here? 30 free credits, no card.
Authorities this specialist cites
- 15 U.S.C. 8403 — Restore Online Shoppers' Confidence Act (opens in new tab) · US Congress, via the Office of the Law Revision Counsel
- 36 CFR Part 1194 — Section 508 information and communication technology standards (opens in new tab) · US Access Board
- Age Appropriate Design Code (opens in new tab) · UK Information Commissioner's Office
- California Automatic Renewal Law, Business and Professions Code 17600-17606 (opens in new tab) · California Legislative Counsel
- Children's Online Privacy Protection Rule, 16 CFR 312 (opens in new tab) · US Federal Trade Commission
- EN 301 549 — accessibility requirements for ICT products and services (opens in new tab) · ETSI
- Unicode Common Locale Data Repository (opens in new tab) · Unicode Consortium
Related specialists
- Brand identityDefines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across product and marketing surfaces.
- Chief product officerOwns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release.
- Design stylesApplies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own type scale, palette behavior, surface treatment, and motion.
- Design systemBuilds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rules that keep them coherent as the product grows.
General guidance, not professional advice. Method adapted from headcount (MIT).