What is a user requirement?
In simple terms, a user requirement is what the user wants the website to be able to do.
The user may be internal or external. An internal user is someone in the company that is managing the website or driving the business of the website. An external user is someone who uses the website.
An example of an internal user requirement
An internal user may want all content to be approved by the website’s manager before it is published. This is called a workflow requirement. When we document this requirement, we should also ask ourselves:
- What if the manager goes on holiday?
- Can anyone override the need for manager approval?
- Are managers on rotation?
An example of an external user requirement
An external user may want to be able to buy bulk t-shirts from your website. The ability to buy in bulk is a functionality. When we document this requirement, we should also ask ourselves:
- Is there a maximum number of tees a single user can buy?
- How often will this maximum number change?
- Should users be able to key in the quantity or select from a list?
User requirements should always be written in plain English. User requirements are not technical requirements so you can leave out all the technical jargon. It should just say clearly what the system is expected to do.
Requirements, ideally, should be mapped to business objectives. Or you might end up with a huge document on your hand detailing a site that will take 200 years to build!