Project Smart ~ Exploring trends and developments in project management today

Calendar icon
Adobe PDF icon

What is User Requirements Capture?

~ By Damian Rees

Many sticky notes with the word want on them and one with the word need

User Requirements Capture is a research exercise that is undertaken early in a project lifecycle to establish and qualify the scope of the project. The aim of the research is to understand the product from a user's perspective, and to establish users' common needs and expectations. The user requirements capture is useful for projects that have a lack of focus or to validate the existing project scope. The research provides an independent user perspective when a project has been created purely to fulfil a business need. The requirements capture findings are then used to balance the business goals with the user needs to ensure the project is a success.

The user requirement capture project can include many different usability research methodologies including; surveys, structured and unstructured interviews, usability tests, and competitor analysis. Typically, the research is undertaken on a one-to-one basis between a usability consultant and an end user, with an average user requirements capture project including up to fifteen one-to-one interviews.

Advantages

The main advantages of a user requirements capture is the saving of time and money by validating the scope of a project against its users' needs and expectations before any work begins. This in turn mitigates the risk of the project launching and failing to meet its objectives (increased online conversion, registrations, visits, etc.). The research will also uncover critical information to improve the end result by answering questions such as; is the current target audience realistic? Can the project be more successful with a different focus? And is the project worth investing in? There is also an important intangible benefit where the project team gains a deep insight into users and their needs at the very beginning, allowing them to remain focused on serving users throughout the duration of the project.

Disadvantages

A user requirements capture will increase the time of the planning phase, which can be a frustration if the project team is keen to get cracking. However, this time is easily saved later in the project due to making quicker, more informed decisions based on user needs. The research can also highlight a conflict in different users' needs and expectations, which may require a user experience consultant to work with the team on making sense of the conflict and isolating a solution. As this method requires experienced user research professionals to ensure they capture true user requirements rather than unfocused conjecture and opinion, it can add an unexpected cost to the start of a project.

Conclusion

Despite the potential costs incurred early in the project lifecycle, a user requirements capture is an essential tool for any project which interfaces between the business and its users. Understanding user needs and requirements at the beginning of the project helps ensure the product is fully adopted by its users, leading to business success, and in more extreme cases a user requirements capture can save a business from investing time and money in a product which is not required by the target audience.


Experience Solutions conducts customer research to help make their clients' products and services easier to use. Experience Solutions specialise in customer experience, user centred design, and usability research and consultancy on all aspects of a customer's journey.


Comments

Be the first to comment on this article.

Add a comment



(never displayed)



 
1500
What is the next number: 10, 12, 14, ..?
Notify me of new comments via email.
Remember my form inputs on this computer.

So You Want to Be a Project Manager

Businessman smiling with hands together

Not sure what skills it takes to become a Project Manager? This article lists the six key skills required to be a successful project manager.

Work Breakdown Structure 101

Hierarchy icons on a white background

Work Breakdown Structure is a tool project managers use to break projects down into manageable pieces. Here's why you need one and how to create your own.

Is Project Management Certification Worth It?

University students in a classroom watching a presentation

Do recognised professional credentials increase your worth in the jobs market? Will the effort of studying to pass the exam improve your career prospects?

How Agile Practices Reduce Requirements Risks

Road warning sign - Risks Ahead

Every software project carries some risk, but many of these risks can be mitigated. That's true of problems related to product requirements.

PROJECT SMART is the project management resource that helps managers at all levels improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With weekly exclusive updates, we keep you in touch with the latest project management thinking.

WE ARE CONNECTED ~ Follow us on social media to get regular updates and opinion on what's happening in the world of project management.


Latest Comments

Duncan commented on…
10 Rules of Highly Successful Project Management
- Mon 26 September 7:50am

John Corbett commented on…
10 Rules of Highly Successful Project Management
- Mon 19 September 1:36pm

London Management Centre commented on…
Get Maximum Benefits of Merging Top-down and Bottom-up Project Management
- Mon 19 September 11:29am

Latest tweets

General Project Management • Re: Software Product Delivery Plan for an Agile project https://t.co/qlwUTdDgAa #pm #projectsmart about 16 hours ago

General Project Management • Re: Best/cheapest online PRINCE2 Foundation course with exam included https://t.co/qRvyY1ZXVj #pm #projectsmart about 16 hours ago

Here are some basic rules of reporting status that you can use to further your reputation https://t.co/eOfIohem8R #projectsmart #pmot about 1 day ago