Lightweight and cost-effective ways to do user research

1. Talk to a few users — not all of them

A common misconception is that research must be statistically significant to be valuable. In our experience, 3–5 conversations are often enough to:

• identify recurring patterns
• uncover obvious misunderstandings
• validate or challenge key assumptions

The goal is not to answer every question, but to avoid the most costly mistakes.

Short, informal interviews of 30–45 minutes can often provide more insight than expected — especially early in a project, when direction is still flexible.

2. Research workshops with stakeholders

In many projects, a great deal of valuable knowledge already exists within the organization:

• product owners
• sales teams
• support teams
• technical experts

At Intunio, we frequently use structured workshops to bring this knowledge together. This is an efficient way to:

• map assumptions
• surface internal contradictions
• separate facts from guesses

Examples of simple exercises include:

• “What do we know for certain about the user?”
• “What do we believe, but don’t have evidence for?”
• “Where are we most uncertain?”

The result is often a clear foundation for design — and a shared understanding within the team, even before engaging external users.

3. Guerrilla testing and rapid prototype validation

You don’t always need fully defined flows or polished prototypes to test ideas.

Lightweight methods can include:

• clickable wireframes
• paper sketches
• static screens with assumed flows

Show these to users and ask questions such as:

• What do you think this does?
• What would you expect to happen here?
• What feels unclear?

These sessions can often be done:

• remotely
• in 20–30 minutes
• with very little preparation

In many projects, this is enough to identify the biggest risks early on.

4. Analyze existing data instead of creating new data

In many organizations, valuable information already exists, such as:

• support tickets
• feedback from sales
• customer emails
• usage analytics
• previous research

Systematically reviewing this material can provide clear signals about:

• where users get stuck
• what causes frustration
• which features are actually used

This is often an underestimated form of research — despite the fact that the data is already available and the cost is low.

5. Test during the design phase instead of before

Not all research needs to happen before design begins.

In some projects, it is more effective to:

• create an initial solution quickly
• use it as a discussion artifact
• test and refine it along the way

Design then becomes a tool for research, rather than the outcome of it.

This approach works particularly well for:

• consumer-facing products
• iterative development processes
• MVP phases

Here, learning becomes a natural part of the design process.

6. Prioritize research where uncertainty is highest

Not all parts of a project carry the same level of risk.

A pragmatic approach we often use is:

• invest in research where decisions are hard to reverse
• focus research where the consequences of wrong decisions are significant
• skip research where risk is low and feedback can be gathered quickly

This ensures the budget is used where it delivers the greatest value.

Research is about direction — not perfection

The goal of user research is rarely to find all the answers.

It is about reducing uncertainty, creating alignment, and making better decisions.

In many projects, it goes a long way to have:

• a handful of conversations
• the right questions
• a willingness to adjust course

What matters most is not how much research is done — but that it is done with the right intent, at the right time, and at the right level of depth.