April 14, 2016

—

6 min

Using paper prototypes in UX

In UX research we are told again and again that to ensure truly user-centered design, it’s important to test ideas with real users as early as possible. There are many benefits that come from introducing the voice of the people you are designing for in the early stages of the design process. The more feedback you have to work with, the more you can inform your design to align with real needs and expectations. In turn, this leads to better experiences that are more likely to succeed in the real world.It is not surprising then that paper prototypes have become a popular tool used among researchers. They allow ideas to be tested as they emerge, and can inform initial designs before putting in the hard yards of building the real thing. It would seem that they’re almost a no-brainer for researchers, but just like anything out there, along with all the praise, they have also received a fair share of criticism, so let’s explore paper prototypes a little further.

‍

What’s a paper prototype anyway? 🧐📖

‍

Paper prototyping is a simple usability testing technique designed to test interfaces quickly and cheaply. A paper prototype is nothing more than a visual representation of what an interface could look like on a piece of paper (or even a whiteboard or chalkboard). Unlike high-fidelity prototypes that allow for digital interactions to take place, paper prototypes are considered to be low-fidelity, in that they don’t allow direct user interaction. They can also range in sophistication, from a simple sketch using a pen and paper to simulate an interface, through to using designing or publishing software to create a more polished experience with additional visual elements.

‍

Screen Shot 2016-04-15 at 9.26.30 AM — Different ways of designing paper prototypes, using OptimalSort as an example

‍

Showing a research participant a paper prototype is far from the real deal, but it can provide useful insights into how users may expect to interact with specific features and what makes sense to them from a basic, user-centered perspective. There are some mixed attitudes towards paper prototypes among the UX community, so before we make any distinct judgements, let's weigh up their pros and cons.

‍

Advantages 🏆

‍

They’re cheap and fastPen and paper, a basic word document, Photoshop. With a paper prototype, you can take an idea and transform it into a low-fidelity (but workable) testing solution very quickly, without having to write code or use sophisticated tools. This is especially beneficial to researchers who work with tight budgets, and don’t have the time or resources to design an elaborate user testing plan.
Anyone can do itPaper prototypes allow you to test designs without having to involve multiple roles in building them. Developers can take a back seat as you test initial ideas, before any code work begins.
They encourage creativityFrom both the product teams participating in their design, but also from the users. They require the user to employ their imagination, and give them the opportunity express their thoughts and ideas on what improvements can be made. Because they look unfinished, they naturally invite constructive criticism and feedback.
They help minimize your chances of failurePaper prototypes and user-centered design go hand in hand. Introducing real people into your design as early as possible can help verify whether you are on the right track, and generate feedback that may give you a good idea of whether your idea is likely to succeed or not.

‍

Disadvantages 😬

‍

They’re not as polished as interactive prototypesIf executed poorly, paper prototypes can appear unprofessional and haphazard. They lack the richness of an interactive experience, and if our users are not well informed when coming in for a testing session, they may be surprised to be testing digital experiences on pieces of paper.
The interaction is limitedDigital experiences can contain animations and interactions that can’t be replicated on paper. It can be difficult for a user to fully understand an interface when these elements are absent, and of course, the closer the interaction mimics the final product, the more reliable our findings will be.
They require facilitationWith an interactive prototype you can assign your user tasks to complete and observe how they interact with the interface. Paper prototypes, however, require continuous guidance from a moderator in communicating next steps and ensuring participants understand the task at hand.
Their results have to be interpreted carefullyPaper prototypes can’t emulate the final experience entirely. It is important to interpret their findings while keeping their limitations in mind. Although they can help minimize your chances of failure, they can’t guarantee that your final product will be a success. There are factors that determine success that cannot be captured on a piece of paper, and positive feedback at the prototyping stage does not necessarily equate to a well-received product further down the track.

‍

Improving the interface of card sorting, one prototype at a time 💡

‍

We recently embarked on a research project looking at the user interface of our card-sorting tool, OptimalSort. Our research has two main objectives — first of all to benchmark the current experience on laptops and tablets and identify ways in which we can improve the current interface. The second objective is to look at how we can improve the experience of card sorting on a mobile phone.

‍

