Product
Contextual Enquiry
Understand how your users really work — on their tasks, with their workarounds.
Most teams research users by asking what they want — in a survey, a focus group, or a sterile usability lab. We do the opposite: we sit beside people while they do their real work, in their own environment, and watch what they actually do — the shortcuts, the workarounds, the moments they get stuck. You get findings grounded in observed behaviour, not stated preference.
Features
Deliverables & Impact
In-context field observation
We observe the real task in the environment where it actually happens — the tools, interruptions, and constraints that a lab or call setting strips away.
Master–apprentice interviewing
The user leads and does their work; we follow and ask in the moment. It surfaces the reasoning and the workarounds people never think to mention.
Workaround & friction mapping
We capture the unofficial process — the spreadsheets on the side, the steps skipped, the re-entry — so you see where the real product is failing them.
Interpretation & affinity synthesis
Raw observation is turned into patterns and shared meaning, so findings are an agreed picture of the work rather than a pile of anecdotes.
Design-ready insight handover
Findings are framed for the people who’ll act on them — clear implications for design and product, not a research report that gets filed and forgotten.
Use Cases
Technical Scenarios &
Implementations
Designing for a specialist domain you don’t work in
Your users are clinicians, tradespeople, or operators in a field your team doesn’t live in. We get you inside that work so the design isn’t built on outsider assumptions.
Redesigning a tool people actively work around
Adoption is low and shadow processes have grown up beside the product. We map what people actually do instead, so the redesign fixes the real friction.
Validating assumptions before a costly build
A big feature or platform is on the roadmap. We pressure-test the thinking against observed behaviour before the budget is committed.
Reconciling contradictory survey and analytics signals
Your quantitative data says one thing and your interviews say another. Field observation explains the gap by showing what users genuinely do.
Onboarding a team to an unfamiliar user base
A new product squad needs to understand who they’re building for, fast. Contextual sessions give them a shared, grounded mental model to design from.
FAQs
Common Questions
Isn’t this just user interviews?
+
No. An interview asks people to recall and describe their work from memory, away from the task — and memory edits heavily. Contextual enquiry watches the work as it happens, in context, so you capture the steps and workarounds people never think to report.
How many users do we need?
+
Fewer than you’d expect. This is depth over breadth — a handful of well-chosen sessions with people doing the real work surfaces the dominant patterns. It’s qualitative discovery, not a statistically powered survey.
Our users are remote — does this still work?
+
Yes. Remote contextual enquiry runs over screen-share while the user does their actual work, with the same master–apprentice approach. You lose some of the physical environment, but the core — observing the real task in real time — holds.
Won’t this slow our design process down?
+
It front-loads a small amount of time to remove a large amount of rework. Designing on observed reality is far cheaper than building the wrong thing and discovering it after launch.
How is this different from usability testing?
+
Different question entirely. Usability testing checks whether people can use a design you’ve already made; contextual enquiry discovers the real tasks and context before there’s a design to test. They pair naturally — enquiry shapes what to build, testing validates how well it works. See Usability Testing.
Get Started
Ready to get started with Contextual Enquiry?
Or contact us directly with more details.