Product Experience
Understand how your product fits people's needs, how they get started and what happens when they use it.
Products, Services & Environments
See your product through the people who use it.
A product experience includes more than its features. People need to understand the offer, set it up, use it in their environment and find help when something goes wrong. We research these interactions to help your team identify user needs, task barriers and practical opportunities to improve.
What we look at
First-use and set-up friction
Feature discovery and adoption
Packaging, labelling and instructions
Concept clarity before build investment
How we study it
In-home and in-context product tests
Task-based usability sessions
Concept and prototype evaluation
Prioritised design recommendations
Research focus
Research at the right stage
Use this research when exploring a product idea, evaluating a prototype, preparing for launch or improving an existing product. The question changes with the stage: a concept study explores understanding and relevance; task testing examines use; an ongoing-use study explores experience over time.
A small business may focus on one product and a few important tasks. A larger organization may need comparisons across versions, audiences or markets. We agree the scope around the decision your team needs to make.
Research focus
Physical, digital and connected products
Research can cover physical products, websites, apps, software and products that combine hardware with digital controls. We examine relevant packaging, instructions, interfaces and support touchpoints within the agreed scope.
Tasks might include selecting an option, unboxing, assembly, account setup, finding a feature, completing everyday work or recovering from an error. Context matters: shared use, limited space, interruptions and device availability can affect the experience.
Our approach
How we study the experience
Interviews explore relevant needs and recent use. Concept and prototype evaluation examines understanding, expectations and proposed interactions. Task-based usability testing observes selected activities using a suitable version of the product.
In-home or in-context studies can investigate use in relevant settings where appropriate. Diaries can capture repeated use over time. Surveys, existing feedback or authorized analytics may complement the study. We select methods after defining the question rather than include every method in a fixed package.
From context to opportunity
Our research process
Plan the study. Select methods, participant criteria, test versions and appropriate safeguards
Prepare the experience. Confirm product availability, setup, logistics and the tasks participants can reasonably complete
Gather and analyze evidence. Identify barriers, expectations and differences, separating observations from reported experience
Recommend improvements. Connect findings to changes worth considering and make assumptions visible
Agree next steps. Identify proposals to validate and relevant follow-up measures where included
The output
What your team receives
Depending on scope, deliverables can include a needs assessment, annotated task findings, an experience map and prioritized recommendations. Findings may cover setup, controls, instructions, content, recurring use and support.
Reports explain the participants, product version, tasks and settings studied. We distinguish observed issues, participant opinions and hypotheses. A findings workshop helps your product, design and delivery teams agree actions. Detailed design and engineering work are separately scoped.
What we investigate
The questions we help you answer
Do people understand what the product offers? Does it address a need they recognize? Can intended users get started and complete important tasks? Which instructions or controls are unclear? Where do people require help or develop workarounds?
We also investigate differences between first use and familiar use, features people overlook and reasons an experience does not fit their routines. Reported interest or purchase intent is not treated as proof of future demand.
Research focus
Prepare for realistic, appropriate testing
Before fieldwork, we agree which products or prototypes will be used, who supplies them and how delivery, setup, return or disposal will be handled where relevant. Prototype limitations are documented so simulated behavior is not mistaken for actual product performance.
The client and responsible specialists must confirm that proposed products and activities are suitable for the study. We agree instructions, participation boundaries and how issues will be reported. User research is not a substitute for engineering, safety or specialist product assessments.
Global research
Relevant users and local contexts
Recruitment can consider experience level, current alternatives, use environment, language and access needs. Where relevant, we include both the person selecting the product and the person using it, reporting their perspectives separately.
For multi-market work, we agree local research arrangements and relevant product variants. Instructions, connectivity, service availability and everyday routines may differ. Study coverage and gaps are documented rather than assume one setting represents every market.
Research ethics
Respect participation and privacy
We agree consent, recording and reporting arrangements before research. Activities should avoid unnecessary sensitive information, and observation in homes or workplaces needs clear boundaries around private spaces and other people.
Public use of identifiable photos or recordings is not assumed from research participation. Test accounts and safe scenarios can be used where practical. Additional safeguards for particular participant groups or product categories are agreed before recruitment.
Clear boundaries
Use findings within their limits
Useful measures may include task completion, errors, assistance needed and reported ease. We agree definitions and interpret results within the sample, tasks and conditions studied.
Qualitative studies do not establish population prevalence, product-market fit or sales forecasts. Short-term use does not prove durability or long-term satisfaction. Research can inform product decisions but does not certify technical performance, accessibility compliance or safety, and we do not guarantee commercial outcomes.
Before we begin
Frequently asked questions
Yes. A concept or suitable prototype can answer focused questions about understanding and proposed use. We document what it cannot demonstrate.
No. Remote, research-setting or in-context sessions are selected according to the question, product and participation requirements.
Yes, with agreed tasks and a comparison design that considers relevant differences and learning effects. We make the basis and limits of the comparison clear.
Share the product stage, intended users, priority tasks and decisions you need to make. Include product examples or existing research if available. We will discuss scope, test arrangements, deliverables, timing and budget.
Let us help shape the next step
Your product has a UX problem.
Let’s find and fix it.
Next research service Service Experience Your product has a UX problem. Let’s find and fix it. Contact Us Tell us what you need to learn about your product.