Requirements Gathering

At the start of any project it’s important to properly understand the project requirements. Specifically confusion around understanding the business, its users, and the project objectives as a whole.

Banner image that represents requirements gathering

Gathering early project requirements

The first stage in the UX process should be research, which is divided into collecting business, user and technical data. After all, every UX project has its own unique requirements, and research is used to determine what they are.

Business requirements

Understanding the business requirements should outline what the product hopes to achieve for the business itself. This may include overall project scope, rough timelines, and business goals. They can be obtained through a UX Workshop, stakeholder interviews, or traditional meetings and discussions. The majority of these should happen after UX proposals and contract agreements, although a certain amount of business requirements should be at least discussed prior to any professional agreement to ensure the client is hiring the correct UX specialist for the job.

User requirements

The user’s needs are pivotal to the design thinking. The requirements should have a huge influence on the UX Design. Using the UX expertise will help establish what they might need it isn’t a good idea to guess at their needs. They should be gathered through UX research, conducting user interviews, user surveys, and user testing.

Technical requirements

The UX Design process can never ignore or separate itself from technical requirements and constraints of a project. After all we’re in a digital world and interfaces are always viewed through technical and electronic devices.

Generally, technical requirements can be separated into functional and non-functional requirements. UX Design should focus on what the product should be able to do and designs may include functional specifications or notes that go alongside user-interface visuals, wireframes or prototypes. Non-functional requirements involve a UX Designer less often, however their design may influence them. Non-functional requirements include things like performance (e.g. loading speeds) and maintenance (e.g. how something is updated in WordPress).

Read about Research & Strategy >

Looking to improve your UX?

Whatever the challenge, whatever the stage. I’d be happy to discuss about how I might get involved in your project.