Rather than replicating the desktop experience on a smaller screen, we want to create an intuitive experience for mobiles, ensuring we maintain the quality of data collected across devices.Our current mobile experience is a scaled down version of the desktop and still has room for improvement, but despite that, 9 per cent of our users utilize the app. We decided to start from the ground up and test an entirely new design using paper prototypes. In the spirit of testing early and often, we decided to jump right into testing sessions with real users. In our first testing sprint, we asked participants to take part in two tasks. The first was to perform an open or closed card sort on a laptop or tablet. The second task involved using paper prototypes to see how people would respond to the same experience on a mobile phone.

‍

‍

Context is everything 🎯

‍

What did we find? In the context of our research project, paper prototypes worked remarkably well. We were somewhat apprehensive at first, trying to figure out the exact flow of the experience and whether the people coming into our office would get it. As it turns out, people are clever, and even those with limited experience using a smartphone were able to navigate and identify areas for improvement just as easily as anyone else. Some participants even said they prefered the experience of testing paper prototypes over a laptop. In an effort to make our prototype-based tasks easy to understand and easy to explain to our participants, we reduced the full card sort to a few key interactions, minimizing the number of branches in the UI flow.

‍

This could explain a preference for the mobile task, where we only asked participants to sort through a handful of cards, as opposed to a whole set.The main thing we found was that no matter how well you plan your test, paper prototypes require you to be flexible in adapting the flow of your session to however your user responds. We accepted that deviating from our original plan was something we had to embrace, and in the end these additional conversations with our participants helped us generate insights above and beyond the basics we aimed to address. We now have a whole range of feedback that we can utilize in making more sophisticated, interactive prototypes.

‍

Whether our success with using paper prototypes was determined by the specific setup of our testing sessions, or simply by their pure usefulness as a research technique is hard to tell. By first performing a card sorting task on a laptop or tablet, our participants approached the paper prototype with an understanding of what exactly a card sort required. Therefore there is no guarantee that we would have achieved the same level of success in testing paper prototypes on their own. What this does demonstrate, however, is that paper prototyping is heavily dependent on the context of your assessment.

‍

Final thoughts 💬

‍

Paper prototypes are not guaranteed to work for everybody. If you’re designing an entirely new experience and trying to describe something complex in an abstracted form on paper, people may struggle to comprehend your idea. Even a careful explanation doesn’t guarantee that it will be fully understood by the user. Should this stop you from testing out the usefulness of paper prototypes in the context of your project? Absolutely not.

‍

In a perfect world we’d test high fidelity interactive prototypes that resemble the real deal as closely as possible, every step of the way. However, if we look at testing from a practical perspective, before we can fully test sophisticated designs, paper prototypes provide a great solution for generating initial feedback.In his article criticizing the use of paper prototypes, Jake Knapp makes the point that when we show customers a paper prototype we’re inviting feedback, not reactions. What we found in our research however, was quite the opposite.

‍

In our sessions, participants voiced their expectations and understanding of what actions were possible at each stage, without us having to probe specifically for feedback. Sure we also received general comments on icon or colour preferences, but for the most part our users gave us insights into what they felt throughout the experience, in addition to what they thought.

‍

What is user research? 👨🏻💻

‍

User experience (UX) research, or user research as it’s commonly referred to, is an important part of the product development process. Primarily, UX research involves using different research methods to gather qualitative and quantitative data and insights about how your users interact with your product. It is an essential part of developing, building, and launching a product that truly meets the needs, desires, and requirements of your users.

‍

At its simplest, user research is talking to your users and understanding what they want and why. And using this to deliver what they need.

‍

How does user research fit into the product development process? 🧩🧩

‍

User research is an essential part of the product development process. By asking questions of your users about how your product works and what place it fills in the market, you can create a product that delivers what the market needs to those who need it.

‍

Without user research, you could literally be firing arrows in the dark, or at the very best, working from a very internal organizational view based on assuming that what you believe users need is what they want. With user research, you can collect qualitative and quantitative data that clearly tells you where and what users would like to see and how they would use it.

‍

Investing in user research right at the start of the product development process can save the team and the organization heavy investment in time and money. With detailed data responses, your brand-new product can leapfrog many development hurdles, delivering a final product that users love and want to keep using. Firing arrows to hit a bullseye.

‍

What user research methods should we use? 🥺

‍

Qualitative ResearchMethods

Qualitative research is about exploration. It focuses on discovering things we cannot measure with numbers and typically involves getting to know users directly through interviews or observation.

‍

Usability Testing – Observational

