User interviews specialists for your dedicated team.

Where User interviews fits in a long-term product team.

What people say they would do is a poor predictor of what they do. Asking "would you use this" produces polite agreement, while asking "tell me about the last time you had this problem" produces an account of real behaviour, which is what to design from.

Leading questions are the standard failure and they are easy to fall into when you have a hypothesis. "Was that frustrating?" plants the answer; "what happened next?" does not. Interview technique is a real skill, well beyond being a good conversationalist.

What your dedicated team does with User interviews.

Analysis is the part that gets cut when time is short, and it is where the value is. Ten recorded interviews with no synthesis is ten hours of audio; the same interviews analysed into patterns are a basis for decisions.

Budgeting analysis time as seriously as session time is part of how research is scoped under outsource ux design.

Common User interviews use cases.

• Past behaviour over stated intent Accounts of what happened, which predict far better than opinions.
• Technique that avoids planting answers Open questions, because a hypothesis makes leading questions easy.
• Analysis budgeted properly Synthesis time planned, since unanalysed sessions are only recordings.

Adding User interviews skills to your team.

Interview research sits with the designers on your team, with analysis time scoped alongside session time.

You can add User interviews capacity as one dedicated specialist or as part of a wider remote team, managed by a service delivery manager from our offices in Thailand. Companies hire dedicated developers this way under one agreement and one monthly fee.