More often than not, it feels likeUXresearch is under-appreciated and under-resourced intechcompanies.

Yes, there are situations in which the traditional UX research process just wont cut it.

In these cases, youre still better off doing research but in a scrappy way.

Scrappy UX research is the answer to your team’s time crunch issues

You should find ways to tweak and play with the UX process to fit your project needs.

When is the right time to get scrappy?

Engaging in scrappy UX research sounds simple, but its utility must be well-thought-out like any method.

Article image

Its essential to know when scrappy techniques are helpful and when theyre doing a disservice to your team.

It’s free, every week, in your inbox.

Overall, the purpose of UX research is to support decision-making throughout the product development cycle.

The 4 stages of user experience research (UXR)

1.

UXR planning

The planning stage is perhaps the most essential stage in the UXR process.

The main way to drive scrappiness in research planning is to push for radical simplicity.

A typical research plan may have a series of different learning objectives and questions that build on each other.

In traditional research, there are four or five different people you want to interview within a customer segment.

Now, traditionally, you talk to two of each group to get a representative mix of impressions.

But suppose we are working under strict consideration of budget and time.

In that case, its okay to have three respondents from one persona (e.g.

hardcore users) and one from the other (e.g.

socializers), as long as having a representative sample is not that important to you.

Thats why it’s crucial that you maximize the time you have for each candidate usually around 30 minutes.

This can be a very effective way to gauge relative interest in different potential directions quickly.

One can fully concentrate on taking notes, while the second person can ask questions and actively listen.

The most important thing to note here is to be careful in drawing premature conclusions.

This articlewas originally published by Aayush Gupta inBuilt In.

you might read ithere.

Also tagged with