Lean Research

Making traditional research methods agile

Traditional research methods can sometimes feel slow and rigid. However, adapting them to an agile framework enables us to unlock valuable insights quickly and iteratively. Here's a guide to making user interviews, in-app surveys, and usability studies more agile while maintaining effectiveness.

User Interviews

Traditionally, user interviews are considered time-consuming and are often used in a project's early stages to gather deep, qualitative insights. However, they can be more agile if broken down into smaller, more focused sessions conducted throughout the design and development phases.

Agile Adaptation:

Keep them short and focused.

Instead of extended, in-depth interviews, break them into smaller, targeted micro-studies sessions focusing on specific user experience areas.

Get comfortable with gently guiding users back to the task at hand.

 If a user starts to wander off into other subjects, try saying, "These are amazing insights on (x) subject. Do you mind if I follow up with you on that?" Then, ask them to return to the task at hand.

No fishing expeditions! 

Never ask a user a question in an interview that you are unsure as to how you will use the answer. There is a time and a place for blue-sky research; we're talking about making these methods more agile. If you can't verbalize using the data, leave the question off.

Use AI tools

Synthesize, group, and analyze user interview scripts and videos much more quickly, but include human eyes in the output!

Add qualitative questions for features that are two-three quarters away.

Select 1-2 more significant open questions your team has about any initiative and ask the user throughout several studies. When the development starts, you should have a "library" of information on that topic.

Surveys

Quantitative or qualitative surveys can provide attitudinal insights from a broad user base. However, due to the time it takes to distribute, gather, and analyze results, they often suffer from delayed feedback loops.

Agile Adaptation:

Use closed-ended multiple-choice

For example, when investigating why users aren't purchasing, you'll likely add a multiple-choice question. I suggest you avoid including an "other" option on the first survey question. Instead, prioritize your roadmap by prioritizing choices tied to actionable feature changes. After users select from your initial list, follow up with, "Are there any reasons we missed?"

Quick analysis

AI tools for real-time data analysis can help provide actionable insights within each sprint.

Usability Testing

Usability testing is a powerful way to observe users performing tasks in a controlled setting. It typically focuses on uncovering friction points.

Agile Adaptation:

Write precise tasks with a singular purpose.

For any usability study, ensure you ask the user one to two main questions.s

Send and play remote testing (on a budget).

Write a script detailing 1-3 specific tasks. Ask users to perform particular tasks, talk aloud, record their thoughts as they work through them, and send you the results.

Iterate within sprints

After each usability test, quickly implement fixes and retest within the same sprint. Remember, only 5-10 users will tell you if a UI is easy to use.

Use Diary Studies

Diary studies can provide rich, longitudinal insights but don't have to take months.

Agile Adaptation:

Set clear, short-term goals for what you want to learn.

Ask users to record their interactions with your product over a week or two, focusing on specific features 6-8 sprints ahead of your team. This will give you the correct information when design/development starts.

Provide easy tools (like a simple mobile app or shared document) for users to log their experiences quickly.