{"version":1,"status":"published","updated":"2026-09-11","instructions":"/library.md","previewCollectsResponses":false,"publishing":"Use the existing authenticated Fillo setup and publishing flow. This catalog does not publish forms.","count":24,"forms":[{"id":"airbnb-experience-feedback","beforePublish":["Choose one experience and survey soon after it ends. Keep the experience or journey reference with the response.","Review low dimension scores as well as low overall ratings; do not average the dimensions into an overall score."],"title":"Experience feedback","organization":"Airbnb","sourceLogo":"/library/sources/airbnb.svg","category":"Feedback","tags":["customer feedback","reviews","experience","satisfaction","ratings"],"description":"Find the part of the experience that needs work, beyond an overall star rating.","evidence":"Published practice","attribution":"Adapted from Airbnb’s review approach","sourceNote":"Airbnb documents an overall rating, six hospitality categories, and a private note. Fillo replaces the hospitality categories with ease and expectations, and keeps one optional note. Airbnb has not validated these product questions.","useWhen":"After a customer completes a meaningful experience with your product.","avoidWhen":"A single task needs diagnosis. Use task-ease feedback instead of rating the whole experience.","interpretation":"Review the dimensions separately and read comments in context. Do not calculate the overall rating from category scores; do not compare these product dimensions with Airbnb’s hospitality ratings.","questionNotes":{"overall":"Ask for an overall impression before specific questions influence the answer.","ease":"Find out how easy the experience was, separately from the overall rating.","expectations":"Measure whether the experience delivered what the customer expected.","improve":"Let any respondent explain what mattered, without requiring another rating or a low score."},"sources":[{"title":"Why reviews matter","publisher":"Airbnb","date":"2025-09-17","url":"https://www.airbnb.com/resources/hosting-homes/a/why-reviews-matter-41"}],"flowSummary":"An overall rating, two separate dimensions, and one optional note","flowTitles":{"impression":"Overall impression","dimensions":"The details that mattered"},"flowNotes":{"impression":"Start with an overall rating before asking about individual parts of the experience.","dimensions":"Ask about ease and expectations separately, then offer one private note. A high overall rating should not prevent someone from explaining a problem."},"schema":{"version":1,"title":"Your experience with {{product}}","description":"Think about the experience you just had.","pages":[{"id":"impression","blocks":[{"id":"overall","kind":"rating","label":"How was your overall experience?","max":5,"required":true}]},{"id":"dimensions","title":"A little more detail","blocks":[{"id":"ease","kind":"linear_scale","label":"How easy was it to get what you needed?","min":1,"max":5,"minLabel":"Very difficult","maxLabel":"Very easy"},{"id":"expectations","kind":"linear_scale","label":"How well did the experience meet your expectations?","min":1,"max":5,"minLabel":"Not at all","maxLabel":"Completely"},{"id":"improve","kind":"long_text","label":"Anything you’d like the team to know?","description":"This note is for the team, not a public review","maxLength":2000}]}],"settings":{"submitLabel":"Send feedback","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=airbnb-experience-feedback"},{"id":"superhuman-product-market-fit","beforePublish":["Survey people with recent experience of the core value. Superhuman’s case used people who had used the product at least twice in the previous two weeks; choose and record a suitable cohort for your product.","Keep all four questions and compare the same eligibility rules over time. Review comments by disappointment segment."],"title":"Product–market fit","organization":"Superhuman","sourceLogo":"/library/sources/superhuman.svg","sourceLogoMonochrome":true,"category":"Research","tags":["feedback","pmf","product market fit","retention","Sean Ellis","Rahul Vohra","startup"],"description":"Discover who needs your product most, and what makes it matter to them.","evidence":"Practitioner case study","attribution":"Adapted from Superhuman’s PMF survey","sourceNote":"Founder Rahul Vohra published a four-question survey built on Sean Ellis’s method. The core disappointment item is retained; Fillo rewrites the follow-ups.","useWhen":"With people who have recently experienced your product’s core value, rather than prospects.","avoidWhen":"Before people have used the product, or as a substitute for retention and revenue evidence.","interpretation":"Segment comments by disappointment level and user context. Treat the familiar 40% threshold as a practitioner heuristic, never a statistical guarantee of product-market fit.","questionNotes":{"disappointment":"Measures how much the product would be missed, rather than generic satisfaction.","audience":"Find the people for whom the value is especially strong.","benefit":"Identify the outcome worth protecting as you expand the product.","improvement":"Look for barriers among people who already value the core benefit."},"sources":[{"title":"How Superhuman Built an Engine to Find Product Market Fit","publisher":"Rahul Vohra / First Round Review","date":"2018","url":"https://review.firstround.com/how-superhuman-built-an-engine-to-find-product-market-fit/"}],"flowSummary":"4 steps · one question at a time","flowNotes":{"attachment":"Start with the core disappointment measure. Survey recent users who have experienced the core value.","audience":"Give the audience question its own space. All respondents see it; segment during analysis.","benefit":"Ask about the value they get before asking for improvements.","improvement":"Finish with opportunities. Keep all four questions across segments to preserve the published method’s intent."},"schema":{"version":1,"title":"Help shape {{product}}","description":"Tell us what matters to you about {{product}}.","pages":[{"id":"attachment","blocks":[{"id":"disappointment","kind":"select","label":"How would you feel if you could no longer use {{product}}?","required":true,"options":[{"id":"very","label":"Very disappointed"},{"id":"somewhat","label":"Somewhat disappointed"},{"id":"not","label":"Not disappointed"}]}]},{"id":"audience","title":"Who it helps","blocks":[{"id":"audience","kind":"long_text","label":"Which people would get the most value from {{product}}?","maxLength":1500}]},{"id":"benefit","title":"What matters most","blocks":[{"id":"benefit","kind":"long_text","label":"What is the biggest benefit you get from {{product}}?","maxLength":1500}]},{"id":"improvement","title":"What could be better","blocks":[{"id":"improvement","kind":"long_text","label":"Which change would make {{product}} more useful to you?","maxLength":1500}]}],"settings":{"submitLabel":"Send answers","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=superhuman-product-market-fit"},{"id":"chromium-bug-report","beforePublish":["Send reports to an owned triage queue. Provide a separate private channel for security vulnerabilities.","If the app supplies environment details, let the reporter correct them: the bug may have happened on another device."],"title":"A bug report engineers can investigate","organization":"Chromium","sourceLogo":"/library/sources/chromium.svg","category":"Bug reports","tags":["Google","bug","issue","support","reproduction","developer"],"description":"Get the steps, context, and expected outcome an engineer needs to investigate.","evidence":"Published practice","attribution":"Adapted from Chromium’s reporting guidelines","sourceNote":"Chromium’s guidelines emphasize the problem, reproduction steps, expected behavior, and evidence. Fillo authors the questions and stages. Intermittent reports keep their steps; uncertain reports can describe the last action instead.","useWhen":"Someone encounters an unexpected behavior they can describe or repeat.","avoidWhen":"Reporting a security vulnerability. Use your private security reporting channel.","interpretation":"Try the steps in the reported environment and consider the impact. An intermittent or incomplete report can still describe a serious bug; investigate rather than automatically closing it for missing steps.","questionNotes":{"summary":"Make the issue recognizable in a triage queue.","actual":"Capture the concrete failure, including an error message if available.","expected":"Describe the expected outcome beside the actual outcome so they can be compared.","repeatable":"Distinguish a reproducible failure from an intermittent event before requesting instructions.","steps":"Keep the same steps field for repeatable and intermittent bugs. Do not force a reporter to invent reliable instructions.","last_action":"Ask for the last action when repeatable steps are unavailable.","environment":"Record enough context to narrow differences between machines.","evidence":"An optional link to a small example or screenshot can reduce back-and-forth. Do not include sensitive material."},"sources":[{"title":"Bug Life Cycle and Reporting Guidelines","publisher":"The Chromium Projects","date":"Undated; checked 2026-09-10","url":"https://www.chromium.org/for-testers/bug-reporting-guidelines/"}],"flowSummary":"3 steps · adapts to reproducibility","flowNotes":{"issue":"Establish the concrete mismatch: what happened and what should have happened belong together.","reproduce":"Keep useful steps even when a bug happens only sometimes. If the person is unsure how to repeat it, ask what happened just before the problem.","context":"Leave environment and an evidence link until the end. Neither should prevent someone from reporting a problem."},"schema":{"version":1,"title":"Report a problem","description":"Help us understand what happened in {{product}}. Leave out passwords and personal data.","pages":[{"id":"issue","blocks":[{"id":"summary","kind":"short_text","label":"Give the issue a short title","maxLength":200,"required":true},{"id":"actual","kind":"long_text","label":"What happened?","maxLength":3000,"required":true},{"id":"expected","kind":"long_text","label":"What did you expect to happen?","maxLength":2000,"required":true}]},{"id":"reproduce","title":"Recreating the problem","blocks":[{"id":"repeatable","kind":"select","label":"Can you make it happen again?","required":true,"options":[{"id":"yes","label":"Yes, I can repeat it"},{"id":"sometimes","label":"Only sometimes"},{"id":"unknown","label":"I’m not sure"}]},{"id":"steps","kind":"long_text","label":"What steps led to the issue?","placeholder":"1. Open…\n2. Choose…\n3. Notice…","visibleIf":[{"fieldId":"repeatable","op":"answered"},{"fieldId":"repeatable","op":"neq","value":"unknown"}],"maxLength":4000},{"id":"last_action","kind":"long_text","label":"What were you doing just before it happened?","visibleIf":[{"fieldId":"repeatable","op":"eq","value":"unknown"}],"maxLength":3000}]},{"id":"context","title":"A little context","blocks":[{"id":"environment","kind":"short_text","label":"Browser, device, and app version","description":"Use the device where the problem happened. Include what you know; it is fine to leave out details you cannot find.","maxLength":300},{"id":"evidence","kind":"url","label":"Link to a screenshot or small example","description":"Optional. Share only material you’re comfortable sending to the team"}]}],"settings":{"submitLabel":"Send report","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=chromium-bug-report"},{"id":"intercom-goal-onboarding","beforePublish":["Connect the answers to an actual next step, migration resource, or person who can help. Remove the help question if nobody can respond.","Avoid asking for account or product information the app already knows."],"title":"Onboarding around a goal","organization":"Intercom","sourceLogo":"/library/sources/intercom.svg","sourceLogoMonochrome":true,"category":"Onboarding","tags":["setup","jobs to be done","JTBD","activation","new user","welcome"],"description":"Learn what someone came to accomplish before showing them around.","evidence":"Published practice","attribution":"Inspired by Intercom’s onboarding method","sourceNote":"Intercom describes onboarding around customer jobs and the forces involved in switching. Fillo authored this intake and its migration branch. The form gathers context; your product must use it to tailor setup.","useWhen":"At first setup, when you can use the answers to choose a useful next step.","avoidWhen":"You cannot act on the answers. An extra questionnaire then only delays activation.","interpretation":"Group responses by desired outcome, then tailor the next setup step. Collect deeper switching stories in an interview rather than extending this intake.","questionNotes":{"goal":"Let the customer’s intended outcome lead the setup.","starting":"Identify a real switch without forcing people who are adding a tool or just exploring to claim they are replacing something.","previous":"Identify what a migrating user is replacing.","carry_over":"Learn what must survive the switch: data, a workflow, or a team habit.","help":"Ask whether the customer wants help before asking about a problem.","obstacle":"Reveal a concern field only when the customer wants help."},"sources":[{"title":"Improve your user onboarding with Jobs-to-be-Done insights","publisher":"Robbie Allan / Intercom","date":"2020-12-01","url":"https://www.intercom.com/blog/four-forces-user-onboarding/"}],"flowSummary":"2–3 steps · skips migration for new users","flowNotes":{"goal":"Learn the desired outcome and starting point. Avoid invented use-case options that only fit one kind of product.","switching":"Only people replacing an existing tool see this step. Ask what must transfer so setup can help them switch.","start":"Reveal an optional concern only when someone wants help. These answers must inform the next onboarding action."},"schema":{"version":1,"title":"Make {{product}} useful for you","description":"A little context will help us guide your first steps.","pages":[{"id":"goal","blocks":[{"id":"goal","kind":"short_text","label":"What would you like to accomplish first?","maxLength":400,"required":true},{"id":"starting","kind":"select","label":"Where are you starting from?","required":true,"options":[{"id":"new","label":"I’m starting from scratch"},{"id":"switching","label":"I’m replacing an existing tool or workflow"},{"id":"alongside","label":"I’m adding this alongside my current tools"},{"id":"exploring","label":"I’m exploring and haven’t decided yet"}]}],"next":[{"when":[{"fieldId":"starting","op":"answered"},{"fieldId":"starting","op":"neq","value":"switching"}],"to":"start"}]},{"id":"switching","title":"Make the switch easier","blocks":[{"id":"previous","kind":"short_text","label":"What do you use today?","maxLength":400},{"id":"carry_over","kind":"long_text","label":"What do you need to bring with you?","description":"For example, existing data or a workflow your team relies on","maxLength":1500}]},{"id":"start","title":"Your first step","blocks":[{"id":"help","kind":"select","label":"Would you like help getting started?","required":true,"options":[{"id":"no","label":"No, I’ll explore on my own"},{"id":"yes","label":"Yes, I’d like some help"}]},{"id":"obstacle","kind":"long_text","label":"What would help you get started?","visibleIf":[{"fieldId":"help","op":"eq","value":"yes"}],"maxLength":1500}]}],"settings":{"submitLabel":"Save preferences","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=intercom-goal-onboarding"},{"id":"single-ease-question","setup":[{"id":"task","label":"Task being evaluated","hint":"Name the task the person has just attempted.","example":"Find and download last month’s invoice","maxLength":250}],"measurement":{"name":"Single Ease Question (SEQ®)","version":"Current English item, MeasuringU 2024","itemIds":["ease"],"scoring":"Raw response from 1 to 7; higher means easier. Report the task-level mean, sample size, and uncertainty.","preserve":"Keep the item wording, seven numbered positions, endpoint labels, and immediate post-task timing. Include unsuccessful attempts."},"beforePublish":["Send immediately after the named task attempt, including failed attempts. Record task, product version, and participant cohort.","Keep observed task success separate from perceived ease. Do not show a target or benchmark before the answer."],"title":"Task ease, measured","organization":"MeasuringU","sourceLogo":"/library/sources/measuringu.png","sourceLogoMonochrome":true,"category":"Research","tags":["feedback","science","SEQ","usability","task ease","UX","onboarding"],"description":"Measure how easy a task felt while the experience is still fresh.","evidence":"Research-backed measure","attribution":"Based on the Single Ease Question (SEQ®)","sourceNote":"This is the current SEQ item shown by Sauro and Lewis in 2024, with its seven numbered positions and endpoint labels. Wording variants have also been studied; this entry keeps one documented version for consistent use.","useWhen":"Immediately after someone attempts a specific task, including an unsuccessful attempt.","avoidWhen":"As a retrospective measure of the entire product, or after only surveying successful users.","interpretation":"Compare the same task across releases, with comparable participants and sample sizes. A single rating is not a benchmark. SEQ is a registered trademark of MeasuringU.","questionNotes":{"ease":"Keep the seven-point scale and task context consistent when comparing scores."},"sources":[{"title":"The Evolution of the Single Ease Question (SEQ)","publisher":"Jeff Sauro and Jim Lewis / MeasuringU","date":"2024-08-06","url":"https://measuringu.com/evolution-of-seq/"}],"flowSummary":"1 question · the seven-point SEQ measure","flowNotes":{"task":"Ask immediately after the task attempt, successful or not. Keep the same item, scale, and timing when comparing versions; record which task was attempted."},"schema":{"version":1,"title":"How did that go?","description":"Think about this task: {{task}}.","pages":[{"id":"task","blocks":[{"id":"ease","kind":"linear_scale","label":"How easy or difficult was it to complete the task?","min":1,"max":7,"minLabel":"Very difficult","maxLabel":"Very easy","required":true}]}],"settings":{"submitLabel":"Send rating","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":false,"previewPath":"/library?form=single-ease-question"},{"id":"anthropic-response-feedback","setup":[{"id":"answer_context","label":"Answer being reviewed","hint":"Describe the request and include the answer, or give a reference the respondent can open. For an embed, replace this with the answer’s live context.","example":"You asked how to export an invoice. The answer said to open Billing, select an invoice, and choose Download PDF.","maxLength":4500,"multiline":true}],"beforePublish":["Show the feedback beside the relevant answer. A shared link should refer to one answer; an embed should carry a response reference.","Confirm reported failures against the answer. Collecting feedback does not by itself change a model or grant permission to reuse a conversation for training."],"title":"Feedback on an AI answer","organization":"Anthropic","sourceLogo":"/library/sources/anthropic.svg","sourceLogoMonochrome":true,"category":"AI products","tags":["feedback","Claude","AI","LLM","quality","model","answer","hallucination"],"description":"Capture whether an answer helped, then ask what went wrong.","evidence":"Published practice","attribution":"Inspired by Claude’s feedback interaction","sourceNote":"Claude documents thumbs-up/down feedback. The diagnostic categories and conditional follow-up here are Fillo’s design, not Anthropic’s published questionnaire.","useWhen":"Beside a specific generated answer, with a response reference supplied by your app.","avoidWhen":"Claiming model accuracy from self-selected feedback, or collecting entire conversations by default.","interpretation":"Review failure categories against the referenced answer. User feedback is a signal for investigation; confirm failures before adding them to an evaluation set.","questionNotes":{"helpful":"Start with a low-effort judgment about one answer.","reason":"Only ask for a failure category on the negative-answer path.","detail":"Allow an explanation even when none of the categories fits or the person skips them."},"sources":[{"title":"Manage user feedback settings on Team and Enterprise plans","publisher":"Claude Help Center / Anthropic","date":"2026-03-16","url":"https://support.claude.com/en/articles/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans"}],"flowSummary":"1–2 steps · helpful answers finish early","flowNotes":{"judgment":"Start with one quick judgment. A helpful answer can be submitted here, without a diagnostic step.","diagnosis":"A negative answer opens optional issue categories and a comment. Neither follow-up depends on answering the other."},"schema":{"version":1,"title":"Was this answer helpful?","description":"{{answer_context}}","pages":[{"id":"judgment","blocks":[{"id":"helpful","kind":"select","label":"Did this help you?","required":true,"options":[{"id":"yes","label":"Yes, it helped","icon":"thumbs_up"},{"id":"no","label":"No, not quite","icon":"thumbs_down"}]}],"next":[{"when":[{"fieldId":"helpful","op":"eq","value":"yes"}],"to":"end"}]},{"id":"diagnosis","title":"Help us understand why","blocks":[{"id":"reason","kind":"select","label":"What was the main issue?","options":[{"id":"incorrect","label":"The information was incorrect"},{"id":"instructions","label":"It missed my instructions"},{"id":"incomplete","label":"Something was missing"},{"id":"other","label":"Something else"}]},{"id":"detail","kind":"long_text","label":"What should we understand about this answer?","description":"Please leave out private conversation content","maxLength":2000}]}],"settings":{"submitLabel":"Send feedback","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":false,"previewPath":"/library?form=anthropic-response-feedback"},{"id":"google-heart-pulse","beforePublish":["Define the product goal and record the usage or journey context. Pair these answers with relevant behavioral measures.","This is a custom pulse, not a standardized HEART instrument. Keep timing, scales, and recruitment consistent across comparisons."],"title":"A pulse on product experience","organization":"Google Research","sourceLogo":"/library/sources/google.png","category":"Feedback","tags":["HEART","happiness","UX","satisfaction","research","science","product"],"description":"Pair how customers feel with whether they achieved what they came to do.","evidence":"Published practice","attribution":"Inspired by Google’s HEART framework","sourceNote":"Google’s CHI 2010 paper presents HEART as a metrics framework. This pulse is Fillo’s adaptation, not a Google survey or a validated HEART score.","useWhen":"You have a defined product goal and can pair feedback with behavioral measurements.","avoidWhen":"You need a standardized usability instrument. These questions have no external normative benchmark.","interpretation":"Choose a goal first, then compare the satisfaction and self-reported outcome with observed behavior. Keep sampling and timing consistent across releases.","questionNotes":{"satisfaction":"Capture an attitudinal signal alongside behavior.","outcome":"Separate liking the product from getting the intended result.","change":"An incomplete outcome or a satisfaction score of 1–3 opens an optional explanation. Finishing a task does not imply a good experience."},"sources":[{"title":"Measuring the User Experience on a Large Scale: User-Centered Metrics for Web Applications","publisher":"Kerry Rodden, Hilary Hutchinson and Xin Fu / Google, CHI 2010","date":"2010","url":"https://research.google/pubs/measuring-the-user-experience-on-a-large-scale-user-centered-metrics-for-web-applications/"}],"flowSummary":"Satisfaction and outcome, with a follow-up for friction","flowNotes":{"feeling":"Capture satisfaction before asking about success. It is an attitudinal signal, not a combined HEART score.","outcome":"Ask whether the person achieved their goal. A complete outcome and a satisfaction score of 4–5 can finish here.","barrier":"An incomplete task or a low satisfaction score opens an optional comment. Fillo chose this threshold; it is not part of the HEART framework."},"schema":{"version":1,"title":"Your experience with {{product}}","description":"Think about your most recent use of the product.","pages":[{"id":"feeling","blocks":[{"id":"satisfaction","kind":"linear_scale","label":"How satisfied are you with the experience?","min":1,"max":5,"minLabel":"Very dissatisfied","maxLabel":"Very satisfied","required":true}]},{"id":"outcome","title":"Getting things done","blocks":[{"id":"outcome","kind":"select","label":"Did you accomplish what you came to do?","required":true,"options":[{"id":"yes","label":"Yes, completely"},{"id":"partly","label":"Partly"},{"id":"no","label":"No"}]}],"next":[{"when":[{"fieldId":"outcome","op":"eq","value":"yes"},{"fieldId":"satisfaction","op":"gt","value":3}],"to":"end"}]},{"id":"barrier","title":"What could be better?","blocks":[{"id":"change","kind":"long_text","label":"What would have made this experience better?","maxLength":2000}]}],"settings":{"submitLabel":"Send feedback","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=google-heart-pulse"},{"id":"govuk-service-feedback","beforePublish":["Offer feedback at relevant exit points, including abandonment. Record the journey stage; a form completion may precede the real service outcome.","When reporting satisfaction, state which options count as satisfied and use submitted satisfaction answers as the denominator. Report the exit-state mix."],"title":"Feedback at the end of a journey","organization":"GOV.UK","sourceLogo":"/library/sources/govuk.svg","sourceLogoMonochrome":true,"category":"Feedback","tags":["service","completion","drop off","exit","customer","satisfaction","government"],"description":"Find the friction at the end of a journey, including why someone stopped.","evidence":"Published practice","attribution":"Adapted from the GOV.UK Service Manual","sourceNote":"GOV.UK recommends feedback at completion, during a service, and at drop-out. Fillo retains a fully labelled five-option satisfaction question across those states, and adds the outcome question and relevant comment prompts.","useWhen":"At a service endpoint or an exit, with the journey stage recorded alongside the response.","avoidWhen":"Treating a completed online form as the end of a service whose real outcome arrives later.","interpretation":"Analyze completed and abandoned journeys separately. Follow up at the actual service outcome if it happens after submission.","questionNotes":{"outcome":"Identify the journey stage so completed and abandoned journeys can be analyzed separately.","satisfaction":"Use the same satisfaction question at every exit state. Excluding people who stop would distort the journey-level result.","improvement":"Let people who finish share a suggestion, even after a positive rating.","barrier":"Ask what caused the exit, without requiring an explanation.","help":"Ask people still working what would help them finish."},"sources":[{"title":"Measuring user satisfaction","publisher":"GOV.UK Service Manual","date":"Updated 2021-02-19","url":"https://www.gov.uk/service-manual/measuring-success/measuring-user-satisfaction"}],"flowSummary":"2 steps · different questions at each exit","flowNotes":{"outcome":"Include people who finish, stop, or are still trying. Do not assume that reaching a form means a successful service outcome.","experience":"Offer the same satisfaction question whether the person finished, stopped, or is still trying. Only the optional comment prompt changes with their situation."},"schema":{"version":1,"title":"Help improve this service","description":"Please do not include personal or financial information.","pages":[{"id":"outcome","blocks":[{"id":"outcome","kind":"select","label":"Were you able to finish what you needed?","required":true,"options":[{"id":"done","label":"Yes"},{"id":"stopped","label":"No, I had to stop"},{"id":"ongoing","label":"I am still working on it"}]}]},{"id":"experience","title":"About your experience","blocks":[{"id":"satisfaction","kind":"select","label":"Overall, how satisfied are you with this service?","options":[{"id":"very_satisfied","label":"Very satisfied"},{"id":"satisfied","label":"Satisfied"},{"id":"neutral","label":"Neither satisfied nor dissatisfied"},{"id":"dissatisfied","label":"Dissatisfied"},{"id":"very_dissatisfied","label":"Very dissatisfied"}]},{"id":"improvement","kind":"long_text","label":"What could we improve?","maxLength":2000,"visibleIf":[{"fieldId":"outcome","op":"eq","value":"done"}]},{"id":"barrier","kind":"long_text","label":"What made you stop?","maxLength":2000,"visibleIf":[{"fieldId":"outcome","op":"eq","value":"stopped"}]},{"id":"help","kind":"long_text","label":"What would help you finish?","maxLength":2000,"visibleIf":[{"fieldId":"outcome","op":"eq","value":"ongoing"}]}]}],"settings":{"submitLabel":"Send feedback","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":false,"previewPath":"/library?form=govuk-service-feedback"},{"id":"stripe-cancellation-feedback","beforePublish":["Confirm cancellation before showing this optional survey. Do not use its submission as the cancellation action.","Associate the response with the cancellation event where appropriate. Do not treat feedback as permission for a retention campaign."],"title":"Cancellation feedback","organization":"Stripe","sourceLogo":"/library/sources/stripe.svg","sourceLogoMonochrome":true,"category":"Feedback","tags":["churn","cancel","retention","subscription","pricing"],"description":"Learn why someone leaves, without making cancellation harder.","evidence":"Published practice","attribution":"Adapted from Stripe’s cancellation feedback","sourceNote":"Stripe documents eight cancellation reasons and an optional explanation for Other. Fillo keeps that structure, rewrites the labels, and makes the whole survey optional.","useWhen":"After cancellation has been confirmed. This form does not cancel a subscription.","avoidWhen":"Making feedback a condition of cancellation, or treating a reason as permission to send a retention offer.","interpretation":"Look for patterns among people who respond. These answers explain reported reasons, not the causes of all churn.","questionNotes":{"reason":"One main reason makes recurring issues easier to spot. Leaving it blank is allowed.","other":"An optional explanation appears when the listed reasons do not fit."},"sources":[{"title":"Add a cancellation page to the customer portal","publisher":"Stripe Docs","date":"Reviewed 2026-09-11","url":"https://docs.stripe.com/customer-management/cancellation-page"}],"flowSummary":"1 step · a follow-up for other reasons","flowNotes":{"reason":"Keep the exit short. Only an unlisted reason opens a text field, and neither answer is required."},"schema":{"version":1,"title":"Leaving {{product}}","description":"Sharing feedback is optional and will not change your cancellation.","pages":[{"id":"reason","blocks":[{"id":"reason","kind":"select","label":"What’s the main reason you’re leaving?","options":[{"id":"cost","label":"The price does not work for me"},{"id":"features","label":"It is missing something I need"},{"id":"alternative","label":"I’m moving to another product"},{"id":"no_need","label":"My needs have changed"},{"id":"support","label":"I was disappointed with the support"},{"id":"ease","label":"I found it difficult to use"},{"id":"quality","label":"It did not work well enough"},{"id":"other","label":"Something else"}]},{"id":"other","kind":"long_text","label":"What made you decide to leave?","maxLength":2000,"visibleIf":[{"fieldId":"reason","op":"eq","value":"other"}]}]}],"settings":{"submitLabel":"Send feedback","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=stripe-cancellation-feedback"},{"id":"gitlab-feature-request","beforePublish":["Choose who will review requests and how they will follow up. This form does not promise a roadmap date.","Keep evidence about the problem and its impact separate from votes for a proposed solution."],"title":"A feature request with context","organization":"GitLab","sourceLogo":"/library/sources/gitlab.svg","category":"Feedback","tags":["feature","idea","request","roadmap","problem","proposal"],"description":"Understand the problem behind a request, even when there’s no proposed solution.","evidence":"Published practice","attribution":"Adapted from GitLab’s feature-request guidance","sourceNote":"GitLab’s product handbook asks for the problem, current workaround, and impact of a feature request. Fillo turns that guidance into a customer intake, with an optional proposal. This is not a copy of GitLab’s internal issue template.","useWhen":"A customer wants to do something your product does not yet support.","avoidWhen":"A feature is broken. A bug report should capture observed and expected behavior instead.","interpretation":"Group requests by the underlying problem and who it affects. A proposed solution is a starting point for investigation, not a delivery commitment.","questionNotes":{"problem":"Start with the situation the customer cannot resolve.","outcome":"Describe success before asking for a particular feature.","workaround":"Learn how the customer copes today; an existing workaround can reveal the actual job.","impact":"Understand the cost of the problem before treating a feature request as a priority.","idea":"Keep proposed solutions optional and distinct from the original problem."},"sources":[{"title":"Product management — submitting feature requests","publisher":"GitLab Handbook","date":"Reviewed 2026-09-11","url":"https://handbook.gitlab.com/handbook/product/product-management/#customer-feature-requests"}],"flowSummary":"The problem, its impact, and an optional idea","flowNotes":{"problem":"Capture the problem and desired outcome together, before introducing a solution.","context":"Ask about the workaround and impact, then leave room for an idea. No yes/no gate is needed for an optional suggestion."},"schema":{"version":1,"title":"Help shape {{product}}","description":"Tell us what you’re trying to do and what’s getting in the way.","pages":[{"id":"problem","blocks":[{"id":"problem","kind":"long_text","label":"What are you unable to do today?","description":"A recent example helps","required":true,"maxLength":3000},{"id":"outcome","kind":"long_text","label":"What would a good outcome look like?","maxLength":2000}]},{"id":"context","title":"A little context","blocks":[{"id":"workaround","kind":"long_text","label":"How do you handle this today?","maxLength":1500},{"id":"impact","kind":"long_text","label":"What does this problem prevent or make harder?","maxLength":1500},{"id":"idea","kind":"long_text","label":"How might we make this better?","maxLength":3000}]}],"settings":{"submitLabel":"Send request","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=gitlab-feature-request"},{"id":"zendesk-support-feedback","beforePublish":["Link each response to the relevant support conversation, and send after it is marked resolved.","Set up review of unresolved-issue feedback. A rating is not a fair stand-alone measure of an individual support agent’s performance."],"title":"Feedback after support","organization":"Zendesk","sourceLogo":"/library/sources/zendesk.svg","sourceLogoMonochrome":true,"category":"Feedback","tags":["CSAT","support","ticket","resolution","customer satisfaction"],"description":"A quick support rating, with room to explain when something went wrong.","evidence":"Published practice","attribution":"Adapted from Zendesk’s support CSAT","sourceNote":"Zendesk supports a two-option rating after a solved ticket, with optional text and reason questions for negative ratings. Fillo supplies the wording, reason options, and page break.","useWhen":"Soon after a specific support conversation is marked resolved.","avoidWhen":"As a general product satisfaction survey, or while the customer is still waiting for help.","interpretation":"Calculate positive ratings as a share of submitted ratings. Read negative answers alongside the conversation; survey replies do not represent every customer.","questionNotes":{"satisfied":"Anchor the rating to one support conversation.","reason":"Separate an unresolved issue from slow or unclear communication.","detail":"Let the customer describe the problem in their own words without requiring another answer."},"sources":[{"title":"Sending a CSAT survey to your customers","publisher":"Zendesk Help","date":"Reviewed 2026-09-11","url":"https://support.zendesk.com/hc/en-us/articles/7689997846554-Sending-a-CSAT-survey-to-your-customers"}],"flowSummary":"1–2 steps · follow up on a poor experience","flowNotes":{"rating":"A positive rating can finish immediately.","follow_up":"After a negative rating, offer two optional ways to explain what went wrong."},"schema":{"version":1,"title":"How was the help you received?","description":"Think about your recent conversation with the {{product}} support team.","pages":[{"id":"rating","blocks":[{"id":"satisfied","kind":"select","label":"Were you satisfied with the support?","required":true,"options":[{"id":"yes","label":"Satisfied"},{"id":"no","label":"Unsatisfied"}]}],"next":[{"when":[{"fieldId":"satisfied","op":"eq","value":"yes"}],"to":"end"}]},{"id":"follow_up","title":"What could we do better?","blocks":[{"id":"reason","kind":"select","label":"What was the main issue?","options":[{"id":"unresolved","label":"My problem is still unresolved"},{"id":"slow","label":"It took too long"},{"id":"unclear","label":"The help was hard to follow"},{"id":"other","label":"Something else"}]},{"id":"detail","kind":"long_text","label":"Anything you’d like us to understand?","maxLength":2000}]}],"settings":{"submitLabel":"Send feedback","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=zendesk-support-feedback"},{"id":"govuk-research-recruitment","setup":[{"id":"research_details","label":"Study or panel details","hint":"Explain the topic, commitment, incentive if any, team contact, and privacy notice URL. These details will appear before the questions.","example":"Example only: We are inviting people to a 30-minute remote study about finding invoices. Participation is voluntary. Add your real incentive, team contact, and privacy notice before publishing.","maxLength":4000,"multiline":true}],"beforePublish":["Describe the real study or panel, expected commitment, incentive if any, and how to contact the research team. Link a privacy notice that explains contact-data use and retention.","Permission to contact is not study consent. Arrange study-specific consent and accommodations before a session."],"title":"Invite people to user research","organization":"GOV.UK","sourceLogo":"/library/sources/govuk.svg","sourceLogoMonochrome":true,"category":"Research","tags":["interview","recruitment","participants","panel","contact","usability study"],"description":"Learn a little about someone’s experience, then ask if they’d like to talk.","evidence":"Published practice","attribution":"Adapted from GOV.UK’s research recruitment practice","sourceNote":"GDS describes recruiting from product users and planning for varied participant needs. Fillo’s form collects experience and permission to contact someone. It is not a study-specific eligibility screener or informed-consent form.","useWhen":"Inviting potential participants to a real study or research panel, with practical details and a privacy notice supplied before they answer.","avoidWhen":"Collecting a general mailing list. Permission to discuss research is not consent to participate in a session or receive marketing.","interpretation":"Recruit across relevant levels of experience, including people who are new. Do not treat this volunteer sample as representative of all users.","questionNotes":{"frequency":"Capture experience without automatically excluding new or infrequent users.","recent_goal":"A concrete goal provides context for a later conversation.","contact_permission":"Ask explicitly before collecting contact details.","email":"Only interested people need to provide a way to reach them.","name":"A name makes the invitation more personal, but is optional.","access":"Offer a way to mention practical participation needs without asking for a diagnosis."},"sources":[{"title":"Remote research: get insights from users in under a week","publisher":"Government Digital Service","date":"2014-01-09","url":"https://insidegovuk.blog.gov.uk/2014/01/09/remote-research-get-insights-from-users-in-under-a-week/"},{"title":"Write a recruitment brief","publisher":"GOV.UK Service Manual","date":"2016-03-31","url":"https://www.gov.uk/service-manual/user-research/write-a-recruitment-brief"}],"flowSummary":"2–3 steps · contact details only with permission","flowNotes":{"context":"Learn about experience and recent goals without treating them as automatic eligibility rules.","interest":"A decline ends the form. It never leads to a required email field.","contact":"Collect only the details needed to follow up and make participation possible."},"schema":{"version":1,"title":"Help us understand your experience with {{product}}","description":"{{research_details}}","pages":[{"id":"context","blocks":[{"id":"frequency","kind":"select","label":"How often do you use {{product}}?","required":true,"options":[{"id":"daily","label":"Most days"},{"id":"weekly","label":"About once a week"},{"id":"less","label":"Less often"},{"id":"new","label":"I haven’t used it yet"}]},{"id":"recent_goal","kind":"long_text","label":"What have you used it for recently?","maxLength":1500,"visibleIf":[{"fieldId":"frequency","op":"neq","value":"new"},{"fieldId":"frequency","op":"answered"}]}]},{"id":"interest","title":"Would you like to talk?","blocks":[{"id":"contact_permission","kind":"select","label":"May our team contact you about user research?","description":"You can decide whether to take part when you hear the details","required":true,"options":[{"id":"yes","label":"Yes, you can contact me"},{"id":"no","label":"No, thank you"}]}],"next":[{"when":[{"fieldId":"contact_permission","op":"eq","value":"no"}],"to":"end"}]},{"id":"contact","title":"How can we reach you?","blocks":[{"id":"email","kind":"email","label":"Email address","required":true},{"id":"name","kind":"short_text","label":"What should we call you?","maxLength":100},{"id":"access","kind":"long_text","label":"Is there anything that would help you take part?","description":"For example, a preferred way to communicate","maxLength":1500}]}],"settings":{"submitLabel":"Send response","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=govuk-research-recruitment"},{"id":"shopify-post-purchase-attribution","beforePublish":["Send after checkout. Use known purchase status instead of asking again when the app can supply it.","Store an appropriate order or cohort reference. Compare remembered sources with observed acquisition data; do not infer causal attribution."],"title":"How customers found you","organization":"Shopify","sourceLogo":"/library/sources/shopify.svg","category":"Feedback","tags":["checkout","post purchase","attribution","marketing","acquisition","growth"],"description":"Separate how a new customer discovered you from what made them buy today.","evidence":"Published practice","attribution":"Adapted from Shopify’s post-purchase survey guidance","sourceNote":"Shopify recommends short post-purchase surveys about discovery and buying influences, with different questions for new and returning customers. Fillo writes the questions, options, and routing.","useWhen":"After a purchase, while the decision is still fresh. Keep answering optional for the shopping journey.","avoidWhen":"Before checkout is complete, or as a replacement for observed acquisition and transaction data.","interpretation":"Treat answers as remembered influences, not proof that a channel caused a purchase. Separate first-time and returning customers.","questionNotes":{"first_purchase":"Returning customers skip the first-discovery question.","discovery":"Ask about first discovery, with an honest option for people who cannot remember.","other_source":"Let an unlisted channel be described without forcing it into a category.","decision":"Ask all buyers what influenced this purchase, separately from initial discovery."},"sources":[{"title":"How to Collect Customer Data in 2026","publisher":"Shopify","date":"2026-06-05","url":"https://www.shopify.com/enterprise/blog/collect-customer-data"}],"flowSummary":"2–3 steps · returning customers skip discovery","flowNotes":{"customer":"Establish whether this is a first purchase before asking about discovery.","discovery":"Ask new customers about the first place they remember encountering the brand.","decision":"Ask what influenced this purchase. An open question lets customers answer in their own words."},"schema":{"version":1,"title":"Thanks for choosing {{product}}","description":"A few quick questions about what brought you here.","pages":[{"id":"customer","blocks":[{"id":"first_purchase","kind":"select","label":"Is this your first purchase from us?","required":true,"options":[{"id":"yes","label":"Yes, it’s my first"},{"id":"no","label":"No, I’ve bought before"}]}],"next":[{"when":[{"fieldId":"first_purchase","op":"eq","value":"no"}],"to":"decision"}]},{"id":"discovery","title":"Finding us","blocks":[{"id":"discovery","kind":"select","label":"Where did you first hear about us?","required":true,"options":[{"id":"search","label":"A search engine"},{"id":"social","label":"Social media"},{"id":"friend","label":"Someone I know"},{"id":"publication","label":"An article, newsletter, or podcast"},{"id":"other","label":"Somewhere else"},{"id":"unknown","label":"I don’t remember"}]},{"id":"other_source","kind":"short_text","label":"Where was that?","maxLength":500,"visibleIf":[{"fieldId":"discovery","op":"eq","value":"other"}]}]},{"id":"decision","title":"This purchase","blocks":[{"id":"decision","kind":"long_text","label":"What made you decide to buy today?","maxLength":2000}]}],"settings":{"submitLabel":"Send feedback","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=shopify-post-purchase-attribution"},{"id":"umux-lite","measurement":{"name":"UMUX-Lite","version":"Original two-item, seven-point version (2013)","itemIds":["usefulness","ease"],"scoring":"For two complete 1–7 answers: (usefulness + ease − 2) × 100 / 12. Higher is better. This is the unadjusted 0–100 composite, not UMUX-LITEr or a SUS score.","preserve":"Keep both statements, seven-point agreement scale, and endpoint polarity. Substitute only the product name. Do not merge data with five-point UX-Lite."},"beforePublish":["Ask people who have used the product, and record their experience level and product version.","Keep the original items and seven response positions. Calculate the unadjusted composite only for complete responses."],"title":"Useful and easy to use","organization":"Lewis, Utesch & Maher","category":"Research","tags":["UMUX-Lite","IBM","MeasuringU","usability","benchmark","usefulness","research","science"],"description":"Two established questions about whether a product meets people’s needs and feels easy to use.","evidence":"Research-backed measure","attribution":"The UMUX-Lite by Lewis, Utesch, and Maher","sourceNote":"Lewis, Utesch, and Maher introduced UMUX-Lite in 2013. Fillo preserves its two items and seven-point agreement scale. This is the original UMUX-Lite, not the later five-point UX-Lite variant.","useWhen":"After people have used the product enough to assess it, including at the end of a usability study.","avoidWhen":"Diagnosing a single task, surveying prospects, or comparing scores after changing wording or scale without accounting for the change.","interpretation":"For a complete response, the unadjusted score is (usefulness + ease − 2) × 100 / 12. Report the mean, sample size, and uncertainty for comparable user groups. This 0–100 score is not a percentage satisfied or a SUS score; do not mix it with the regression-adjusted variant.","questionNotes":{"usefulness":"Keep the original requirements item so the instrument remains recognizable and comparable.","ease":"Keep the original ease item and use the same scale for both statements."},"sources":[{"title":"UMUX-LITE: When there’s no time for the SUS","publisher":"James R. Lewis, Brian S. Utesch and Deborah E. Maher / CHI","date":"2013","url":"https://doi.org/10.1145/2470654.2481287"},{"title":"Measuring Usability: From the SUS to the UMUX-Lite","publisher":"Jeff Sauro, MeasuringU","date":"2017-10-11","url":"https://measuringu.com/umux-lite/"}],"flowSummary":"1 step · two fixed seven-point scales","flowNotes":{"measure":"Keep both statements together. Branching or extra diagnostic questions would change this short measurement experience."},"schema":{"version":1,"title":"Your experience with {{product}}","description":"How much do you agree with each statement?","pages":[{"id":"measure","blocks":[{"id":"usefulness","kind":"linear_scale","label":"{{product}}’s capabilities meet my requirements.","min":1,"max":7,"minLabel":"Strongly disagree","maxLabel":"Strongly agree","required":true},{"id":"ease","kind":"linear_scale","label":"{{product}} is easy to use.","min":1,"max":7,"minLabel":"Strongly disagree","maxLabel":"Strongly agree","required":true}]}],"settings":{"submitLabel":"Send feedback","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=umux-lite"},{"id":"system-usability-scale","title":"System Usability Scale","organization":"John Brooke","category":"Research","tags":["SUS","usability","benchmark","science","post study","UX"],"description":"A complete, established measure of how usable a product feels after using it.","evidence":"Research-backed measure","attribution":"The System Usability Scale by John Brooke","sourceNote":"This entry keeps the ten-item English SUS and five-point agreement scale, using ‘awkward’ in item 8 as recommended by Lewis and Sauro for clarity. It is the documented wording variant, not an exact copy of the 1996 text. Acknowledge Brooke’s SUS in published reports.","useWhen":"After someone has used the product or completed a usability session, before the debrief.","avoidWhen":"You need to diagnose one task, or the respondent has not used the product. Use SEQ after a task or UMUX-Lite when two items are the practical limit.","interpretation":"For each complete response, subtract 1 from odd-numbered answers and subtract even-numbered answers from 5. Sum those contributions and multiply by 2.5. Report the composite, sample size, and uncertainty. A score of 80 is not 80% satisfied. Individual statements are not independent diagnostic scales.","beforePublish":["Identify the product version and participant cohort. Ask before a discussion that could influence the ratings.","Keep all ten statements and their polarity. Acknowledge John Brooke’s SUS in published reports; the instrument is © Digital Equipment Corporation, 1986."],"measurement":{"name":"System Usability Scale (SUS)","version":"Ten-item English SUS with the ‘awkward’ wording variant recommended in 2009","itemIds":["sus_1","sus_2","sus_3","sus_4","sus_5","sus_6","sus_7","sus_8","sus_9","sus_10"],"scoring":"For complete 1–5 answers: 2.5 × [(sus_1 − 1) + (5 − sus_2) + (sus_3 − 1) + (5 − sus_4) + (sus_5 − 1) + (5 − sus_6) + (sus_7 − 1) + (5 − sus_8) + (sus_9 − 1) + (5 − sus_10)]. Range 0–100; higher is better; not a percentage.","preserve":"Keep the ten statements, order, five-point agreement scale, and pre-debrief timing. Item 8 uses ‘awkward’. Report one composite, not a separate learnability subscale."},"questionNotes":{"sus_1":"SUS item 1. Score this positively worded statement as part of the full composite; do not interpret it as a separate scale.","sus_2":"SUS item 2. Reverse-code this negatively worded statement as part of the full composite; do not interpret it as a separate scale.","sus_3":"SUS item 3. Score this positively worded statement as part of the full composite; do not interpret it as a separate scale.","sus_4":"SUS item 4. Reverse-code this negatively worded statement as part of the full composite; do not interpret it as a separate scale.","sus_5":"SUS item 5. Score this positively worded statement as part of the full composite; do not interpret it as a separate scale.","sus_6":"SUS item 6. Reverse-code this negatively worded statement as part of the full composite; do not interpret it as a separate scale.","sus_7":"SUS item 7. Score this positively worded statement as part of the full composite; do not interpret it as a separate scale.","sus_8":"SUS item 8. Reverse-code this negatively worded statement as part of the full composite; do not interpret it as a separate scale.","sus_9":"SUS item 9. Score this positively worded statement as part of the full composite; do not interpret it as a separate scale.","sus_10":"SUS item 10. Reverse-code this negatively worded statement as part of the full composite; do not interpret it as a separate scale."},"flowSummary":"The complete ten-item instrument on one page","flowTitles":{"measure":"Rate the system you used"},"flowNotes":{"measure":"Keep the instrument together and in its original order. Its positive and negative statements contribute to one composite; conditional follow-ups would interrupt that experience."},"sources":[{"title":"SUS: A ‘quick and dirty’ usability scale","publisher":"John Brooke, in Usability Evaluation in Industry","date":"1996","url":"https://hci-studies.org/methods-and-measures/downloads/SUS_Brooke1996.pdf"},{"title":"The Factor Structure of the System Usability Scale — wording guidance in section 5.2","publisher":"James R. Lewis and Jeff Sauro / HCI International","date":"2009","url":"https://measuringu.com/wp-content/uploads/2017/07/Lewis_Sauro_HCII2009.pdf"}],"schema":{"version":1,"title":"Your experience with {{product}}","description":"Here, ‘this system’ means {{product}}. Give your first reaction to each statement. If you cannot judge a statement, choose the middle response, as the original questionnaire instructs.","pages":[{"id":"measure","blocks":[{"id":"sus_1","kind":"linear_scale","label":"I think that I would like to use this system frequently.","required":true,"min":1,"max":5,"minLabel":"Strongly disagree","maxLabel":"Strongly agree"},{"id":"sus_2","kind":"linear_scale","label":"I found the system unnecessarily complex.","required":true,"min":1,"max":5,"minLabel":"Strongly disagree","maxLabel":"Strongly agree"},{"id":"sus_3","kind":"linear_scale","label":"I thought the system was easy to use.","required":true,"min":1,"max":5,"minLabel":"Strongly disagree","maxLabel":"Strongly agree"},{"id":"sus_4","kind":"linear_scale","label":"I think that I would need the support of a technical person to be able to use this system.","required":true,"min":1,"max":5,"minLabel":"Strongly disagree","maxLabel":"Strongly agree"},{"id":"sus_5","kind":"linear_scale","label":"I found the various functions in this system were well integrated.","required":true,"min":1,"max":5,"minLabel":"Strongly disagree","maxLabel":"Strongly agree"},{"id":"sus_6","kind":"linear_scale","label":"I thought there was too much inconsistency in this system.","required":true,"min":1,"max":5,"minLabel":"Strongly disagree","maxLabel":"Strongly agree"},{"id":"sus_7","kind":"linear_scale","label":"I would imagine that most people would learn to use this system very quickly.","required":true,"min":1,"max":5,"minLabel":"Strongly disagree","maxLabel":"Strongly agree"},{"id":"sus_8","kind":"linear_scale","label":"I found the system very awkward to use.","required":true,"min":1,"max":5,"minLabel":"Strongly disagree","maxLabel":"Strongly agree"},{"id":"sus_9","kind":"linear_scale","label":"I felt very confident using the system.","required":true,"min":1,"max":5,"minLabel":"Strongly disagree","maxLabel":"Strongly agree"},{"id":"sus_10","kind":"linear_scale","label":"I needed to learn a lot of things before I could get going with this system.","required":true,"min":1,"max":5,"minLabel":"Strongly disagree","maxLabel":"Strongly agree"}]}],"settings":{"submitLabel":"Send ratings","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=system-usability-scale"},{"id":"ueq-short","title":"Practical and engaging: UEQ-S","organization":"UEQ research team","category":"Research","tags":["UEQ-S","user experience","pragmatic","hedonic","science","short survey"],"description":"Eight word pairs for a brief view of practical quality and how engaging a product feels.","evidence":"Research-backed measure","attribution":"The short User Experience Questionnaire (UEQ-S)","sourceNote":"Schrepp, Hinderks, and Thomaschewski publish eight word pairs with seven response positions. Fillo retains their order and polarity and displays the positions as numbered buttons. The authors make the materials freely available.","useWhen":"People have used the product and survey space is constrained, such as a short exit survey or a larger questionnaire with limited room for UX items.","avoidWhen":"You need the full UEQ’s six diagnostic dimensions. The authors recommend the full version for ordinary post-test evaluations where the extra detail is practical.","interpretation":"Subtract 4 from each 1–7 answer. Average the first four items for pragmatic quality and the last four for hedonic quality; each ranges from −3 to +3. Report both dimensions and sample size. Do not present their overall average as a universal UX KPI or report six full-UEQ scales from these eight items.","beforePublish":["Keep the eight pairs in order, with the negative endpoint on the left and positive on the right. Use an author-published language version when translating.","Decide whether the short version’s two broad dimensions answer your research question. Use the authors’ analysis materials for detailed interpretation."],"measurement":{"name":"UEQ-S","version":"Eight-item UEQ-S (2017); current English item sheet reviewed 2026-09-11","itemIds":["support","simplicity","efficiency","clarity","excitement","interest","invention","novelty"],"scoring":"Recode each 1–7 position as position − 4. Pragmatic quality = mean(support, simplicity, efficiency, clarity); hedonic quality = mean(excitement, interest, invention, novelty). Each is −3…+3, higher is better. This template requires all eight responses.","preserve":"Preserve all eight endpoint pairs, their order, seven positions, and negative-left polarity. This is the short version, not the full UEQ or UEQ+."},"questionNotes":{"support":"Published item 1, contributing to pragmatic quality. Keep the endpoint pair and direction unchanged.","simplicity":"Published item 2, contributing to pragmatic quality. Keep the endpoint pair and direction unchanged.","efficiency":"Published item 3, contributing to pragmatic quality. Keep the endpoint pair and direction unchanged.","clarity":"Published item 4, contributing to pragmatic quality. Keep the endpoint pair and direction unchanged.","excitement":"Published item 5, contributing to hedonic quality. Keep the endpoint pair and direction unchanged.","interest":"Published item 6, contributing to hedonic quality. Keep the endpoint pair and direction unchanged.","invention":"Published item 7, contributing to hedonic quality. Keep the endpoint pair and direction unchanged.","novelty":"Published item 8, contributing to hedonic quality. Keep the endpoint pair and direction unchanged."},"flowSummary":"Eight paired descriptions, two dimensions","flowTitles":{"measure":"Your impression of the product"},"flowNotes":{"measure":"Choose a position between each pair of words. Keep the practical items first and the experiential items second, as in the published short version."},"sources":[{"title":"UEQ handbook — short version","publisher":"UEQ authors","date":"Version 11, 2023-09-12","url":"https://ueq-online.org/Material/Handbook.pdf"},{"title":"UEQ-S items and language versions","publisher":"UEQ authors","date":"Reviewed 2026-09-11","url":"https://ueq-online.org/Material/UEQS_Items.pdf"},{"title":"Design and Evaluation of a Short Version of the User Experience Questionnaire","publisher":"Schrepp, Hinderks and Thomaschewski / IJIMAI","date":"2017","url":"https://doi.org/10.9781/ijimai.2017.09.001"}],"schema":{"version":1,"title":"Your impression of {{product}}","description":"For each pair of words, choose the position that best describes your experience. There are no right or wrong answers.","pages":[{"id":"measure","blocks":[{"id":"support","kind":"linear_scale","label":"obstructive — supportive","required":true,"min":1,"max":7,"minLabel":"obstructive","maxLabel":"supportive"},{"id":"simplicity","kind":"linear_scale","label":"complicated — easy","required":true,"min":1,"max":7,"minLabel":"complicated","maxLabel":"easy"},{"id":"efficiency","kind":"linear_scale","label":"inefficient — efficient","required":true,"min":1,"max":7,"minLabel":"inefficient","maxLabel":"efficient"},{"id":"clarity","kind":"linear_scale","label":"confusing — clear","required":true,"min":1,"max":7,"minLabel":"confusing","maxLabel":"clear"},{"id":"excitement","kind":"linear_scale","label":"boring — exciting","required":true,"min":1,"max":7,"minLabel":"boring","maxLabel":"exciting"},{"id":"interest","kind":"linear_scale","label":"not interesting — interesting","required":true,"min":1,"max":7,"minLabel":"not interesting","maxLabel":"interesting"},{"id":"invention","kind":"linear_scale","label":"conventional — inventive","required":true,"min":1,"max":7,"minLabel":"conventional","maxLabel":"inventive"},{"id":"novelty","kind":"linear_scale","label":"usual — leading edge","required":true,"min":1,"max":7,"minLabel":"usual","maxLabel":"leading edge"}]}],"settings":{"submitLabel":"Send ratings","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=ueq-short"},{"id":"microsoft-documentation-feedback","title":"Feedback on a help article","organization":"Microsoft Learn","sourceLogo":"/library/sources/microsoft.svg","category":"Feedback","tags":["documentation","docs","article","help center","content","knowledge base"],"description":"Find articles that leave readers stuck, and the information they need instead.","evidence":"Published practice","attribution":"Adapted from Microsoft Learn’s content feedback","sourceNote":"Microsoft documents helpfulness feedback, one or more reasons, and an optional comment. Fillo authors the reason labels and shows them after a negative answer; comments remain available after either answer.","useWhen":"At the end of a specific article, or from its feedback link while the content is still visible.","avoidWhen":"A reader needs a support reply or wants to report a product bug. Give those requests their own route.","interpretation":"Review the answer against the article and its version. Multiple reasons can apply to one response, so their percentages need not sum to 100. Feedback from volunteers does not measure whether all readers completed their tasks.","setup":[{"id":"article","label":"Article being reviewed","hint":"Use a recognizable title and, for a shared form, a link readers can open.","example":"Exporting your invoices — the help article you just read","maxLength":400}],"beforePublish":["Keep the article URL, language, and version with the response. In an embed, supply this from the page instead of asking the reader to retype it.","Send feedback to the content owner and provide a separate support link. Do not copy Microsoft’s privacy or response-time promises into your own form."],"questionNotes":{"helpful":"Ask about the article’s usefulness, not satisfaction with the whole product.","reasons":"Allow more than one content problem, and do not require a diagnosis before accepting a comment.","comment":"Leave room for a specific example, correction, or positive feedback after either answer."},"flowSummary":"One page with optional reasons after a negative answer","flowNotes":{"article":"Start with whether the article helped. A negative answer reveals optional reasons; the comment is available on both paths."},"sources":[{"title":"Provide feedback for Microsoft Learn content","publisher":"Microsoft Learn","date":"Updated 2024-10-04","url":"https://learn.microsoft.com/en-us/contribute/content/provide-feedback"}],"schema":{"version":1,"title":"Did this article help?","description":"About: {{article}}","pages":[{"id":"article","blocks":[{"id":"helpful","kind":"select","label":"Was this article helpful?","required":true,"options":[{"id":"yes","label":"Yes","icon":"thumbs_up"},{"id":"no","label":"No","icon":"thumbs_down"}]},{"id":"reasons","kind":"multi_select","label":"What needs attention?","description":"Choose any that apply","visibleIf":[{"fieldId":"helpful","op":"eq","value":"no"}],"options":[{"id":"missing","label":"Information I need is missing"},{"id":"unclear","label":"The explanation is hard to follow"},{"id":"incorrect","label":"Something is incorrect or out of date"},{"id":"example","label":"An example does not work"},{"id":"translation","label":"There is a translation problem"},{"id":"other","label":"Something else"}]},{"id":"comment","kind":"long_text","label":"What should the author know?","description":"Leave out passwords and private account details","maxLength":999}]}],"settings":{"submitLabel":"Send feedback","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":false,"previewPath":"/library?form=microsoft-documentation-feedback"},{"id":"w3c-accessibility-barrier","title":"Report an accessibility barrier","organization":"W3C WAI","category":"Bug reports","tags":["accessibility","a11y","keyboard","screen reader","WCAG","barrier"],"description":"Understand what someone could not do, without asking them to diagnose the technology.","evidence":"Published practice","attribution":"Adapted from W3C WAI’s reporting guidance","sourceNote":"W3C recommends describing the page, intended action, barrier, and relevant technology. It explicitly allows incomplete technical details. Fillo turns that guidance into a form and keeps follow-up contact optional.","useWhen":"Someone encounters an accessibility barrier in your website or product.","avoidWhen":"As the only way to get help. Someone blocked by a form may need email, phone, or another accessible route.","interpretation":"Recreate the barrier in the stated context, and consider its effect on the person’s task. A report is evidence to investigate, not a conformance audit or a diagnosis of the respondent.","beforePublish":["Provide an accessible alternative contact route and assign someone to review reports. Test this form with keyboard navigation and relevant assistive technology.","Ask only for relevant technical information. Do not require a disability diagnosis, screenshot, or software-version lookup before accepting a report."],"questionNotes":{"location":"A page name or description can locate the problem when a URL is unavailable.","goal":"The intended action explains the effect of the barrier.","barrier":"Ask what stopped or made the action difficult, without requiring technical terminology.","technology":"Optional browser, assistive technology, or settings can help reproduce the issue.","email":"A reply address is useful only when the person is happy to be contacted about this report."},"flowSummary":"The barrier first, optional technical and reply details second","flowTitles":{"problem":"What was difficult?","details":"Details that may help"},"flowNotes":{"problem":"Capture the intended action and what made it difficult. A page description is welcome; the person does not need to know a URL or accessibility standard.","details":"Offer optional technical context and a way to follow up. Neither is required to report a barrier."},"sources":[{"title":"Contacting Organizations about Inaccessible Websites","publisher":"W3C Web Accessibility Initiative","date":"Reviewed 2026-09-11","url":"https://www.w3.org/WAI/teach-advocate/contact-inaccessible-websites/"}],"schema":{"version":1,"title":"Report an accessibility problem","description":"Tell us about a barrier you encountered in {{product}}. Share only details you are comfortable sending.","pages":[{"id":"problem","blocks":[{"id":"location","kind":"short_text","label":"Where did you encounter the problem?","description":"A page name, link, or description is enough","maxLength":1000},{"id":"goal","kind":"short_text","label":"What were you trying to do?","required":true,"maxLength":500},{"id":"barrier","kind":"long_text","label":"What made that difficult or impossible?","required":true,"maxLength":4000}]},{"id":"details","title":"Details that may help","blocks":[{"id":"technology","kind":"long_text","label":"Anything useful about your device or setup?","description":"For example, your browser, screen reader, keyboard use, or zoom settings. Include only what you know.","maxLength":2000},{"id":"email","kind":"email","label":"Email for follow-up","description":"Only if you are happy for the team to contact you about this report"}]}],"settings":{"submitLabel":"Send report","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=w3c-accessibility-barrier"},{"id":"govuk-page-problem","title":"A quick page problem report","organization":"GOV.UK","sourceLogo":"/library/sources/govuk.svg","sourceLogoMonochrome":true,"category":"Bug reports","tags":["page","website","problem","broken","visitor","nontechnical"],"description":"Two plain questions when a visitor needs to tell you something is wrong.","evidence":"Published practice","attribution":"Adapted from GOV.UK’s page-problem report","sourceNote":"GOV.UK’s page footer asks what the visitor was doing and what went wrong. Fillo keeps those two intents and adds a visible page reference for a shared form. It is a short intake, not a full engineering bug report.","useWhen":"From a page-level ‘Report a problem’ link, while the visitor can still describe what happened.","avoidWhen":"A technical reporter can provide reproduction steps, or someone needs account-specific support.","interpretation":"Read the task and problem together, then route the report to the page or product owner. Do not infer prevalence from a voluntary problem-reporting form.","setup":[{"id":"page","label":"Page being reported","hint":"Give the page title or public URL. In an embed, supply the page reference from your app.","example":"Billing and invoices","maxLength":400}],"beforePublish":["Keep the page and release context with the response, and connect reports to a triage queue.","Provide a separate support route for personal or account-specific problems."],"questionNotes":{"task":"The intended action gives the report context.","problem":"Accept an ordinary description of the failure without requiring technical steps."},"flowSummary":"Task and problem, together on one page","flowNotes":{"problem":"The two answers describe one event. Keeping them together makes the report easy to review and avoids a page break for each sentence."},"sources":[{"title":"Get feedback page — live page-problem footer","publisher":"GOV.UK Service Manual","date":"Reviewed 2026-09-11","url":"https://www.gov.uk/service-manual/service-assessments/get-feedback-page"}],"schema":{"version":1,"title":"Report a problem with this page","description":"Page: {{page}}. Please leave out personal or financial information.","pages":[{"id":"problem","blocks":[{"id":"task","kind":"short_text","label":"What were you trying to do?","maxLength":1000,"required":true},{"id":"problem","kind":"long_text","label":"What went wrong?","maxLength":3000,"required":true}]}],"settings":{"submitLabel":"Send report","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":false,"previewPath":"/library?form=govuk-page-problem"},{"id":"intercom-trial-evaluation","title":"Find what held a trial back","organization":"Intercom","sourceLogo":"/library/sources/intercom.svg","sourceLogoMonochrome":true,"category":"Onboarding","tags":["trial","activation","conversion","evaluation","friction"],"description":"Separate a trial that never got started from a product that did not meet the goal.","evidence":"Practitioner case study","attribution":"Inspired by Intercom’s trial onboarding practice","sourceNote":"Intercom describes learning the trial’s use case and following up based on what people actually did. Fillo authors this short evaluation and its branches; Intercom did not publish these exact questions.","useWhen":"Near the end of a trial, or after a meaningful pause, with the trial period and usage context known.","avoidWhen":"As another interruption during every session, or as proof that a person intends to buy.","interpretation":"Separate not-started trials from attempted evaluations. Compare reported outcomes with actual activation and conversion; a stated obstacle is a lead for investigation, not a proven cause of lost revenue.","beforePublish":["Choose the trial cohort and timing. Avoid sending the same survey repeatedly to one person.","Assign an owner to review obstacles. Offer help only through a route that is actually staffed."],"questionNotes":{"goal":"Learn the intended outcome before treating usage as evidence of value.","tried":"Do not ask someone to rate a product they did not get a chance to try.","not_started":"A non-started trial needs a different explanation from a failed attempt.","outcome":"Ask whether an attempted trial answered the person’s need, with room for an unfinished evaluation.","obstacle":"Only an incomplete outcome opens the optional obstacle question."},"flowSummary":"The trial goal, then a branch for whether it was attempted","flowNotes":{"goal":"Establish the goal and whether the product was tried.","result":"Non-starters can explain what kept them away. People who tried it can describe the outcome and, where relevant, the obstacle."},"sources":[{"title":"Try before you buy: how sales can maximize the free product trial","publisher":"Patrick O’Neill / Intercom","date":"2018-07-16","url":"https://www.intercom.com/blog/try-before-you-buy/"}],"schema":{"version":1,"title":"How did your trial go?","description":"Think about your recent trial of {{product}}.","pages":[{"id":"goal","blocks":[{"id":"goal","kind":"short_text","label":"What did you hope to accomplish during the trial?","maxLength":1000},{"id":"tried","kind":"select","label":"Did you get a chance to try the product?","required":true,"options":[{"id":"yes","label":"Yes"},{"id":"no","label":"No, not yet"}]}]},{"id":"result","title":"What happened","blocks":[{"id":"not_started","kind":"long_text","label":"What kept you from trying it?","maxLength":2000,"visibleIf":[{"fieldId":"tried","op":"eq","value":"no"}]},{"id":"outcome","kind":"select","label":"Did you accomplish what you wanted to test?","required":true,"visibleIf":[{"fieldId":"tried","op":"eq","value":"yes"}],"options":[{"id":"yes","label":"Yes"},{"id":"partly","label":"Partly"},{"id":"no","label":"No"},{"id":"ongoing","label":"I’m still evaluating it"}]},{"id":"obstacle","kind":"long_text","label":"What, if anything, is getting in the way?","maxLength":2000,"visibleIf":[{"fieldId":"tried","op":"eq","value":"yes"},{"fieldId":"outcome","op":"answered"},{"fieldId":"outcome","op":"neq","value":"yes"}]}]}],"settings":{"submitLabel":"Send feedback","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=intercom-trial-evaluation"},{"id":"intercom-feature-adoption","title":"Why a feature is not being used","organization":"Intercom","sourceLogo":"/library/sources/intercom.svg","sourceLogoMonochrome":true,"category":"Feedback","tags":["feature","adoption","discovery","activation","unused","engagement"],"description":"Learn whether the problem is awareness, relevance, getting started, or continued use.","evidence":"Practitioner case study","attribution":"Inspired by Intercom’s feature-adoption research","sourceNote":"Des Traynor describes talking to the people who are not adopting a feature and investigating why. Fillo supplies these categories and branches, without the social-pressure framing that most other users already use it.","useWhen":"With people who could use a specific feature but appear not to. Let them correct that assumption.","avoidWhen":"You have not defined the feature or eligible audience, or you plan to turn hypothetical interest into a demand forecast.","interpretation":"Keep lack of awareness, lack of need, first-use friction, and discontinued use separate. Investigate each with product context; better communication may help where additional code would not.","setup":[{"id":"feature","label":"Feature being discussed","hint":"Use the name people see in your product, without a sales pitch.","example":"Saved reports","maxLength":160}],"beforePublish":["Choose a relevant cohort using observed behavior, and allow for missing or incorrect tracking.","Use the answers to decide whether to improve discovery, explain the feature, or investigate a usability problem. Do not treat disinterest as a defective response."],"questionNotes":{"experience":"Allow people to correct the assumption that they are not using the feature. Analytics may have misclassified them.","not_tried":"Ask about the actual obstacle to trying, rather than predicting future adoption.","stopped":"A person who stopped can describe what happened during real use."},"flowSummary":"A usage check, then a relevant optional follow-up","flowNotes":{"experience":"Establish the situation without assuming awareness. People who did not know the feature or already use it can finish here.","follow_up":"Only the not-tried and stopped-using paths get another question. Lack of a need is a valid explanation, and a comment is optional."},"sources":[{"title":"Lessons learned in growing a product — Looking for adoption","publisher":"Des Traynor / Intercom","date":"2016-04-13","url":"https://www.intercom.com/blog/lessons-learned-in-growing-a-product-business/"}],"schema":{"version":1,"title":"A question about {{feature}}","description":"We’d like to understand your experience with this feature in {{product}}.","pages":[{"id":"experience","blocks":[{"id":"experience","kind":"select","label":"Which best describes your experience with {{feature}}?","required":true,"options":[{"id":"unaware","label":"I did not know about it"},{"id":"not_tried","label":"I know about it, but have not tried it"},{"id":"stopped","label":"I tried it, but stopped using it"},{"id":"using","label":"I use it"}]}],"next":[{"when":[{"fieldId":"experience","op":"eq","value":"not_tried"}],"to":"follow_up"},{"when":[{"fieldId":"experience","op":"eq","value":"stopped"}],"to":"follow_up"},{"when":[],"to":"end"}]},{"id":"follow_up","title":"A little more context","blocks":[{"id":"not_tried","kind":"long_text","label":"What has kept you from trying it?","maxLength":2000,"visibleIf":[{"fieldId":"experience","op":"eq","value":"not_tried"}]},{"id":"stopped","kind":"long_text","label":"What led you to stop using it?","maxLength":2000,"visibleIf":[{"fieldId":"experience","op":"eq","value":"stopped"}]}]}],"settings":{"submitLabel":"Send feedback","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=intercom-feature-adoption"},{"id":"jarrett-visit-intent","title":"What brought someone here","organization":"Caroline Jarrett","category":"Research","tags":["visit","intent","top tasks","discovery","website","goals"],"description":"One question about the visitor’s purpose, asked while they still have it in mind.","evidence":"Published practice","attribution":"Inspired by Caroline Jarrett’s survey practice","sourceNote":"Jarrett recommends using an in-the-moment survey opportunity to ask about the purpose of a visit. Fillo uses one open question so the team can learn the visitor’s language before creating a fixed list of tasks.","useWhen":"Near the start of a visit, as a small optional invitation that does not block the person’s task.","avoidWhen":"You need to know whether the visit succeeded. That is a separate outcome question to ask at the appropriate exit.","interpretation":"Group answers by intended task and keep examples of the language people use. A self-selected sample suggests needs to investigate; it does not establish the exact population share of each task.","beforePublish":["Choose where and how often to invite visitors. Keep the underlying page usable without answering.","Record the entry page or relevant cohort. Use the answers to build a task taxonomy before replacing the open question with categories."],"questionNotes":{"purpose":"Ask about the current visit rather than a general opinion of the product."},"flowSummary":"One open question about the current visit","flowNotes":{"purpose":"Give the visitor a direct question they can answer now. Do not add a second gate asking whether they want to answer a survey."},"sources":[{"title":"Web form specialist Caroline Jarrett on designing surveys that work","publisher":"Caroline Jarrett, interviewed by Intercom","date":"Reviewed 2026-09-11","url":"https://www.intercom.com/blog/podcasts/caroline-jarrett-on-designing-surveys/"}],"schema":{"version":1,"title":"A quick question","description":"About your visit to {{product}} today.","pages":[{"id":"purpose","blocks":[{"id":"purpose","kind":"long_text","label":"What brought you here today?","maxLength":1500,"required":true}]}],"settings":{"submitLabel":"Send answer","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=jarrett-visit-intent"},{"id":"openai-summary-comparison","sourceLogo":"/library/sources/openai.svg","sourceLogoMonochrome":true,"title":"Compare two AI summaries","organization":"OpenAI","category":"AI products","tags":["evaluation","eval","pairwise","preference","summary","RLHF","human feedback"],"description":"Compare two summaries of the same text against a shared brief, with room to explain the choice.","evidence":"Published practice","attribution":"Adapted from OpenAI’s human summary comparisons","sourceNote":"OpenAI’s 2020 research used human comparisons of summaries, detailed guidance, and reviewer quality checks. Fillo provides a review form for one pair. Its wording, tie and unable-to-judge options are adaptations; it does not reproduce the training or evaluation pipeline.","useWhen":"Reviewers can read the same source text and both summaries, and understand the criteria for a useful summary.","avoidWhen":"Treating one preference as proof of factual accuracy, general model quality, or statistical significance.","interpretation":"Keep each judgment tied to the source, both outputs, and the reviewer assignment. Report ties and unable-to-judge answers separately. Compare balanced, blinded assignments across a defined evaluation set; do not infer a model win rate from one static pair.","setup":[{"id":"source_text","label":"Source text","hint":"Use a short text both summaries are based on. Only include material you may share with the reviewers.","example":"The export service will be unavailable on Saturday from 02:00 to 03:00 UTC for maintenance. Existing files remain accessible. Scheduled exports will resume automatically afterwards.","maxLength":4500,"multiline":true},{"id":"summary_a","label":"Summary A","hint":"Keep the model name out of the respondent-facing text.","example":"New exports will pause Saturday, 02:00–03:00 UTC. Existing files stay accessible, and scheduled exports resume afterwards.","maxLength":2500,"multiline":true},{"id":"summary_b","label":"Summary B","hint":"Both summaries must refer to the same source text.","example":"All files will be unavailable for three hours on Saturday. You will need to restart scheduled exports manually.","maxLength":2500,"multiline":true}],"beforePublish":["This shared form reviews one fixed pair. For a model comparison, assign multiple cases, vary A/B order, hide model identities, and store the mapping outside respondent-visible copy. The template does not randomize assignments.","Train reviewers on the task, check agreement on a sample, and inspect explanations. Feedback collection does not automatically train a model."],"questionNotes":{"source_heading":"Identify the shared source before showing either output.","source_text":"Reviewers need the source to check omissions and unsupported claims.","a_heading":"Use a neutral output label rather than a model name.","summary_a":"Show the first summary without a quality claim.","b_heading":"Use the same treatment for the second output.","summary_b":"Show the second summary against the same source and criteria.","brief":"Give reviewers a shared standard before asking for a preference.","preference":"Distinguish a preferred summary from a tie or an inability to judge.","explanation":"Capture the evidence behind the choice without making a comment mandatory."},"flowSummary":"One source, two summaries, and a reasoned comparison","flowTitles":{"comparison":"Read and compare"},"flowNotes":{"comparison":"Keep the source and both outputs available while the reviewer decides. A page break that hides the text would turn the task into a memory exercise."},"sources":[{"title":"Learning to summarize from human feedback","publisher":"Stiennon et al. / OpenAI","date":"2020-09-02","url":"https://arxiv.org/abs/2009.01325"},{"title":"Learning to summarize with human feedback","publisher":"OpenAI","date":"2020-09-04","url":"https://openai.com/index/learning-to-summarize-with-human-feedback/"}],"schema":{"version":1,"title":"Compare two summaries","description":"Read the original text and both summaries before choosing.","pages":[{"id":"comparison","blocks":[{"id":"source_heading","kind":"heading","text":"Original text"},{"id":"source_text","kind":"paragraph","text":"{{source_text}}"},{"id":"a_heading","kind":"heading","text":"Summary A"},{"id":"summary_a","kind":"paragraph","text":"{{summary_a}}"},{"id":"b_heading","kind":"heading","text":"Summary B"},{"id":"summary_b","kind":"paragraph","text":"{{summary_b}}"},{"id":"brief","kind":"paragraph","text":"Prefer a summary that preserves the important facts and purpose of the original, is clear and concise, and does not add unsupported claims. A longer or more polished answer is not necessarily better."},{"id":"preference","kind":"select","label":"Which summary does the better job?","required":true,"options":[{"id":"a","label":"Summary A"},{"id":"b","label":"Summary B"},{"id":"tie","label":"They are about equally good or bad"},{"id":"unable","label":"I cannot judge this pair"}]},{"id":"explanation","kind":"long_text","label":"What led to your choice?","description":"You can point to a missing fact, an unsupported claim, or something that was especially clear","maxLength":3000}]}],"settings":{"submitLabel":"Send comparison","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":false,"previewPath":"/library?form=openai-summary-comparison"},{"id":"user-experience-questionnaire","title":"A fuller view of user experience","organization":"UEQ research team","category":"Research","tags":["UEQ","full UEQ","26 items","user experience","usability","pragmatic","hedonic","science","study"],"description":"The full User Experience Questionnaire, covering six aspects of how a product feels to use.","evidence":"Research-backed measure","attribution":"The full User Experience Questionnaire (UEQ)","sourceNote":"The authors publish 26 English word pairs in a fixed order with mixed endpoint directions. Fillo preserves those items and presents the seven positions as buttons. The introduction is shortened; this is not a facsimile of the paper questionnaire.","useWhen":"After a usability session or enough product use to form an impression, when six experience dimensions are useful to the study.","avoidWhen":"A short exit invitation cannot support the full instrument. Use UEQ-S for two broad dimensions, or SEQ for one task. These ratings do not identify the exact interface change to make.","interpretation":"Recode each response toward the positive endpoint, then calculate the six published scale means. Keep Attractiveness, Perspicuity, Efficiency, Dependability, Stimulation, and Novelty separate. Use the authors’ current analysis tool for benchmark comparisons and record its version. A low scale suggests where to investigate, not a proven cause.","beforePublish":["Keep all 26 pairs in their published order and direction. Ask after product use and before the debrief; retain product version and participant context.","Use the author-published language version for your audience. Decide data-quality and exclusion rules before looking for a preferred result, and inspect flagged responses rather than treating a flag as proof of bad faith."],"measurement":{"name":"User Experience Questionnaire (UEQ)","version":"Full 26-item English questionnaire; authors’ language package reviewed 2026-09-11","itemIds":["ueq_1","ueq_2","ueq_3","ueq_4","ueq_5","ueq_6","ueq_7","ueq_8","ueq_9","ueq_10","ueq_11","ueq_12","ueq_13","ueq_14","ueq_15","ueq_16","ueq_17","ueq_18","ueq_19","ueq_20","ueq_21","ueq_22","ueq_23","ueq_24","ueq_25","ueq_26"],"scoring":"For positions 1–7, recode positive-left items 3,4,5,9,10,12,17,18,19,21,23,24,25 as 4 − response; recode the other items as response − 4. Average recoded items by scale: Attractiveness 1,12,14,16,24,25; Perspicuity 2,4,13,21; Efficiency 9,20,22,23; Dependability 8,11,17,19; Stimulation 5,6,7,18; Novelty 3,10,15,26. Each scale ranges −3…+3; higher is better. Do not create a grand total from all 26 items.","preserve":"Keep all endpoint pairs, mixed polarity, fixed item order, and seven positions. Use full-UEQ scoring and benchmarks, never the UEQ-S formula or benchmark."},"questionNotes":{"ueq_1":"Published UEQ item 1, contributing to Attractiveness. Preserve its direction; the positive endpoint is not always on the right.","ueq_2":"Published UEQ item 2, contributing to Perspicuity. Preserve its direction; the positive endpoint is not always on the right.","ueq_3":"Published UEQ item 3, contributing to Novelty. Preserve its direction; the positive endpoint is not always on the right.","ueq_4":"Published UEQ item 4, contributing to Perspicuity. Preserve its direction; the positive endpoint is not always on the right.","ueq_5":"Published UEQ item 5, contributing to Stimulation. Preserve its direction; the positive endpoint is not always on the right.","ueq_6":"Published UEQ item 6, contributing to Stimulation. Preserve its direction; the positive endpoint is not always on the right.","ueq_7":"Published UEQ item 7, contributing to Stimulation. Preserve its direction; the positive endpoint is not always on the right.","ueq_8":"Published UEQ item 8, contributing to Dependability. Preserve its direction; the positive endpoint is not always on the right.","ueq_9":"Published UEQ item 9, contributing to Efficiency. Preserve its direction; the positive endpoint is not always on the right.","ueq_10":"Published UEQ item 10, contributing to Novelty. Preserve its direction; the positive endpoint is not always on the right.","ueq_11":"Published UEQ item 11, contributing to Dependability. Preserve its direction; the positive endpoint is not always on the right.","ueq_12":"Published UEQ item 12, contributing to Attractiveness. Preserve its direction; the positive endpoint is not always on the right.","ueq_13":"Published UEQ item 13, contributing to Perspicuity. Preserve its direction; the positive endpoint is not always on the right.","ueq_14":"Published UEQ item 14, contributing to Attractiveness. Preserve its direction; the positive endpoint is not always on the right.","ueq_15":"Published UEQ item 15, contributing to Novelty. Preserve its direction; the positive endpoint is not always on the right.","ueq_16":"Published UEQ item 16, contributing to Attractiveness. Preserve its direction; the positive endpoint is not always on the right.","ueq_17":"Published UEQ item 17, contributing to Dependability. Preserve its direction; the positive endpoint is not always on the right.","ueq_18":"Published UEQ item 18, contributing to Stimulation. Preserve its direction; the positive endpoint is not always on the right.","ueq_19":"Published UEQ item 19, contributing to Dependability. Preserve its direction; the positive endpoint is not always on the right.","ueq_20":"Published UEQ item 20, contributing to Efficiency. Preserve its direction; the positive endpoint is not always on the right.","ueq_21":"Published UEQ item 21, contributing to Perspicuity. Preserve its direction; the positive endpoint is not always on the right.","ueq_22":"Published UEQ item 22, contributing to Efficiency. Preserve its direction; the positive endpoint is not always on the right.","ueq_23":"Published UEQ item 23, contributing to Efficiency. Preserve its direction; the positive endpoint is not always on the right.","ueq_24":"Published UEQ item 24, contributing to Attractiveness. Preserve its direction; the positive endpoint is not always on the right.","ueq_25":"Published UEQ item 25, contributing to Attractiveness. Preserve its direction; the positive endpoint is not always on the right.","ueq_26":"Published UEQ item 26, contributing to Novelty. Preserve its direction; the positive endpoint is not always on the right."},"flowSummary":"The full instrument, with six scale scores","flowTitles":{"measure":"Your impression after using the product"},"flowNotes":{"measure":"Keep the questionnaire in its published sequence. The endpoint direction changes between items; read each pair. There are no branches or diagnostic interruptions inside the measure."},"sources":[{"title":"UEQ questionnaire and analysis materials","publisher":"UEQ authors","date":"Reviewed 2026-09-11","url":"https://ueq-online.org/"},{"title":"UEQ handbook","publisher":"Martin Schrepp","date":"Version 11, 2023-09-12","url":"https://ueq-online.org/Material/Handbook.pdf"},{"title":"Construction and Evaluation of a User Experience Questionnaire","publisher":"Bettina Laugwitz, Theo Held and Martin Schrepp / USAB","date":"2008","url":"https://doi.org/10.1007/978-3-540-89350-9_6"}],"schema":{"version":1,"title":"Your experience with {{product}}","description":"Choose a position between each pair of words to give your first impression of the product. Read both endpoints: their direction changes. Answer every pair, even if an attribute does not seem to fit completely. There are no right or wrong answers.","pages":[{"id":"measure","blocks":[{"id":"ueq_1","kind":"linear_scale","label":"annoying — enjoyable","required":true,"min":1,"max":7,"minLabel":"annoying","maxLabel":"enjoyable"},{"id":"ueq_2","kind":"linear_scale","label":"not understandable — understandable","required":true,"min":1,"max":7,"minLabel":"not understandable","maxLabel":"understandable"},{"id":"ueq_3","kind":"linear_scale","label":"creative — dull","required":true,"min":1,"max":7,"minLabel":"creative","maxLabel":"dull"},{"id":"ueq_4","kind":"linear_scale","label":"easy to learn — difficult to learn","required":true,"min":1,"max":7,"minLabel":"easy to learn","maxLabel":"difficult to learn"},{"id":"ueq_5","kind":"linear_scale","label":"valuable — inferior","required":true,"min":1,"max":7,"minLabel":"valuable","maxLabel":"inferior"},{"id":"ueq_6","kind":"linear_scale","label":"boring — exciting","required":true,"min":1,"max":7,"minLabel":"boring","maxLabel":"exciting"},{"id":"ueq_7","kind":"linear_scale","label":"not interesting — interesting","required":true,"min":1,"max":7,"minLabel":"not interesting","maxLabel":"interesting"},{"id":"ueq_8","kind":"linear_scale","label":"unpredictable — predictable","required":true,"min":1,"max":7,"minLabel":"unpredictable","maxLabel":"predictable"},{"id":"ueq_9","kind":"linear_scale","label":"fast — slow","required":true,"min":1,"max":7,"minLabel":"fast","maxLabel":"slow"},{"id":"ueq_10","kind":"linear_scale","label":"inventive — conventional","required":true,"min":1,"max":7,"minLabel":"inventive","maxLabel":"conventional"},{"id":"ueq_11","kind":"linear_scale","label":"obstructive — supportive","required":true,"min":1,"max":7,"minLabel":"obstructive","maxLabel":"supportive"},{"id":"ueq_12","kind":"linear_scale","label":"good — bad","required":true,"min":1,"max":7,"minLabel":"good","maxLabel":"bad"},{"id":"ueq_13","kind":"linear_scale","label":"complicated — easy","required":true,"min":1,"max":7,"minLabel":"complicated","maxLabel":"easy"},{"id":"ueq_14","kind":"linear_scale","label":"unlikable — pleasing","required":true,"min":1,"max":7,"minLabel":"unlikable","maxLabel":"pleasing"},{"id":"ueq_15","kind":"linear_scale","label":"usual — leading edge","required":true,"min":1,"max":7,"minLabel":"usual","maxLabel":"leading edge"},{"id":"ueq_16","kind":"linear_scale","label":"unpleasant — pleasant","required":true,"min":1,"max":7,"minLabel":"unpleasant","maxLabel":"pleasant"},{"id":"ueq_17","kind":"linear_scale","label":"secure — not secure","required":true,"min":1,"max":7,"minLabel":"secure","maxLabel":"not secure"},{"id":"ueq_18","kind":"linear_scale","label":"motivating — demotivating","required":true,"min":1,"max":7,"minLabel":"motivating","maxLabel":"demotivating"},{"id":"ueq_19","kind":"linear_scale","label":"meets expectations — does not meet expectations","required":true,"min":1,"max":7,"minLabel":"meets expectations","maxLabel":"does not meet expectations"},{"id":"ueq_20","kind":"linear_scale","label":"inefficient — efficient","required":true,"min":1,"max":7,"minLabel":"inefficient","maxLabel":"efficient"},{"id":"ueq_21","kind":"linear_scale","label":"clear — confusing","required":true,"min":1,"max":7,"minLabel":"clear","maxLabel":"confusing"},{"id":"ueq_22","kind":"linear_scale","label":"impractical — practical","required":true,"min":1,"max":7,"minLabel":"impractical","maxLabel":"practical"},{"id":"ueq_23","kind":"linear_scale","label":"organized — cluttered","required":true,"min":1,"max":7,"minLabel":"organized","maxLabel":"cluttered"},{"id":"ueq_24","kind":"linear_scale","label":"attractive — unattractive","required":true,"min":1,"max":7,"minLabel":"attractive","maxLabel":"unattractive"},{"id":"ueq_25","kind":"linear_scale","label":"friendly — unfriendly","required":true,"min":1,"max":7,"minLabel":"friendly","maxLabel":"unfriendly"},{"id":"ueq_26","kind":"linear_scale","label":"conservative — innovative","required":true,"min":1,"max":7,"minLabel":"conservative","maxLabel":"innovative"}]}],"settings":{"submitLabel":"Send ratings","successTitle":"Thank you for sharing","successMessage":"Your response has been received."}},"requiresProductName":true,"previewPath":"/library?form=user-experience-questionnaire"}]}