One of the best ways to learn about your users and how they interact with your new product is to observe them in their own environment. Watch how they accomplish tasks, the order they do things, what frustrates them, and what makes the task easier and/or more enjoyable for your subject. The data can be collated to inform the usability of your product, improving intuitive design and what resonates with your users.

‍

Competitive Analysis

Reviewing products already on the market can be a great start to the product development process. Why are your competitors’ products successful? And how well do they behave for users? Learn from their successes, and even better, build on where they may not be performing as well and find where your product fills the gap in the market.

‍

Quantitative Research Methods

Quantitative research is about measurement. It focuses on gathering data and then turning this data into usable statistics.

‍

Surveys

Surveys are a popular user research method for gathering information from a wide range of people. In most cases, a survey will feature a set of questions designed to assess someone’s thoughts on a particular aspect of your new product. They’re useful for getting feedback or understanding attitudes, and you can use the learnings from your survey of a subset of users to draw conclusions about a larger population of users.

‍

Wrap Up 🌯

‍

Gathering information on your users during the product development process and before you invest time and money can be hugely beneficial to the entire process. Collating robust data and insights to guide the new product development and respond directly to user needs, and filling that all-important niche. Undertaking user experience research shouldn’t stop at product development but throughout each and every step of your product life cycle. If you want to find out more about UX research throughout the life cycle of your product, take a read of our article UX research for each product phase.

Learn more

1 min read

The Power of Prototype Testing Live Training

If you missed our recent live training on Prototype Testing, don’t worry—we’ve got everything you need right here! You can catch up at your convenience, so grab a cup of tea, put your feet up, and enjoy the show.
‍

In the session, we explored the powerful new features of our Prototype Testing tool, offering a step-by-step guide to setting up, running, and analyzing your tests like a seasoned pro. This tool is a game-changer for your design workflow, helping you identify usability issues and gather real user feedback before committing significant resources to development.

Here’s a quick recap of the highlights:

‍

1. Creating a prototype test from scratch using images

‍

We walked through how to create a prototype test from scratch using static images. This method is perfect for early-stage design concepts, where you want to quickly test user flows without a fully interactive prototype.

‍

2. Preparing your Figma prototype for testing

‍

Figma users, we’ve got you covered! We discussed how to prepare your Figma prototype for the smoothest possible testing experience. From setting up interactions to ensuring proper navigation, these tips ensure participants have an intuitive experience during the test. For more detailed instructions, check out our help article

‍

3. Seamless Figma prototype imports

‍

One of the standout features of the tool is its seamless integration with Figma. We showed how easy it is to import your designs directly from Figma into Optimal, streamlining the setup process. You can bring your working files straight in, and resync when you need to with one click of a button.

‍

4. Understanding usability metrics and analyzing results

‍

We explored how to analyze the usability metrics, and walked through what the results can indicate on click maps and paths. These visual tools allow you to see exactly how participants navigate your design, making it easier to spot pain points, dead ends, or areas of friction. By understanding user behavior, you can rapidly iterate and refine your prototypes for optimal user experience.

‍

Learn more

1 min read

Efficient Research: Maximizing the ROI of Understanding Your Customers

Introduction

‍

User research is invaluable, but in fast-paced environments, researchers often struggle with tight deadlines, limited resources, and the need to prove their impact. In our recent UX Insider webinar, Weidan Li, Senior UX Researcher at Seek, shared insights on Efficient Research—an approach that optimizes Speed, Quality, and Impact to maximize the return on investment (ROI) of understanding customers.

‍

At the heart of this approach is the Efficient Research Framework, which balances these three critical factors:

Speed – Conducting research quickly without sacrificing key insights.
Quality – Ensuring rigor and reliability in findings.
Impact – Making sure research leads to meaningful business and product changes.

‍

Within this framework, Weidan outlined nine tactics that help UX researchers work more effectively. Let’s dive in.

‍

‍

1. Time Allocation: Invest in What Matters Most

‍

Not all research requires the same level of depth. Efficient researchers prioritize their time by categorizing projects based on urgency and impact:

High-stakes decisions (e.g., launching a new product) require deep research.
Routine optimizations (e.g., tweaking UI elements) can rely on quick testing methods.
Low-impact changes may not need research at all.

‍

By allocating time wisely, researchers can avoid spending weeks on minor issues while ensuring critical decisions are well-informed.

‍

2. Assistance of AI: Let Technology Handle the Heavy Lifting

