Products
Understand how people choose, set up and use your products. Turn evidence from physical, digital and connected experiences into clear improvement priorities.
Product research
See your product through the people who use it
A product can work as intended and still be difficult to understand, set up or fit into everyday life. People may miss a useful feature, struggle with instructions or develop workarounds your team has never seen. Product user experience research helps you understand these moments before deciding what to change.
UX Pacific studies the experience around physical products, digital products and products that connect the two. We explore what people need to accomplish, what helps them and what gets in their way. The focus is on practical evidence for product decisions, not simply collecting opinions or rating appearance.
When to research
When product research is useful
Use the study area when you are exploring a new product, assessing a concept, preparing a launch or improving something already in use. It is also relevant when support requests, returns, low feature adoption or inconsistent feedback suggest an experience problem, but do not explain its cause.
A smaller team may need evidence for one important decision. An established business may need to investigate several product lines, user groups or markets. We define the study around your question, product stage and constraints, rather than assuming every project needs a large research programme.
What we investigate
Questions we help you answer
Can people understand what the product does and whether it meets their needs? Can they unpack, assemble, activate or configure it without unnecessary help? Which tasks cause confusion, errors or extra effort? Which features support real needs, and which remain unused? What changes when the product is shared, used repeatedly or used under time pressure?
-
01
Choosing and understanding
Explore how people interpret product information, compare alternatives and understand features, limitations and intended use. Identify gaps between what the product communicates and what people expect.
-
02
First use and setup
Study packaging, opening, assembly, installation, registration and initial use where relevant. See whether people can find the right information, complete the steps and recognise that setup has succeeded.
-
03
Everyday use and connected interactions
Understand routines, handling, controls, feature discovery and recurring tasks. For connected products, examine the transitions between hardware, apps, accounts and notifications, including what happens when connectivity or access is interrupted.
-
04
Help, maintenance and the next decision
Explore troubleshooting, cleaning, maintenance, replenishment, repair and replacement as appropriate. Where returns or abandonment matter, investigate the surrounding experience without assuming the product itself is the only explanation.
Our approach
How we gather evidence
The method depends on the decision. Interviews explore needs and expectations. Contextual observation examines use in its actual setting. Usability testing reveals difficulties with agreed tasks.
From insight to action
From your question to improvement priorities
First, we clarify the decision, intended users, product stage and available evidence. We then agree the participant criteria, tasks, setting, materials and outputs. For physical products, this includes practical arrangements such as shipping, installation, safe handling and return where needed.
During the study, we look for recurring barriers and differences between users or situations. Findings are translated into priorities your team can discuss and act on. Where a change needs further validation, we make that clear rather than presenting a recommendation as a proven solution.
The output
What your team receives
Agreed deliverables can include a summary of user needs, task-level findings, an experience map, setup and instruction issues, and prioritised improvement opportunities. Each priority should explain the problem, supporting evidence and relevant user context. Consented recordings or excerpts may be included where agreed.
A findings discussion helps product, design, engineering, customer support and commercial teams understand the implications. The proposal specifies the outputs and level of detail, so you know what the study will deliver before it begins.
Research in context
Different users, settings and markets
The buyer and the user are not always the same person. We consider who chooses, sets up, uses, maintains or supports the product, and which perspectives the study needs. Relevant differences may include experience level, access needs, language, context, routines or market conditions.
Find the right service
Choose the research service around your decision
For a focused study, explore Product Experience Research. If the question centres on an interface, see Website & Mobile App Experience. For connected interactions, explore Technology Experience. When the issue extends into support or the wider lifecycle, Service Experience or Journey Experience may be more relevant.
Research principles
Clear boundaries, responsible research
Participant consent, recording permissions, confidential materials and appropriate handling are agreed as part of the study. Product experience research is not a substitute for engineering validation, safety certification, clinical evaluation or specialist compliance testing. These require separately defined expertise and assessment.
Findings reflect the study design and conditions. A prototype may not behave like a finished product, and short-term testing may not reveal long-term wear or changing routines. We explain these limits so your team can use the evidence appropriately.
Before we begin
Frequently asked questions
Do we need a finished product?
No. Concepts, models, packaging samples or prototypes can support an early study. We agree what each material can realistically test and what must wait until a working product is available.
Can research explain returns or low adoption?
It can investigate experience-related contributors and test possible explanations. Commercial records and other evidence may also be needed. Research does not automatically establish a single cause or guarantee a reduction in returns.
What should we share to start?
Tell us about the product, intended users, current stage, target markets and decision you need to make. Include available samples or prototypes, known issues and timing constraints. You do not need to choose a method before contacting us.
Let us help shape the next step
Your product has a UX problem.
Let’s find and fix it.
Tell us what you need to learn we will help shape a practical research approach around your decision.