User experience (UX) research is the process of gathering evidence to inform software design decisions. Instead of relying on assumptions about users, their goals and their context, we use specific methods to observe them directly. This isn't an optional phase or a final polish; for our UI/UX design projects, it is a foundational activity for managing risk. Building the wrong product, or building the right product the wrong way, is the most expensive mistake in software development. Research is the primary tool for avoiding it.
Our process uses research to answer practical questions. Who is the target user for an agri-commerce platform? What specific information does a real estate professional need on their dashboard? What workflow must a food ordering app support on an unreliable mobile connection? The answers define the product's requirements.
Core research methods we use
Different project stages require different types of information. We select from a range of qualitative and quantitative methods to get the necessary data, whether we are exploring a new concept or validating a specific interface detail.
Contextual inquiry
To understand a user's workflow, we must observe it in their own environment. We watch users perform their actual tasks, asking questions to understand their motivations and decision-making processes. This method is effective at uncovering unstated needs and workarounds that users might not think to mention in a standard interview.
User interviews
One-on-one interviews help us explore a user's attitudes, beliefs and past experiences. These are semi-structured conversations, not rigid questionnaires. The goal is to uncover the 'why' behind a user's actions, providing qualitative depth that complements quantitative data from surveys or analytics.
Usability testing
We test prototypes with real users to identify usability problems before writing code. We give a user a representative task to complete, such as finding a product or filling out a form, and observe where they struggle. This is an iterative process; we test, fix the identified issues and test again to validate the solution.
Card sorting and tree testing
To design effective information architecture and navigation, we need to understand a user's mental model. In a card sorting session, we ask users to group topics into categories that make sense to them. In a tree test, we ask them to find specific information in a proposed site structure. The results directly inform the product's sitemap and menu systems.
The outputs of UX research
Research activities produce more than just notes. They generate concrete artefacts that guide the entire project team, from designers and developers to product managers. These documents create a shared understanding of the user and the problems we are tasked with solving.
Personas and journey maps
Data from interviews and observation is synthesised into user personas. These are not just demographic profiles; they are detailed archetypes that describe a user's goals, motivations and pain points. We then map these personas' interactions with the product in a user journey map, identifying opportunities for improvement at each step.
Data-supported design decisions
When we propose a design, we can point to the research that supports it. A decision to use a particular navigation pattern or label a button a certain way is backed by evidence from a tree test or usability session. This moves conversations away from subjective preference and towards a shared focus on user outcomes.
Prioritised feature sets
Research helps teams distinguish between essential features and low-priority requests. By understanding the core tasks users need to accomplish, we can focus development effort where it will have the most impact. This is critical for managing scope and delivering a functional product on schedule.
The necessary trade-offs of research
UX research is not a cost-free activity and every method involves compromises. Acknowledging these trade-offs is necessary for planning a realistic project.
Time versus certainty
Conducting research adds time to the initial phases of a project. The trade-off is that this upfront investment significantly reduces the risk of building a product that requires expensive changes or fails to find an audience after launch. The choice is not whether to spend the time, but whether to spend it on proactive research or reactive fixes.
Depth versus breadth
No project has the budget to research every aspect of a product in exhaustive detail. We must prioritise. We might conduct deep contextual inquiry for one critical user journey while using a more rapid survey for a less critical one. The trade-off is between gaining a rich understanding of a narrow area and a general understanding of the whole system.
Finding the right participants
The value of research depends entirely on the quality of the participants. For some products, especially in niche B2B domains, recruiting users who match the target profile can be difficult and time-consuming. The trade-off is often between delaying a project to find ideal participants and proceeding with 'good enough' proxies who are more readily available.
Research is a continuous process
Launching a product is not the end of the research process. User needs change, market conditions shift and new technologies create new possibilities. Post-launch, we use analytics data, user feedback channels and follow-up studies to monitor performance and identify areas for future improvement. This ensures the product adapts and remains relevant. By integrating research into the entire product lifecycle, we build a culture focused on delivering sustained value to the end user.

We have built this
The Bar Council of Gujarat
The statutory body for the legal profession in Gujarat needed services that work for advocates, law students and the public. We designed and built its website, its Android and iOS app and the admin panel behind them, around clear information and simple navigation on desktop, tablet and phone.
Want this for your business?
Ask ET on our website, or book a free 30-minute call with a project lead, not a salesperson.


