LinkedIn Xing Instagram
← All Services

Qualitative User Research

Planning and conducting interviews, contextual inquiry, and usability studies — surfacing what people actually do, not just what they say in surveys.

What qualitative research actually is

Qualitative user research is the work of understanding users through direct conversation and observation, rather than through metrics and analytics. It answers questions like why something is happening, what users are trying to accomplish, and where products fail to support those goals.

The methods are well-established: structured and semi-structured interviews, contextual inquiry (observing users in their actual work environment), usability studies (watching users attempt specific tasks). What makes the difference is how the research is framed, who is recruited, what is asked, and how the findings are turned into actionable insight.

Qualitative research is conducted for both B2B and B2C products, in person and remote, in German and English. The output is a synthesized findings document with clear themes, supporting evidence, and recommendations.

When qualitative research fits

  • A team's assumptions about users need to be validated or challenged
  • A new product or feature is being planned and user needs are unclear
  • An existing product has performance problems that quantitative data cannot explain
  • Internal stakeholders disagree about user priorities and need a neutral basis for decisions
  • Accessibility or specialized user needs need to be understood in depth
  • The product serves a complex domain (enterprise, healthcare, public-sector) where general patterns do not apply

Not the right approach when the question is about scale ("how many users do X") — that needs quantitative data. And not the right approach when there is no time to act on findings — research without follow-through is wasted budget.

What you get

  • Research plan with goals, questions, and method
  • Recruiting brief and screener
  • Interview guide or task script
  • Recordings and notes from all sessions (with consent)
  • Synthesized findings document with themes, quotes, and recommendations
  • Optional: stakeholder presentation walking through findings
  • Optional: video highlights for internal use

The synthesis is the core deliverable. Raw interview transcripts are useful, but what teams actually need is a clear set of themes, supported by evidence, with recommendations on what to do about them.

How the process runs

A typical qualitative research engagement runs across three to four weeks:

  1. Research planning (three to five days): goals defined, questions formulated, recruiting brief written.
  2. Recruiting (one to two weeks, often in parallel with planning): finding the right participants is usually the slowest part. Recruiting can be run independently or with a recruiter.
  3. Fieldwork (one to two weeks): interviews and observations conducted. Typically six to twelve sessions per study.
  4. Synthesis (three to five days): patterns identified, themes written up, recommendations formulated.
  5. Handover (half day): findings presented to the team, questions answered.

For tighter timelines, the process can be compressed — but recruiting tends to be the bottleneck regardless of methodology.

Frequently asked questions

How many participants do you typically recruit?

For exploratory interviews, six to ten participants per user segment is a common target. For usability studies on a focused flow, five to eight participants is usually sufficient — patterns become clear after that. For more complex studies with multiple user segments, the number scales accordingly.

Can you handle the recruiting?

Yes. Recruiting can be run through professional panels, my own network, or the client's user base. For specialized segments (enterprise users, healthcare professionals, public-sector staff), recruiting takes longer and is best planned in advance.

Do you do quantitative research?

Qualitative research is my specialty, but I work with quantitative data when it complements the qualitative work. Surveys can be designed to validate qualitative findings at scale, or to identify questions worth exploring in depth. For pure quantitative studies (large-N surveys, A/B tests, analytics analysis), specialists are usually recommended.

In what languages can the research be conducted?

German and English natively. For other languages, the work is done with a translator or local researcher, depending on the project.

How do you handle research ethics and consent?

Standard practice: written informed consent before sessions, GDPR-compliant data handling, anonymized findings unless quotes are explicitly cleared, secure storage of recordings, and a clear retention and deletion policy. For sensitive contexts (healthcare, public-sector), additional protocols may apply.

Can research be done remotely?

Yes, most contemporary research is remote, conducted via video call with screen sharing. In-person research is valuable for contextual inquiry — understanding how users work in their actual environment — but remote works well for interviews and usability studies. The method should fit the question, not the other way around.

What is the difference between an interview and a usability study?

Interviews focus on understanding: what users do, why they do it, what they need. Usability studies focus on testing: watching users attempt specific tasks with a product or prototype, identifying where they struggle. Both methods are often combined in one project, with interviews surfacing context and usability studies testing solutions.

Can findings be integrated into a Figma file or design system?

Yes. Findings can be linked to specific UI elements, components, or flows in Figma, making them actionable for the design team. For larger engagements, this can be set up as part of the synthesis phase.

How do you combine several usability studies into one insights deck?

First I bring all findings into one shared format: observation, affected task, segment, and source. Then I cluster them across all studies by theme, with AI helping on the first grouping while I review and name the clusters. A finding that shows up in several studies carries more weight than one from a single session. The deck then has one insight per theme, with evidence from the studies and a recommendation. I keep contradictions between studies visible instead of smoothing them over, because they often point to different segments or contexts.

Need to understand your users better?

Book a 30-minute conversation to talk through your research needs and the best way forward.

Get in touch