People & Interaction Experience
Understand what happens when people communicate, seek help and work with your teams, tools and services.
People & Behavior
People & Interaction Experience research that informs clearer decisions.
An interaction can be a conversation with a staff member, a handover between teams or a task completed through a system. We research how people understand and respond to these moments, helping your team identify communication gaps, unclear responsibilities and practical barriers to progress.
What we look at
Task success, errors and recovery paths
Communication gaps and unclear next steps
Task time, assistance and reported effort
Differences between intended and actual behaviour
How we study it
Moderated lab and remote usability testing
Shadowing and interaction observation
Heuristic review paired with behavioural evidence
Prioritized recommendations linked to user needs
When to research
When this research helps
Use this research when people repeatedly ask for clarification, receive inconsistent explanations, struggle to get help or lose context during a handover. It can also inform the design of staff-assisted services, collaborative workflows and self-service interactions.
A small business may focus on one recurring interaction. A larger organization may need to compare roles, channels or locations. We define the scope around the experience problem and decisions your team needs to make.
What we investigate
What we help you understand
Do people understand what is being explained or requested? Are responsibilities and next steps clear? Can they ask questions, recover from misunderstandings and find appropriate help? Where does the interaction create unnecessary effort or uncertainty?
We examine both the person receiving the service and the people delivering it where relevant. Staff may face information gaps or system constraints that affect the interaction. We keep these perspectives distinct rather than assume one account represents everyone involved.
Our approach
How we study interactions
Interviews explore specific recent experiences. Observation and contextual inquiry examine agreed interactions as they happen. Task-based usability testing studies how intended users interpret and use a system, while role-based scenarios can explore a proposed service exchange.
Journey and workflow mapping connect interactions to earlier and later steps. Authorized feedback or support records can provide additional context. Expert review observations are kept separate from participant findings, and simulated interactions are identified as such.
From context to opportunity
Our research process
Plan the study. Select methods, participant roles, scenarios and appropriate access and recording arrangements
Gather evidence. Explore recent experiences or observe agreed tasks with neutral questions and clear boundaries
Analyze barriers. Identify misunderstandings, task difficulties, handover gaps and relevant differences between groups
Recommend improvements. Connect findings to changes in information, guidance, interfaces, support or processes
Agree validation. Identify proposed changes to test, responsible teams and relevant measures where in scope
The output
What your team receives
Depending on scope, deliverables can include interaction or workflow maps, annotated task findings, communication gaps and a prioritized recommendation plan. Reports explain the participants, situations and tasks covered.
We distinguish observed behavior, participant explanations and researcher interpretation. A findings workshop helps your teams agree next steps. Recommendations for scripts, training, design or process changes may require further validation; implementation is separately scoped.
From insight to action
People-to-people and people-to-system interactions
Research can cover customer conversations, support exchanges, team coordination, partner handovers and staff-assisted tasks. It can also examine forms, interfaces, connected devices and transitions between human assistance and self-service.
The focus is the interaction in context, not a judgment of someone's personality or character. We consider the information, tools, environment and processes involved rather than attribute every difficulty to an individual.
Research ethics
Participation without unnecessary pressure
We agree consent, recording, access and reporting arrangements before fieldwork. Observation should not quietly include people who have not been covered by the agreed participation arrangements. Sensitive or consequential tasks can use safe scenarios or test accounts where practical.
For workplace or service interactions, we discuss how supervisory relationships and client presence could affect candid feedback. Reporting safeguards address identifiable details, especially in small teams. This research is not covert monitoring or an individual performance appraisal.
Research in context
Different contexts can change the interaction
Language, access needs, experience level and available channels can affect how an interaction works. We agree relevant participant groups and contexts before recruitment and document who was not covered.
For multi-market work, local research arrangements and appropriate language support are scoped in advance. We investigate differences without treating nationality or background as a fixed explanation for individual behavior.
Measurement
Measure what the evidence supports
Relevant measures may include task completion, misunderstandings, repeated explanations, assistance required and participant-reported effort. We define measures around the study question rather than treat every pause as a problem.
Observed behavior does not reveal a person's internal state. Session time is not automatically a measure of cognitive load, and qualitative findings do not establish population prevalence. Research can inform improvements but does not guarantee conversion, efficiency or a commercial outcome.
Before we begin
Frequently asked questions
No. Usability testing is one method. The study can also examine conversations, collaboration and handovers where they shape a product or service experience.
Yes, where participation and access arrangements support it. We report relevant differences between roles rather than combine them into one assumed perspective.
Yes. Suitable prototypes or role-based scenarios can explore comprehension and task flow. Simulated findings are not treated as proof of real-world outcomes.
Share the interaction, people involved, setting and difficulties you want to understand. Include existing feedback if available. We will discuss scope, participation arrangements, deliverables, timing and budget.
Let us help shape the next step
Your interaction has a UX problem.
Let’s find and fix it.
Next research service Customer Experience Your interaction has a UX problem. Let’s find and fix it. Contact Us Tell us which interactions need attention.