- Conduct user interviews
- Process the interviews and identify the trends
- Send out survey to appropriate sample (use sample size calculator) of target user to quantify the findings
- Identify the user problems
- Rank the problems in terms impact towards the team's business objectives
- Then you can move on to solutions (brainstorms, sketching, wires, prototypes, testing, etc.)
Scheduling User Interviews
- Compose your survey (Typeform, SurveyMonkey)
- Pull your sample of survey participants
- Set up interview time blocks (Tools like Pow Wow help make scheduling much easier)
- Write a personalized invitation
- Include an incentive if possible (Gift Card) to increase potential responses
- Send the invitation from the appropriate source & tool
- Source: Using your real first name and work email makes it feel more personal and is usually more effective
- Tool: The tools you used to create the survey most likely have native tools to bulk send your email, but you may have an internal tool that can send the emails which may be more effective for you.
- After your scheduling tool sends you the confirmation of a confirmed appointment, you may need to add some extra details to the automatically generated meeting in your calendar
- Invite the person via the email added in the description of the meeting
- Add anyone else who will be in the meeting (observers, scribes)
- Book the meeting room in your office
- Add the hangouts link to the meeting
- Save changes and send out invites regarding the modifications to the meeting
- On the day of the interviews, you may want to send an email to each participant to confirm they are still on for the interview
- Sometimes they need the reminder
- They may tell you they can't make it, saving you time
- Increases turnout
Documenting User Interviews
- Use a spreadsheet, not a word doc to capture interview answers for all participants
- Capturing the answers in a spreadsheets helps you to quickly compare answers to the same question instantly, compared to capturing your answers in a doc where you'd have to go back and collect and compare each answer, creating unnecessary busy-work
- Have one person be the Interviewer, another the Scribe who will take notes and capture observations
Problem Validation Research
Before brainstorming solutions, it might be worth it to invest a bit of time to really make sure that the problem you have identified really is a problem.
Some questions to ask:
- How do we know this is a problem?
- Data patterns
- Observation (Moderated or unmoderated user testing)
- User feedback
- Is this a big enough problem for us to invest time into solving?
- How many users does it affect?
- In what severity does it affect them?