Research You Can Actually Fit In
The ideal of a full discovery phase and extensive user research is rarely matched by the reality of project deadlines and budgets. Rather than adding to the guilt, it is worth accepting that a small amount of targeted research is often better than none at all. The key is to focus on answering specific questions as they arise, instead of trying to build a complete picture of the user upfront.
This approach does not add time to a project; it can save it. Think about the hours lost in stakeholder meetings arguing over the correct label, or the revision cycles caused by a client who cannot decide between two design options. A quick survey or a five-second test can replace that debate with data. Instead of asking for extra time for research, we can simply substitute it for meetings that were going to happen anyway.
Skip the Grand Discovery
Many projects skip a discovery phase out of necessity. That is not necessarily a failure. General audience research performed upfront is often wasteful, as you frequently only learn which questions are important after the work has begun. A full customer journey mapping exercise, done just because you read you should, is not a good use of scarce time.
A better starting point is to collect what the organization already knows. Most companies have relevant resources: personas from marketing, past survey data, or analytics reports. Collating this existing information is quick and often reveals 80% of what you need. Only if there are significant, obvious gaps in this knowledge is it worth doing some upfront research. More often, you will have enough to begin and can conduct focused research when specific issues surface.
Answer One Question at a Time
Research is most effective when it addresses a single, clearly defined question. Trying to learn everything about your user in one exercise is a guarantee of wasted time. Adding extra survey questions just because the answers would be interesting slows down the whole process.
Your focus should be on answering specific questions, not improving your general understanding of the user.
For example, if you want to know why people are abandoning their carts, a one-question exit survey on the checkout page is a direct solution. If stakeholders are worried that a critical call to action will be missed, a quick five-second test can dispel or confirm that fear immediately. By keeping each research effort small and focused, it becomes much easier to slot into the existing project workflow.
Keep Your Methods Lightweight
Lean research requires a move away from time-consuming facilitated methods like interviews and moderated usability tests. The focus should be on techniques that take minutes to set up and deliver results you can interpret at a glance. This points to surveys and unmoderated testing tools.
Quick and Dirty Surveys
Short, focused surveys are a powerful tool for settling disagreements. They are effective for testing two competing label options against each other, discovering what tasks users want to complete on a site, or finding out why visitors are not signing up for a free trial.
Speed of deployment is a major advantage. If you have a budget, you can use a panel service like Pollfish to target a specific demographic for a few dollars per submission, often getting results within a day. If money is tight, you can distribute the survey link via social media, a mailing list, or your website to get outside perspectives.
Unfacilitated Tests
Most design debates among stakeholders revolve around four questions: Did users see it? Did they understand it? Can they use it? Will they like it? There are specific tests for each.
Did users see it? Run a 5-Second Test. Show a user your design for five seconds and ask them what they saw. Tools like Usability Hub and Maze provide a URL that can be sent to participants, making it as simple as distributing a survey. If they recall the key element, you have your answer.
Did users understand it? A variation of the 5-Second Test helps here. After showing the design, ask users to describe it in their own words to see if their interpretation matches your intent.
Can people use it? If you have a working prototype, unmoderated usability testing is an option. With a tool like Maze, you define the task, give it the direct route to completion, and share the participant link. It aggregates data on completion time and missteps. If you only have a mockup, use a first-click test. You show the design to users and ask where they would click to complete a given task. Data shows that if the first click is right, users have an 87% chance of completing the action correctly, versus 46% if wrong.
Will people like it? This is often the most contentious question. A preference test can help, but a semantic differential survey is more useful. Agree with stakeholders on the associations the design should evoke—for example, "professional" or "friendly"—and ask users to rate the design against those words. If it scores well on the agreed terms, the internal debate is settled.
A Pragmatic Starting Point
Admittedly, this approach is not perfect. It lacks the rigor of a large-scale, peer-reviewed study and can potentially lead to false conclusions. However, it is far superior to the alternative: making design decisions based on internal opinions and speculation. Even a small amount of this lean research can demonstrate its value to stakeholders, making them more receptive to investing in more substantial research in the future. While they may rightly point out issues with your sample size or participant selection, that gives you the perfect opening to request more time and budget for a more thorough effort.