‍

AI is transforming UX research, enabling faster and more scalable insights. Weidan suggests using AI to:

Automate data analysis – AI can quickly analyze survey responses, transcripts, and usability test results.
Generate research summaries – Tools like ChatGPT can help synthesize findings into digestible insights.
Speed up recruitment – AI-powered platforms can help find and screen participants efficiently.

‍

While AI can’t replace human judgment, it can free up researchers to focus on higher-value tasks like interpreting results and influencing strategy.

‍

3. Collaboration: Make Research a Team Sport

‍

Research has a greater impact when it’s embedded into the product development process. Weidan emphasizes:

Co-creating research plans with designers, PMs, and engineers to align on priorities.
Involving stakeholders in synthesis sessions so insights don’t sit in a report.
Encouraging non-researchers to run lightweight studies, such as A/B tests or quick usability checks.

‍

When research is shared and collaborative, it leads to faster adoption of insights and stronger decision-making.

‍

4. Prioritization: Focus on the Right Questions

‍

With limited resources, researchers must choose their battles wisely. Weidan recommends using a prioritization framework to assess:

Business impact – Will this research influence a high-stakes decision?
User impact – Does it address a major pain point?
Feasibility – Can we conduct this research quickly and effectively?

‍

By filtering out low-priority projects, researchers can avoid research for research’s sake and focus on what truly drives change.

‍

5. Depth of Understanding: Go Beyond Surface-Level Insights

‍

Speed is important, but efficient research isn’t about cutting corners. Weidan stresses that even quick studies should provide a deep understanding of users by:

Asking why, not just what – Observing behavior is useful, but uncovering motivations is key.
Using triangulation – Combining methods (e.g., usability tests + surveys) to validate findings.
Revisiting past research – Leveraging existing insights instead of starting from scratch.

‍

Balancing speed with depth ensures research is not just fast, but meaningful.

‍

6. Anticipation: Stay Ahead of Research Needs

‍

Proactive researchers don’t wait for stakeholders to request studies—they anticipate needs and set up research ahead of time. This means:

Building a research roadmap that aligns with upcoming product decisions.
Running continuous discovery research so teams have a backlog of insights to pull from.
Creating self-serve research repositories where teams can find relevant past studies.

‍

By anticipating research needs, UX teams can reduce last-minute requests and deliver insights exactly when they’re needed.

‍

7. Justification of Methodology: Explain Why Your Approach Works

‍

Stakeholders may question research methods, especially when they seem time-consuming or expensive. Weidan highlights the importance of educating teams on why specific methods are used:

Clearly explain why qualitative research is needed when stakeholders push for just numbers.
Show real-world examples of how past research has led to business success.
Provide a trade-off analysis (e.g., “This method is faster but provides less depth”) to help teams make informed choices.

‍

A well-justified approach ensures research is respected and acted upon.

‍

8. Individual Engagement: Tailor Research Communication to Your Audience

‍

Not all stakeholders consume research the same way. Weidan recommends adapting insights to fit different audiences:

Executives – Focus on high-level impact and key takeaways.
Product teams – Provide actionable recommendations tied to specific features.
Designers & Engineers – Share usability findings with video clips or screenshots.

‍

By delivering insights in the right format, researchers increase the likelihood of stakeholder buy-in and action.

‍

9. Business Actions: Ensure Research Leads to Real Change

‍

The ultimate goal of research is not just understanding users—but driving business decisions. To ensure research leads to action:

Follow up on implementation – Track whether teams apply the insights.
Tie findings to key metrics – Show how research affects conversion rates, retention, or engagement.
Advocate for iterative research – Encourage teams to re-test and refine based on new data.

‍

Research is most valuable when it translates into real business outcomes.

‍

Final Thoughts: Research That Moves the Needle

‍

Efficient research is not just about doing more, faster—it’s about balancing speed, quality, and impact to maximize its influence. Weidan’s nine tactics help UX researchers work smarter by:

‍
✔️ Prioritizing high-impact work
✔️ Leveraging AI and collaboration
✔️ Communicating research in a way that drives action

‍

By adopting these strategies, UX teams can ensure their research is not just insightful, but transformational.

‍

Watch the full webinar here

‍

View all blog articles

Prototype Testing

Seeing is believing

Explore our tools and see how Optimal makes gathering insights simple, powerful, and impactful.

Start your free trial

Get in touch