User interview

Illustration that represents a light bulb

1. Understand

On the first we stay in the problem space, challenging our understanding of the problem.This is some text inside of a div block.

Illustration that represents some working tools

2. Ideate

On the second day we gather inspiration, ideate and sketch solutions together.

Illustration that represents a futuristic mobile interface

3. Prototype

On the third day we turn the most voted sketches into a prototype and prepare to meet the users.

Illustration that represents some bubble talks

4. Test

On the fourth and final day we test the prototype with users and round off the sprint together.

How it works

User interviews are one of the most fundamental research methods we have and are often part of larger design processes in some shape or form.

When you want to understand your end-users, you can either observe them or talk to them. Observing them gives you honest answers about what they do, but to really understand the underlying motivations that drive them, their expectations and their mental model of how things should work, you will need to talk to them.

Interviewing is all about understanding the other person. Lead the conversation to the areas you are interested in, learn using open questions and active listening skills.

Understand

25-55 minutes

Product Owner, Business Analyst, UX Designer, Developer, Quality assurer

Before

1. Involve your team. When you run interviews, try to include more than one team member but no more than three. Running it alone can make it challenging to take notes, while inviting the entire team can be intimidating to the user. Regardless of how many you are, ask for consent in compliance with GDPR to record the interview so that all team members can watch the interview.

2. Assign roles. One person asks the questions and does the talking, one person takes notes and one can make sure the recording works. The interviewer can take breaks between topics and ask other members if they have something they want to ask.

During

3. Show interest. Be genuinely interested in the topic and the person you are interviewing. This creates trust and people are more enthusiastic to elaborate on things on their own.

4. Do not judge. You are there to learn about the other person, not correct them or engage in debates.

5. Reflect constantly. Don’t assume that you understood everything. Go back and see if you got it right. Quite often you hear “Oh I didn’t mean it like that, let me give you another example…”.

6. Clarify your doubts. The interview is the best moment to clarify things you are not sure about. If you are not sure what the other person meant when they said something – ask them. “When you were talking about invoices, you meant…?”. There is no use going back to the office with uncertainties.

After

7. Analyse your findings. Go through your notes with the team and fill in any gaps with help from recordings.

8. Summarise, group and prioritise the findings, for instance by running a thematic analysis.

Tips

Use interview tips and tricks to get the most out of your user interviews.

Learn more

User interviews - Nielsen Norman Group (article)
The three types of user interviews - Nielsen Norman Group (video)
Interview tips and tricks - Amanda Lundius & Victoria Bondarchuk, Visma (slide deck)

This is some text inside of a div block.

What’s a Rich Text element?

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.

No items found.

Templates

Ultimately, the choice of design tool depends on the specific needs of the designer and the project at hand. Each tool has its strengths and weaknesses, and designers must consider factors such as cost, ease of use, and collaboration features when selecting the best tool for their needs.

Design Sprint 2.0 board

Follow this day-by-day exercise schedule for a meaningful and efficient Design Sprint.

Design Sprint Plan

Usability test script

Score card

Design Sprint 2.0 board

Usability testing tips and tricks

Video intro

Tool recommendations

Below you will find some tool recommendations, but please note that you are free to choose whatever tool you prefer. For some tools we have group wide licenses, in which case access can be requested via licenses@visma.com. Remember that you always need cost approval from your immediate manager.