{"id":3557,"date":"2022-07-01T21:44:34","date_gmt":"2022-07-01T21:44:34","guid":{"rendered":"https:\/\/blog.qualaroo.com\/?p=3557"},"modified":"2026-07-18T16:09:37","modified_gmt":"2026-07-18T16:09:37","slug":"step-by-step-testing-your-prototype","status":"publish","type":"post","link":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/","title":{"rendered":"Prototype Testing: A Step-by-Step Guide for Teams"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Your prototype is ready. The design decisions have been made, the flows are linked, and the screens are shareable.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What most product teams do next is run a session, watch a few recordings, write up a summary, and move into development.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What they should do is instrument the prototype for in-context feedback, run structured tasks, collect responses when they are most accurate, and use severity, not volume, to decide what to fix.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This guide covers that approach: how to actually test a prototype, screen by screen, question by question, round by round, so the feedback you collect is specific enough to change what gets built.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_Is_Prototype_Testing_and_Why_Does_It_Only_Work_When_You_Treat_It_as_a_Decision_Tool\"><\/span><strong>What Is Prototype Testing, and Why Does It Only Work When You Treat It as a Decision Tool?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<div style=\"background: #e8f4fd; border-left: 4px solid #0073aa; padding: 18px 20px; margin-bottom: 28px; border-radius: 0 4px 4px 0; font-size: 16px; line-height: 1.75;\">\n<p style=\"margin: 0; color: #333333;\">Prototype testing is the process of presenting an early version of a product to real users to identify usability issues, navigation gaps, and design mismatches before full development begins. It is iterative by design: each round surfaces problems, the team fixes the critical ones, and the next round confirms the fix worked and did not introduce new issues.          \n<\/p>\n<\/div>\n\n\n\n<p class=\"wp-block-paragraph\">How you frame prototype testing shapes what your team does with it.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you treat it as a validation ritual before handoff, you will run one round, collect feedback, and ship anyway.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you treat it as a decision-making tool, you will run multiple rounds, change real things between rounds, and arrive at development with design choices grounded in observed user behavior rather than internal consensus.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The distinction between prototype testing and QA is also worth making explicit.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">QA checks whether the product functions as built. Prototype testing checks whether the right product was built in the first place. Both matter, and neither replaces the other.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_Do_You_Run_a_Prototype_Test_That_Produces_Decisions_Not_Just_Observations\"><\/span><strong>How Do You Run a Prototype Test That Produces Decisions, Not Just Observations?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Here is the end-to-end workflow focused on what happens after the prototype exists: how to set up feedback collection, structure tasks, ask the right questions at the right moment, and act on what you learn.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 1: Define What You Are Testing and Why<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The quality of your test is decided before a single user sits down, when you document the specific assumptions your current design is built on.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Not features. Assumptions.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8220;We believe users will navigate to the upgrade option via the dashboard sidebar.&#8221;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8220;We believe users understand what &#8216;workspace&#8217; means without a tooltip.&#8221;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Each assumption is a testable research question, and each one, if wrong, would change something significant about the design.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Limit each session to 1 to 5 research questions. Every observation beyond those is context, not primary signal. More than 5, and you will exit the session with findings too diffuse to prioritize.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you are unsure which assumptions carry the most risk, behavioral data from your existing product is the fastest way to narrow the list.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Qualaroo&#8217;s Session Recordings let you watch real user journeys in your live product, identifying where hesitation, rage clicks, and drop-offs already occur, so your prototype test focuses on friction points that are already costing you rather than ones you are only guessing about.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 2: Write Task Scenarios That Reveal Real Behavior<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Task scenarios are where most prototype tests are won or lost before the session begins.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The wording of a task changes the behavior you observe, which changes the findings you produce, which changes what gets fixed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Write tasks around user goals, not product features.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Usability researcher Jared Spool&#8217;s work with Ikea demonstrated this directly: asking users to &#8220;find a bookcase&#8221; sent them straight to the search bar.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Asking users to organize 200 paperback novels in their living room sent them through product categories, revealing how the site&#8217;s architecture matched or mismatched their mental models. The second task produced the insight that drove real design changes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Three rules that change task quality:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong><strong>No product terminology users wouldn&#8217;t already know.<\/strong> <\/strong>If your product calls something a &#8220;workspace,&#8221; don&#8217;t use that word. Observe whether users discover and understand it themselves.<\/li><li><strong><strong>No instructions on how to complete the task.<\/strong> <\/strong>Observe what users do without guidance.<\/li><li><strong><strong>Write for a realistic situation, not a feature demonstration.<\/strong> <\/strong>&#8220;Book a flight to Amsterdam&#8221; is a demonstration. &#8220;You want to visit a friend in Amsterdam next September with two weeks off and a tight budget. Find the best option.&#8221; The second produces richer, more differentiated behavior.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Before the real sessions, pilot your task scenarios with one colleague. If they immediately ask for clarification, the wording needs revision. This 15-minute step prevents an entire round of corrupted data.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 3: Recruit Participants Who Will Surface Real Problems<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Five participants per round is the established starting point, grounded in <a href=\"https:\/\/www.nngroup.com\/articles\/5-test-users-qual-quant\/\" target=\"_blank\" aria-label=\"undefined (opens in a new tab)\" rel=\"noreferrer noopener\">Nielsen and Landauer&#8217;s research<\/a> showing that 5 users surface approximately 85% of usability problems per iteration. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Three rounds of 5 consistently outperform one round of 15: the first round surfaces structural problems, the second confirms fixes held, and the third cleans up what the first two missed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That said, 5 is a starting point, not a universal rule. Adjust based on:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>User Segments: If your product serves meaningfully different user types (admins vs. end users, novices vs. experts), recruit at least 3 to 5 per segment per round.<\/li><li>Task Complexity: Longer, multi-step flows have more failure points and benefit from larger samples.<\/li><li>Risk Level: High-stakes decisions (a complete navigation redesign, a new checkout flow) warrant more participants before committing to development.<\/li><li>Test Type: Exploratory rounds can run lean. Confirmatory rounds validating a specific fix need enough participants to distinguish the signal from the noise.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A few recruiting principles that change result quality:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Recruit slightly broader than your exact persona.<\/strong> Steve Krug&#8217;s advice in <a href=\"https:\/\/sensible.com\/dont-make-me-think\/\" target=\"_blank\" aria-label=\"undefined (opens in a new tab)\" rel=\"noreferrer noopener\">&#8216;Don&#8217;t Make Me Think&#8217;<\/a> holds: almost any user will reveal navigational and structural failures.<\/li><li><strong>Screen out anyone who has seen the prototype.<\/strong> Familiarity masks friction and makes the session nearly useless for discovering new problems.<\/li><li><strong>Segment by dimensions that matter:<\/strong> technical proficiency, domain familiarity, geography, or use case.<\/li><li><strong>Get explicit consent before recording.<\/strong> In the EU and a growing number of US states, data protection requirements apply to user research, not just product analytics.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Get explicit consent before recording any session or collecting personal data. In the EU and in a growing number of US states, data protection requirements apply to user research, not just product analytics.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 4: Instrument the Prototype With In-Context Survey Questions<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The primary signal in prototype testing is observed behavior: what users do, where they hesitate, what paths they take, and where they fail. Moderator notes, session recordings, and task completion data are the foundation of your findings.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In-context survey questions are a useful supplement, not a replacement for observation. They capture reactions at the exact screen where something happened, which is more accurate than a post-session debrief relying on memory. But a survey answer without behavioral context is still just stated preference. Use both together.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When your prototype is hosted on a live URL via Figma, InVision, Marvel, Adobe XD, or Axure, you can attach an in-app survey to that URL and configure it to appear at a time-on-page threshold, an exit signal, or a scroll depth marker.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What this produces is feedback tied to the exact screen and moment where the experience happened, not what the participant remembers 20 minutes after the session ended.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">According to GraphicSprings&#8217; case study with Qualaroo, <a href=\"https:\/\/qualaroo.com\/blog\/measure-user-experience\/\">in-context UX feedback<\/a> contributed to a 41% increase in revenue as part of a broader UX optimization process.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"367\" src=\"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2022\/03\/qualaroo.com_case-studies_graphicsprings_PP-1024x367.png\" alt=\"Graphicsprings Case Study\" class=\"wp-image-23767\"\/><\/figure>\n\n\n\n<div class=\"banner-btn newuishow\" style=\"text-align: center;\"> \n  <a class=\"round_btn try-btn\" href=\"https:\/\/qualaroo.com\/case-studies\/graphicsprings\/\" target=\"_blank\" rel=\"noopener noreferrer\">View Complete Success Story<\/a>\n<\/div>\n\n\n\n<p class=\"wp-block-paragraph\">We cover the full setup process in the dedicated section below.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 5: Run the Session and Capture Behavioral Signal<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">During moderated sessions, your job is to observe, not to guide.&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Do not explain what the participant should do.&nbsp;<\/li><li>Do not react visibly when something goes wrong.&nbsp;<\/li><li>Do not defend a design decision.&nbsp;<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The moment you intervene, the session stops producing a real behavioral signal.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Three principles that change what you capture:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Ask participants to think aloud.<\/strong> &#8220;Tell me what you&#8217;re thinking as you look for that&#8221; produces more usable data than any post-session debrief.<\/li><li><strong>Note hesitation, not just failure.<\/strong> A participant who eventually finds the right element via an unexpected path is signaling an information architecture problem, even if the task technically succeeded.<\/li><li><strong>Don&#8217;t count a task as complete just because they got there.<\/strong> Note the time taken, the path chosen, and whether they expressed confidence or uncertainty at the end.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Moderated or unmoderated: which produces the outcome you need?<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Method<\/strong><\/td><td><strong>When to Use It<\/strong><\/td><td><strong>What You Gain<\/strong><\/td><td><strong>What You Trade Off<\/strong><\/td><\/tr><tr><td><strong>Moderated<\/strong><\/td><td>Early-stage concepts, complex flows, sessions where follow-up questions would change what you learn<\/td><td>Rich qualitative signal, ability to probe unexpected behavior in real time<\/td><td>More setup time, moderator presence can subtly influence how participants respond<\/td><\/tr><tr><td><strong>Unmoderated<\/strong><\/td><td>Navigation validation, remote participants across time zones, and later-stage tests where structural issues are resolved<\/td><td>Speed, scale, no moderator influence on behavior<\/td><td>No ability to follow up on unexpected paths or ask why a participant made a specific choice<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Use moderation early, when flows are complex, and you need the reasoning behind user behavior, not just the behavior itself.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Switch to unmoderated when you are validating fixes at scale and need a confirmatory signal without the scheduling overhead.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 6: Turn Findings Into Product Decisions That Stick<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is where prototype testing either compounds into value or disappears into a shared folder no one opens.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>1. Triage by Severity, Not Frequency&nbsp;<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A problem one participant encountered that blocked task completion is more urgent than a complaint; five participants mentioned that it is annoying but not a blocker.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Categorize every finding into three buckets: prevents task completion, slows it significantly, or is cosmetic. Fix in that order.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>2. Track Quantitative Metrics Alongside Qualitative Findings<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Observations alone make it hard to compare rounds or demonstrate improvement to stakeholders. Four metrics worth capturing per task per round:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Task Success Rate: <\/strong>The percentage of participants who completed the task without assistance. The clearest indicator of whether a flow works.<br><strong>Time on Task: <\/strong>How long did the completion take? A task everyone completes but takes twice as long as expected signals friction even when the success rate looks healthy.<br><strong>Error Rate: <\/strong>How often participants took a wrong path, clicked the wrong element, or had to backtrack. High error rates on a specific screen point directly at the redesign target.<br><strong>Post-Task Difficulty Rating:<\/strong> A single 1 to 5 scale question immediately after each task (&#8220;How difficult was that?&#8221;) gives you a comparable score across rounds and surfaces perceived friction that behavioral data alone may not capture.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Track these for each task and each round. A task success rate that improves from 40% to 80% between rounds is clearer evidence of a fix working than qualitative notes alone.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>3. Retest After Fixing, Every Time\u00a0<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Fixing one issue often shifts behavior around adjacent elements. A navigation change that resolves the original problem can break the path to something else.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second round catches what the first round missed and confirms the fix held. Without it, you are shipping an assumption, just a more recent one.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>4. Document the Decision, Not Just the Finding<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8220;Users could not find the upgrade button&#8221; is a finding.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8220;We moved the upgrade button to the top navigation because three rounds of prototype testing showed users expected to find account management actions there, not in the sidebar&#8221; is a decision with evidence.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second form prevents the button from being moved back six months later when a stakeholder proposes &#8220;cleaning up&#8221; the navigation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_Set_Up_In-App_Surveys_Inside_Your_Prototype_Using_Qualaroo\"><\/span><strong>How to Set Up In-App Surveys Inside Your Prototype Using Qualaroo<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Qualaroo&#8217;s Nudge for Prototypes lets you collect feedback directly from a prototype without writing a single line of code. It works with Figma, InVision, Marvel, AdobeXD, and Axure. The setup takes a few minutes. Here is exactly how it works.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 1: Create a New Nudge for Prototypes<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In your Qualaroo dashboard, click &#8220;Create a Nudge.&#8221; Hover over &#8220;Nudge for Prototype&#8221; and select &#8220;New From Scratch.&#8221;&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"270\" src=\"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2022\/07\/Screenshot-2026-05-12-103852-1024x270.png\" alt=\"Selecting Nudge for Prototype from Channel Types\" class=\"wp-image-24799\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This opens the prototype-specific setup flow, which is separate from a standard website Nudge\u2122.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 2: Enter Your Prototype URL<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Paste the target URL of your prototype and click &#8220;Next.&#8221;&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"1018\" src=\"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2022\/07\/nudge-for-prototype-url-1024x1018.png\" alt=\"Enter Your Prototype URL\" class=\"wp-image-24800\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Qualaroo detects which prototyping tool you are using based on the URL and surfaces any tool-specific instructions you need to complete before the Nudge\u2122 will fire correctly.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Make sure the URL is a public or &#8220;shared&#8221; link.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Private or password-protected links will return an error at this stage. If you are using a tool not on the supported list, select &#8220;Nudge for Prototypes with a custom URL&#8221; instead.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 3: Test the URL<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Once Qualaroo confirms the URL is compatible, click &#8220;Test Now.&#8221;&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"861\" src=\"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2022\/07\/nudge-for-prototype-test-now-1024x861.png\" alt=\"Test the URL. Once Qualaroo confirms the URL is compatible, click &quot;Test Now.&quot; \" class=\"wp-image-24801\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">A new window opens showing your prototype with confirmation that Qualaroo has been implemented on it.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This lets you verify the Nudge\u2122 is firing before you send the link to any participants. When you are satisfied, click &#8220;Create.&#8221;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 4: Build Your Question Sequence<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">With the Nudge\u2122 created, select your questions, answer types, and <a href=\"https:\/\/qualaroo.com\/features\/question-branching\/\">branching logic<\/a> in the Edit tab.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"410\" src=\"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2026\/05\/app.qualaroo.com_surveys_240767_editPP-1024x410.png\" alt=\"Build Your Prototype testing Question Sequence\" class=\"wp-image-24802\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Qualaroo supports multiple-choice, rating-scale, and open-text fields within the same Nudge\u2122.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use branching to route participants to different follow-up questions based on their answers, so participants who found a task easy skip the follow-up that asks what made it hard, and participants who struggled get that depth automatically.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s how you can use branching:<\/p>\n\n\n\n<figure class=\"wp-block-embed-youtube wp-block-embed is-type-video is-provider-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"How to Use Skip Logic &amp; Branching in Surveys (Step-by-Step) | Qualaroo\" width=\"1120\" height=\"630\" src=\"https:\/\/www.youtube.com\/embed\/62hmNWnTGQw?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Keep each screen to 3 to 5 questions. Above that threshold, skip rates increase, and the responses you do get become less reliable.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 5: Set Your Targeting Rules<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Move to the <a href=\"https:\/\/qualaroo.com\/features\/advanced-user-targeting\/\">Targeting tab<\/a> to control when, how often, and for how long the Nudge\u2122 fires.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"963\" height=\"1024\" src=\"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2022\/09\/qualaroo-targeting-963x1024.png\" alt=\"Advanced targeting for popup surveys\" class=\"wp-image-24150\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This tab also shows two URLs: your original prototype URL and the updated distribution URL that has Qualaroo embedded. The distribution URL is what you send to participants, not the original.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use the targeting options here to control session timing, response frequency, and notification preferences.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you are running multiple rounds with different participant segments, configure separate <a href=\"https:\/\/qualaroo.com\/features\/nudge-for-prototypes\/\">Nudges\u2122 for the prototype<\/a> with different targeting rules for each segment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 6: Finalize and Distribute<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Save your targeting settings. Make any final visual adjustments in the Design tab.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then copy the updated URL from the Targeting tab and send it to your test participants.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Every participant who opens that link will see your prototype with the Nudge\u2122 survey embedded and firing at the configured moments.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For open-text responses collected across sessions, <a href=\"https:\/\/qualaroo.com\/features\/watson\/\">Qualaroo&#8217;s AI Sentiment Analysis<\/a> classifies each response by sentiment automatically, so you can identify which screens are generating negative reactions before your debrief without reading every reply individually.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s how sentiment analysis works:<\/p>\n\n\n\n<figure class=\"wp-block-embed-youtube wp-block-embed is-type-video is-provider-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"How to Use AI Sentiment Analysis on Customer Survey Responses\" width=\"1120\" height=\"630\" src=\"https:\/\/www.youtube.com\/embed\/6XtwxzlABys?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Questions_to_Ask_During_Prototype_Testing\"><\/span><strong>Questions to Ask During Prototype Testing<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The questions you embed in the prototype, and when you embed them, determine the quality of the signal you get back.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Vague questions at the wrong moment produce polite, unusable answers. Specific <a href=\"https:\/\/qualaroo.com\/blog\/prototype-testing-questions\/\">prototype testing questions<\/a> triggered at the right screen produce the feedback that drives real design changes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 1: First Impressions, Before Any Interaction<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ask these before the participant has clicked anything. You are testing whether the design communicates its own purpose, not whether users can figure it out with help.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These work as an opening survey Nudge\u2122 triggered the moment the first prototype screen loads, before the participant begins any task:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>&#8220;Who do you think this product is for?&#8221;<\/li><li>&#8220;What do you think you can do here?&#8221;<\/li><li>&#8220;What&#8217;s the first thing you notice?&#8221;<\/li><li>&#8220;Is there anything that feels out of place or doesn&#8217;t make sense?&#8221;<\/li><li>&#8220;Does this remind you of anything you&#8217;ve used before?&#8221;<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s a quick <a href=\"https:\/\/app.qualaroo.com\/surveys\/new?channel=web&amp;survey_id=230971\">first-impression prototype testing survey<\/a> template:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"512\" height=\"439\" src=\"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2022\/07\/output-expected-template-qlr.png\" alt=\"first-impression prototype testing survey template\" class=\"wp-image-24803\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">What you are looking for: whether users can identify the core value proposition, the intended audience, and the primary action within 10 seconds.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If they cannot, that is a positioning and visual hierarchy problem, not a copy problem.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 2: During-Task Prompts<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">These surface the participant&#8217;s internal reasoning while the behavior is still observable. In moderated sessions, ask them verbally when the participant pauses, hesitates, or takes an unexpected path.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In unmoderated sessions, embed these as time-on-page Nudge\u2122 triggers on screens where hesitation is most likely to occur.<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>&#8220;Can you tell me what you&#8217;re thinking right now?&#8221;<\/li><li>&#8220;What did you expect to happen when you clicked that?&#8221;<\/li><li>&#8220;What are you looking for?&#8221;<\/li><li>&#8220;Where would you expect to find that?&#8221;<\/li><li>&#8220;Was there anything missing that you expected to see?&#8221;<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s a <a href=\"https:\/\/app.qualaroo.com\/surveys\/new?channel=web&amp;survey_id=230972\">during-task prompt template<\/a> for you:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"511\" height=\"439\" src=\"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2022\/07\/is-anything-missing-template-qlr.png\" alt=\"during-task prompt template\" class=\"wp-image-24804\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">What you are looking for: the gap between what users expected and what the design delivered. That gap is your redesign brief.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Phase 3: Post-Task Structured Questions<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Trigger these immediately after each task completes.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Configure the Nudge\u2122 to appear as soon as the participant reaches the end state of a task flow, whether that is a confirmation screen, a dead end, or a point where the task was abandoned.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Keep the sequence to 4 to 5 questions per task. Beyond that, fatigue sets in, and response quality drops sharply.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">After Each Task:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>&#8220;How would you rate the difficulty of that task on a scale of 1 to 5?&#8221;<\/li><li>&#8220;What, if anything, confused you during that task?&#8221;<\/li><li>&#8220;What would you change about that experience?&#8221;<\/li><li>&#8220;Did the product guide you to what you needed?&#8221;<\/li><li>&#8220;Is there anything you expected to see that wasn&#8217;t there?&#8221;<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s a prototype testing <a href=\"https:\/\/app.qualaroo.com\/surveys\/new?channel=web&amp;survey_id=230953\">survey template for after-task prompts<\/a>:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"576\" height=\"716\" src=\"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2021\/12\/UES-QLR.png\" alt=\"A Task Completion Template You Can Use:\" class=\"wp-image-24487\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">At the End of the Full Session:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>&#8220;Was there a function you expected that was missing?&#8221;<\/li><li>&#8220;How was the overall experience of moving through this?&#8221;<\/li><li>&#8220;Would you use this? Why or why not?&#8221;<\/li><li>&#8220;What would make you more confident using this?&#8221;<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s a <a href=\"https:\/\/app.qualaroo.com\/surveys\/new?channel=web&amp;survey_id=242503\">prototype testing template<\/a> you can use at the end of a full session:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"571\" height=\"484\" src=\"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2022\/07\/qualaroo.com_templates_capture-screenshot_PP-2-1.png\" alt=\"prototype testing template you can use at the end of a full session\" class=\"wp-image-24805\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Question Writing Rules That Change Response Quality<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Do not ask leading questions. &#8220;Did you find that easy?&#8221; is leading.&nbsp;<\/li><li>&#8220;How would you describe that experience?&#8221; is not.&nbsp;<\/li><li>Do not ask users what they would do hypothetically.&nbsp;<\/li><li>Ask them to do it and observe what happens.&nbsp;<\/li><li>Do not use the product&#8217;s own terminology in task or question wording if users would not already know it. The goal is behavior, not stated preference.<\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Matching Question Emphasis to What You Are Testing<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Testing Goal<\/strong><\/td><td><strong>Primary Question Phase<\/strong><\/td><td><strong>What to Prioritize<\/strong><\/td><\/tr><tr><td>Concept Clarity<\/td><td>Phase 1<\/td><td>First-impression questions triggered on screen load<\/td><\/tr><tr><td>Navigation And Ia<\/td><td>Phase 2<\/td><td>Time-on-page triggers on key navigation screens<\/td><\/tr><tr><td>Microcopy Validation<\/td><td>Phase 3<\/td><td>Post-task questions about specific labels and button text<\/td><\/tr><tr><td>Full Flow Usability<\/td><td>All three phases<\/td><td>Balanced question set across every task in the session<\/td><\/tr><tr><td>Comparative Testing<\/td><td>Phase 3<\/td><td>Difficulty ratings and preference questions across both versions<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The Prototype Exists. Now, Make It Tell You Something Useful.<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A prototype sitting in a shared folder is not a research asset.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It becomes one the moment you attach structured questions to it, send it to the right participants, and treat what comes back as design evidence rather than opinions to scroll through.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The teams that ship products users actually want are not running longer sessions or recruiting more participants.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">They are asking better questions at the right screen, collecting responses while the experience is still live, and using what they find to make a specific change before the next round.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That loop, repeated two or three times, is what separates a prototype test from a prototype review.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You have the prototype. You have the framework. The next step is putting them together using <a href=\"https:\/\/app.qualaroo.com\/signup\">Qualaroo<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn how to validate your designs and test your prototype. Discover the best prototype testing practices to create awesome products that sell.<\/p>\n","protected":false},"author":28,"featured_media":6683,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,158,157,123],"tags":[89,1756,72,80,97,75,96],"class_list":["post-3557","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-qualaroo","category-user-experience","category-user-research","category-ux","tag-prototype","tag-prototype-design","tag-prototype-testing","tag-prototyping","tag-questions-for-testing-my-prototype","tag-test-prototypes","tag-testing-prototype-questions"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Prototype Testing Guide: Steps for Product Teams<\/title>\n<meta name=\"description\" content=\"Run prototype tests that validate design decisions before launch. Includes testing methods, sample questions, and best practices for product teams.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Prototype Testing Guide: Steps for Product Teams\" \/>\n<meta property=\"og:description\" content=\"Run prototype tests that validate design decisions before launch. Includes testing methods, sample questions, and best practices for product teams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/\" \/>\n<meta property=\"og:site_name\" content=\"Qualaroo Blog - User Research and Customer Feedback Trends\" \/>\n<meta property=\"article:published_time\" content=\"2022-07-01T21:44:34+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-07-18T16:09:37+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2021\/09\/A-Step-by-Step-Guide-Testing-Your-Prototype-Blog-qualaroo.com_.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"758\" \/>\n\t<meta property=\"og:image:height\" content=\"335\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Qualaroo Editorial Team\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Qualaroo Editorial Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"17 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Prototype Testing Guide: Steps for Product Teams","description":"Run prototype tests that validate design decisions before launch. Includes testing methods, sample questions, and best practices for product teams.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/","og_locale":"en_US","og_type":"article","og_title":"Prototype Testing Guide: Steps for Product Teams","og_description":"Run prototype tests that validate design decisions before launch. Includes testing methods, sample questions, and best practices for product teams.","og_url":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/","og_site_name":"Qualaroo Blog - User Research and Customer Feedback Trends","article_published_time":"2022-07-01T21:44:34+00:00","article_modified_time":"2026-07-18T16:09:37+00:00","og_image":[{"width":758,"height":335,"url":"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2021\/09\/A-Step-by-Step-Guide-Testing-Your-Prototype-Blog-qualaroo.com_.jpg","type":"image\/jpeg"}],"author":"Qualaroo Editorial Team","twitter_misc":{"Written by":"Qualaroo Editorial Team","Est. reading time":"17 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/#article","isPartOf":{"@id":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/"},"author":{"name":"Qualaroo Editorial Team","@id":"https:\/\/qualaroo.com\/blog\/#\/schema\/person\/e04ac4df4fa53e249aaad0d804ca7144"},"headline":"Prototype Testing: A Step-by-Step Guide for Teams","datePublished":"2022-07-01T21:44:34+00:00","dateModified":"2026-07-18T16:09:37+00:00","mainEntityOfPage":{"@id":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/"},"wordCount":3236,"commentCount":0,"image":{"@id":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/#primaryimage"},"thumbnailUrl":"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2021\/09\/A-Step-by-Step-Guide-Testing-Your-Prototype-Blog-qualaroo.com_.jpg","keywords":["prototype","prototype design","prototype testing","prototyping","questions for testing my prototype","test prototypes","testing prototype questions"],"articleSection":["Qualaroo","User Experience","User Research","UX"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/","url":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/","name":"Prototype Testing Guide: Steps for Product Teams","isPartOf":{"@id":"https:\/\/qualaroo.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/#primaryimage"},"image":{"@id":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/#primaryimage"},"thumbnailUrl":"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2021\/09\/A-Step-by-Step-Guide-Testing-Your-Prototype-Blog-qualaroo.com_.jpg","datePublished":"2022-07-01T21:44:34+00:00","dateModified":"2026-07-18T16:09:37+00:00","author":{"@id":"https:\/\/qualaroo.com\/blog\/#\/schema\/person\/e04ac4df4fa53e249aaad0d804ca7144"},"description":"Run prototype tests that validate design decisions before launch. Includes testing methods, sample questions, and best practices for product teams.","breadcrumb":{"@id":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/#primaryimage","url":"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2021\/09\/A-Step-by-Step-Guide-Testing-Your-Prototype-Blog-qualaroo.com_.jpg","contentUrl":"https:\/\/qualaroo.com\/blog\/wp-content\/uploads\/2021\/09\/A-Step-by-Step-Guide-Testing-Your-Prototype-Blog-qualaroo.com_.jpg","width":758,"height":335,"caption":"Customer retention strategies"},{"@type":"BreadcrumbList","@id":"https:\/\/qualaroo.com\/blog\/step-by-step-testing-your-prototype\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/qualaroo.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Prototype Testing: A Step-by-Step Guide for Teams"}]},{"@type":"WebSite","@id":"https:\/\/qualaroo.com\/blog\/#website","url":"https:\/\/qualaroo.com\/blog\/","name":"Qualaroo Blog - User Research and Customer Feedback Trends","description":"Get the latest updates, trends, tips, &amp; guides around User Research and Customer Feedback on our blog.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/qualaroo.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/qualaroo.com\/blog\/#\/schema\/person\/e04ac4df4fa53e249aaad0d804ca7144","name":"Qualaroo Editorial Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/fd4f94bf064d2dbc3c244e9f508280147746419f64d3ae0c2fff507aeae8cd7a?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/fd4f94bf064d2dbc3c244e9f508280147746419f64d3ae0c2fff507aeae8cd7a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/fd4f94bf064d2dbc3c244e9f508280147746419f64d3ae0c2fff507aeae8cd7a?s=96&d=mm&r=g","caption":"Qualaroo Editorial Team"},"description":"Qualaroo Editorial Team is a passionate group of UX and feedback management experts dedicated to delivering top-notch content. We stay ahead of the curve on trends, tackle technical hurdles, and provide practical tips to boost your business. With our commitment to quality and integrity, you can be confident you're getting the most reliable resources to enhance your user experience improvement and lead generation initiatives.","url":"https:\/\/qualaroo.com\/blog\/author\/editorial-team\/"}]}},"_links":{"self":[{"href":"https:\/\/qualaroo.com\/blog\/wp-json\/wp\/v2\/posts\/3557","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qualaroo.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qualaroo.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qualaroo.com\/blog\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/qualaroo.com\/blog\/wp-json\/wp\/v2\/comments?post=3557"}],"version-history":[{"count":91,"href":"https:\/\/qualaroo.com\/blog\/wp-json\/wp\/v2\/posts\/3557\/revisions"}],"predecessor-version":[{"id":25463,"href":"https:\/\/qualaroo.com\/blog\/wp-json\/wp\/v2\/posts\/3557\/revisions\/25463"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/qualaroo.com\/blog\/wp-json\/wp\/v2\/media\/6683"}],"wp:attachment":[{"href":"https:\/\/qualaroo.com\/blog\/wp-json\/wp\/v2\/media?parent=3557"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qualaroo.com\/blog\/wp-json\/wp\/v2\/categories?post=3557"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qualaroo.com\/blog\/wp-json\/wp\/v2\/tags?post=3557"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}