Requirements gathering is a very crucial step before you start design or development. Identifying the variation of the requirement needs is the core challenge. Understand the context, focus on the needs & challenges to discover the problem should be the core focus of the requirement gathering method.

“Write down the problem correctly to see the correct solution.”


No ideas are bad ideas. This should be the focal point for your brainstorming and ideation sessions. Whilst true that many brainstorming sessions are timely and generate terrible ideas. It is still a platform for bad ideas to be converted into brilliant ideas. Make sure you get everyone involved so that the ideas can flow.

Brainstorming sparks conceptual thinking along with creativity and is a great method for generating requirements early on. What is great about this part of the UX requirements process is that it doesn’t rely on any research.

After you’ve scanned through the requirements needed from the brainstorming session, you want to capture further requirements by utilising stakeholder interviews. This is more highlevel than a free-for-all brainstorming session and should be treated with more severity; however, the conversational tone should be maintained throughout.

Stakeholder interviews

This stage allows you to coax information from key stakeholders to generate more substantial and fitting requirements. You can ask questions such as:

  • How does this product fit the overall strategy?
  • Who are our biggest competitors?
  • Who are our customers both present and future; and how do you want that to be different in 2 or 5 years?
  • What qualities do you want our users to attribute to our product?
  • How might we meet the business need and how?
  • Who will use this feature?