[{"data":1,"prerenderedAt":1545},["ShallowReactive",2],{"kc-/knowledge/conversational-form-design":3,"kc-clusters-/knowledge/conversational-form-design":139,"kc-related-/knowledge/conversational-form-design":1544},{"id":4,"title":5,"author":6,"body":7,"date":103,"description":104,"draft":105,"extension":106,"faqs":107,"image":117,"isPillar":118,"meta":119,"navigation":118,"path":120,"pillar":121,"pillarName":121,"seo":122,"sources":123,"stem":132,"tags":133,"takeaways":137,"updated":103,"__hash__":138},"knowledge/knowledge/conversational-form-design.md","Conversational Form Design: Asking One Question at a Time","RoundPushPin Team",{"type":8,"value":9,"toc":95},"minimark",[10,14,19,26,30,41,45,48,81,85],[11,12,13],"p",{},"Conversational form design presents a form as a focused sequence — one question at a time — rather than a single page packed with fields. The goal is to lower the perceived effort of each step so more people start, stay, and finish, while still capturing clean, structured data underneath.",[15,16,18],"h2",{"id":17},"what-is-a-conversational-form","What is a conversational form?",[11,20,21,25],{},[22,23,24],"strong",{},"A conversational form asks one question per screen, advances as the respondent answers, and uses transitions to keep the flow moving."," It borrows from how a good interviewer works: ask, listen, ask the next relevant thing — instead of handing someone a clipboard with forty fields. The format is a presentation choice; the data it collects can still be fully structured.",[15,27,29],{"id":28},"why-does-asking-one-question-at-a-time-help","Why does asking one question at a time help?",[11,31,32,35,36,40],{},[22,33,34],{},"Because perceived length and cognitive load drive abandonment."," Research on web surveys finds that longer questionnaires reduce participation and response quality (Galesic & Bosnjak, 2009), and the UX principle of ",[37,38,39],"em",{},"progressive disclosure"," — showing only what's relevant at each step — is a well-established way to reduce that load (Nielsen Norman Group). Showing one question at a time is progressive disclosure applied to forms.",[15,42,44],{"id":43},"what-does-good-conversational-design-get-right","What does good conversational design get right?",[11,46,47],{},"It manages three things at once:",[49,50,51,58,70],"ul",{},[52,53,54,57],"li",{},[22,55,56],{},"Momentum"," — each screen is a small, obvious step, so starting feels cheap and finishing feels close.",[52,59,60,63,64,69],{},[22,61,62],{},"Relevance"," — ",[65,66,68],"a",{"href":67},"/knowledge/conditional-logic-in-forms","conditional logic"," hides questions that don't apply, so no one wades through irrelevant fields.",[52,71,72,75,76,80],{},[22,73,74],{},"Clarity"," — each question is phrased to be understood and answered the same way by everyone, which is its own discipline (see ",[65,77,79],{"href":78},"/knowledge/how-to-ask-the-right-questions-in-a-form","how to ask the right questions",").",[15,82,84],{"id":83},"does-conversational-ux-hurt-the-data","Does conversational UX hurt the data?",[11,86,87,90,91,94],{},[22,88,89],{},"Only if the tool treats the data as an afterthought."," The format is about presentation; the storage is a separate decision. RoundPushPin keeps the conversational experience but maps every answer to a typed column in a relational database — so you get higher completion ",[37,92,93],{},"and"," structured, queryable data. The articles in this topic go deeper on each part of designing forms people finish.",{"title":96,"searchDepth":97,"depth":97,"links":98},"",2,[99,100,101,102],{"id":17,"depth":97,"text":18},{"id":28,"depth":97,"text":29},{"id":43,"depth":97,"text":44},{"id":83,"depth":97,"text":84},"2026-02-12","Conversational form design presents one question at a time instead of a wall of fields. This guide explains why the format works, what the survey-methodology research says about length and question quality, and how to design forms people finish.",false,"md",[108,111,114],{"q":109,"a":110},"Do conversational forms get higher completion rates?","They can, because showing one question at a time lowers perceived effort, and survey research links shorter, lower-burden forms to higher participation. Completion still depends on asking few, clear, relevant questions.",{"q":112,"a":113},"What is the difference between a conversational form and a regular form?","A conversational form asks one question per screen and advances as you answer; a regular form shows all fields on one page. The data collected can be identical — the difference is presentation and perceived effort.",{"q":115,"a":116},"Are conversational forms good for surveys?","Yes for most surveys — the one-at-a-time format reduces fatigue. For very long, matrix-style instruments, pair the format with a clear progress indicator so respondents can gauge how much is left.","/images/knowledge/conversational-form-design.png",true,{},"/knowledge/conversational-form-design",null,{"title":5,"description":104},[124,128],{"title":125,"url":126,"publisher":127},"Galesic, M. & Bosnjak, M. (2009) — Effects of questionnaire length on participation and indicators of response quality in a web survey","https://doi.org/10.1093/poq/nfp031","Public Opinion Quarterly",{"title":129,"url":130,"publisher":131},"Progressive Disclosure (Jakob Nielsen)","https://www.nngroup.com/articles/progressive-disclosure/","Nielsen Norman Group","knowledge/conversational-form-design",[134,135,136],"form design","ux","guide",[],"0keBt93sanctFvicv_WGXbHUHSFX7LcrnniJOViPG8I",[140,315,464,598,691,864,1035,1149,1294,1416],{"id":141,"title":142,"author":6,"body":143,"date":287,"description":288,"draft":105,"extension":106,"faqs":289,"image":299,"isPillar":105,"meta":300,"navigation":118,"path":301,"pillar":302,"pillarName":303,"seo":304,"sources":305,"stem":309,"tags":310,"takeaways":313,"updated":103,"__hash__":314},"knowledge/knowledge/building-better-forms.md","Building Better Forms: Our Product Vision",{"type":8,"value":144,"toc":275},[145,148,152,158,161,164,168,173,176,180,188,192,195,199,202,206,244,248,251,272],[11,146,147],{},"Forms are everywhere. Job applications, customer surveys, event registrations, onboarding flows. They're one of the most common ways software collects data from humans. Yet the tools we use to build them force us to choose between great UX and great data.",[15,149,151],{"id":150},"do-you-have-to-choose-between-form-ux-and-data-quality","Do you have to choose between form UX and data quality?",[11,153,154,157],{},[22,155,156],{},"No — that trade-off is a false one."," Polished form tools tend to hide your data in a black box, while custom-built forms give you data control at the cost of weeks of work and weaker UX. RoundPushPin gives you both: conversational UX on top of a structured, queryable database.",[11,159,160],{},"On one side, you have Typeform and its clones. Beautiful, conversational, high completion rates. But your data lives in a black box. On the other side, you have custom-built forms. Full control over your data model, but you're spending weeks building something that still doesn't look as good.",[11,162,163],{},"RoundPushPin eliminates this trade-off.",[15,165,167],{"id":166},"what-are-roundpushpins-design-principles","What are RoundPushPin's design principles?",[169,170,172],"h3",{"id":171},"_1-respondent-experience-first","1. Respondent Experience First",[11,174,175],{},"Every form built with RoundPushPin uses a one-question-at-a-time interface. CSS Scroll Snap provides native-feeling transitions. Vue's transition system handles animations. The result feels smooth, focused, and respectful of the respondent's attention.",[169,177,179],{"id":178},"_2-data-as-a-first-class-citizen","2. Data as a First-Class Citizen",[11,181,182,183,187],{},"Behind the scenes, every form maps to a PostgreSQL schema. We use Drizzle ORM with TypeScript to define table structures that mirror your form's questions. This means your data is queryable, joinable, and analyzable from the moment it's collected — the reasoning behind ",[65,184,186],{"href":185},"/knowledge/why-relational-data","choosing a relational model over JSON blobs",".",[169,189,191],{"id":190},"_3-developer-experience-matters","3. Developer Experience Matters",[11,193,194],{},"RoundPushPin is built with TypeScript end-to-end. Validation schemas defined with Zod work on both client and server — the same rules that provide real-time feedback to respondents also protect your API. No duplication, no drift.",[169,196,198],{"id":197},"_4-own-your-infrastructure","4. Own Your Infrastructure",[11,200,201],{},"We believe your data should live on your servers. RoundPushPin is self-hosted by default. A Docker Compose file gets you running with PostgreSQL in one command. No vendor lock-in, no data residency concerns, no surprise pricing.",[15,203,205],{"id":204},"what-is-roundpushpin-built-with","What is RoundPushPin built with?",[49,207,208,214,220,226,232,238],{},[52,209,210,213],{},[22,211,212],{},"Nuxt 4"," for server-side rendering and client-side interactivity",[52,215,216,219],{},[22,217,218],{},"FormKit"," for schema-driven form rendering",[52,221,222,225],{},[22,223,224],{},"Drizzle ORM"," for type-safe database operations",[52,227,228,231],{},[22,229,230],{},"PostgreSQL"," for relational data storage",[52,233,234,237],{},[22,235,236],{},"Pinia"," for client-side state management",[52,239,240,243],{},[22,241,242],{},"Zod"," for isomorphic validation",[15,245,247],{"id":246},"what-is-roundpushpin-building-next","What is RoundPushPin building next?",[11,249,250],{},"Our roadmap is focused on three areas:",[252,253,254,260,266],"ol",{},[52,255,256,259],{},[22,257,258],{},"The Form Builder",": A visual editor for creating forms with conditional logic, validation rules, and custom themes",[52,261,262,265],{},[22,263,264],{},"The Response Engine",": Real-time data capture with event sourcing for granular analytics",[52,267,268,271],{},[22,269,270],{},"The Analytics Layer",": Built-in dashboards for completion rates, drop-off analysis, and response patterns",[11,273,274],{},"We're shipping fast and improving constantly. If you care about forms and data, follow along.",{"title":96,"searchDepth":97,"depth":97,"links":276},[277,278,285,286],{"id":150,"depth":97,"text":151},{"id":166,"depth":97,"text":167,"children":279},[280,282,283,284],{"id":171,"depth":281,"text":172},3,{"id":178,"depth":281,"text":179},{"id":190,"depth":281,"text":191},{"id":197,"depth":281,"text":198},{"id":204,"depth":97,"text":205},{"id":246,"depth":97,"text":247},"2026-01-25","How RoundPushPin reimagines the form-building experience with conversational UX, developer-first design, and structured data.",[290,293,296],{"q":291,"a":292},"What makes a good form builder?","One that delivers a high-completion experience and keeps the resulting data usable. Many tools optimize the first and neglect the second; the better question after 'how does it look?' is 'how do I query this data?'",{"q":294,"a":295},"Why does form data structure matter?","Because the storage model caps what you can do later: structured, typed data is queryable and joinable, while unstructured blobs must be wrangled before any analysis. Structure is the difference between data you can question and data you fight.",{"q":297,"a":298},"Can I self-host RoundPushPin?","Yes. RoundPushPin is self-hosted, built with TypeScript end to end, so you can run it on your own infrastructure and own your data.","/images/knowledge/building-better-forms.png",{},"/knowledge/building-better-forms","conversational-form-design","Conversational form design",{"title":142,"description":288},[306,307],{"title":129,"url":130,"publisher":131},{"title":308,"url":126,"publisher":127},"Galesic, M. & Bosnjak, M. (2009) — Effects of questionnaire length on participation and response quality","knowledge/building-better-forms",[311,312],"product","vision",[],"ZaP-Ua9nq9rSM2PVDqRGSDwZJqhOKm3tSDgefhD4ovk",{"id":316,"title":317,"author":6,"body":318,"date":430,"description":431,"draft":105,"extension":106,"faqs":432,"image":441,"isPillar":105,"meta":442,"navigation":118,"path":443,"pillar":302,"pillarName":303,"seo":444,"sources":445,"stem":454,"tags":455,"takeaways":459,"updated":430,"__hash__":463},"knowledge/knowledge/form-completion-rate.md","How to Improve Form Completion Rate (What the Research Says)",{"type":8,"value":319,"toc":423},[320,323,330,334,340,344,357,361,367,371,374,405,409],[11,321,322],{},"Form completion rate is the percentage of people who finish a form out of everyone who starts it. It is the single most important number for any form, and the research on what improves it is remarkably consistent: reduce length, reduce effort, and only ask what's relevant.",[11,324,325],{},[326,327],"img",{"alt":328,"src":329},"Funnel diagram showing form completion leaking from \"Form viewed\" down to \"Completed\" as drop-off grows with each step","/images/knowledge/diagrams/completion-funnel.png",[15,331,333],{"id":332},"what-is-a-good-form-completion-rate","What is a good form completion rate?",[11,335,336,339],{},[22,337,338],{},"There is no universal benchmark — it depends on audience, intent, and how much you ask — so the useful comparison is your form against itself over time."," Track starts, completions, and where people drop off, then change one thing and measure. Absolute numbers from other companies' forms are rarely comparable to yours.",[15,341,343],{"id":342},"does-form-length-really-reduce-completion","Does form length really reduce completion?",[11,345,346,349,350,352,353,356],{},[22,347,348],{},"Yes — this is one of the best-supported findings in survey methodology."," In a controlled web-survey experiment, Galesic and Bosnjak (2009) found that longer stated questionnaire length lowered participation ",[37,351,93],{}," degraded response quality in the later questions. Peytchev (2009) studied ",[37,354,355],{},"breakoff"," — people abandoning partway — and tied it to respondent burden. Every additional question is a chance to lose someone.",[15,358,360],{"id":359},"how-much-does-cutting-fields-help","How much does cutting fields help?",[11,362,363,366],{},[22,364,365],{},"Enough that it's the highest-leverage change you can usually make."," Baymard Institute's research on checkout flows found the average checkout asks 11.3 form fields when around 8 are actually needed. The lesson generalizes: audit every field and delete or defer anything you don't truly need at that moment.",[15,368,370],{"id":369},"what-actually-moves-completion-rate","What actually moves completion rate?",[11,372,373],{},"The evidence points to a short list:",[252,375,376,382,388,397],{},[52,377,378,381],{},[22,379,380],{},"Ask fewer questions."," Cut optional fields; collect the rest later. (Galesic & Bosnjak, 2009)",[52,383,384,387],{},[22,385,386],{},"Lower perceived effort."," One question at a time and a visible sense of progress reduce the burden that drives breakoff (Peytchev, 2009).",[52,389,390,393,394,396],{},[22,391,392],{},"Only ask what's relevant."," Use ",[65,395,68],{"href":67}," so no one answers questions that don't apply to them.",[52,398,399,402,403,187],{},[22,400,401],{},"Ask clearly."," Confusing questions cause hesitation and drop-off — see ",[65,404,79],{"href":78},[15,406,408],{"id":407},"how-roundpushpin-helps","How RoundPushPin helps",[11,410,411,418,419,187],{},[22,412,413,414,417],{},"RoundPushPin's ",[65,415,416],{"href":120},"conversational design"," lowers perceived effort by asking one question at a time, and its conditional logic shows only relevant questions — both of which target the exact factors the research links to completion."," And because responses are stored relationally, you can measure completion and drop-off per question ",[65,420,422],{"href":421},"/knowledge/query-form-data-with-sql","directly in SQL",{"title":96,"searchDepth":97,"depth":97,"links":424},[425,426,427,428,429],{"id":332,"depth":97,"text":333},{"id":342,"depth":97,"text":343},{"id":359,"depth":97,"text":360},{"id":369,"depth":97,"text":370},{"id":407,"depth":97,"text":408},"2026-02-14","Form completion rate is the share of people who finish a form they started. This evidence-based guide covers what survey-methodology and UX research show actually moves it: fewer questions, lower perceived effort, and relevant questions only.",[433,435,438],{"q":333,"a":434},"There's no universal benchmark — it varies by audience, intent, and length — so compare your form against itself over time rather than to others. Track starts, completions, and per-question drop-off.",{"q":436,"a":437},"Does reducing the number of form fields increase conversions?","Usually yes. Research links longer forms to lower completion, and Baymard found typical checkouts ask about 11 fields when around 8 suffice. Cutting unnecessary fields is often the single highest-leverage change.",{"q":439,"a":440},"Why do people abandon forms?","Mostly effort: too many questions, irrelevant fields, unclear wording, and no sense of progress. Survey research ties 'breakoff' to respondent burden, so lowering effort is the core fix.","/images/knowledge/form-completion-rate.png",{},"/knowledge/form-completion-rate",{"title":317,"description":431},[446,447,450],{"title":125,"url":126,"publisher":127},{"title":448,"url":449,"publisher":127},"Peytchev, A. (2009) — Survey breakoff","https://doi.org/10.1093/poq/nfp014",{"title":451,"url":452,"publisher":453},"Checkout flows have an average of 11.3 form fields","https://baymard.com/blog/checkout-flow-average-form-fields","Baymard Institute","knowledge/form-completion-rate",[456,457,458],"conversion","completion rate","research",[460,461,462],"Completion rate = finishers ÷ starters; compare your form against itself over time, not to others.","Length is the biggest lever — research links longer forms to lower completion and quality.","Cut fields, lower perceived effort, show only relevant questions, and ask clearly.","tavcEKYHSA8KbRqa1bK_h3nWX27ArfLqaWy9OF2vE-Q",{"id":465,"title":466,"author":6,"body":467,"date":565,"description":566,"draft":105,"extension":106,"faqs":567,"image":577,"isPillar":105,"meta":578,"navigation":118,"path":78,"pillar":302,"pillarName":303,"seo":579,"sources":580,"stem":593,"tags":594,"takeaways":596,"updated":565,"__hash__":597},"knowledge/knowledge/how-to-ask-the-right-questions-in-a-form.md","How to Ask the Right Questions in a Form",{"type":8,"value":468,"toc":559},[469,472,476,482,486,493,497,500,538,542],[11,470,471],{},"Asking the right questions in a form means writing each question so that everyone interprets it the same way, can answer it with reasonable effort, and gives you data you can actually use. Decades of survey-methodology research show that the wording, format, and order of questions change the answers you get — so question design is a measurement decision, not a cosmetic one.",[15,473,475],{"id":474},"why-does-the-way-you-ask-a-question-matter-so-much","Why does the way you ask a question matter so much?",[11,477,478,481],{},[22,479,480],{},"Because respondents construct answers from the question itself."," Schwarz (1999) showed that small changes in wording, response options, and context systematically shape the answers people give — the question is part of the measurement, not a neutral wrapper. Tourangeau, Rips, and Rasinski (2000) model answering as four cognitive steps — comprehension, retrieval, judgment, and response — and a question can break down at any of them.",[15,483,485],{"id":484},"what-makes-people-give-low-quality-answers","What makes people give low-quality answers?",[11,487,488,489,492],{},"Effort. Krosnick (1991) described ",[37,490,491],{},"satisficing",": when a question is hard or a form is long, respondents stop giving their best answer and instead pick the easiest acceptable one — choosing the first reasonable option, agreeing by default, or selecting \"don't know.\" The fix is to lower the effort each question demands, not to demand more diligence from the respondent.",[15,494,496],{"id":495},"what-are-the-practical-rules-for-writing-form-questions","What are the practical rules for writing form questions?",[11,498,499],{},"The research converges on a short, durable list:",[252,501,502,508,514,520,526,532],{},[52,503,504,507],{},[22,505,506],{},"Ask one thing per question."," Split double-barreled questions (\"How satisfied are you with speed and support?\") into two.",[52,509,510,513],{},[22,511,512],{},"Use plain, concrete language."," Avoid jargon, negations, and vague quantifiers (\"often\", \"regularly\").",[52,515,516,519],{},[22,517,518],{},"Make response options balanced and exhaustive."," Offer a clear scale and a genuine escape (\"Not applicable\") so people don't satisfice into a wrong answer.",[52,521,522,525],{},[22,523,524],{},"Prefer closed questions for data you'll analyze;"," reserve open text for genuine nuance, since open answers cost more effort and are harder to compare.",[52,527,528,531],{},[22,529,530],{},"Mind order and context."," Earlier questions frame later ones (Schwarz, 1999); ask general before specific, and don't let one question bias the next.",[52,533,534,537],{},[22,535,536],{},"Only ask what you'll use."," Every question is effort that risks drop-off — relevance is part of good question design.",[15,539,541],{"id":540},"how-does-this-connect-to-completion","How does this connect to completion?",[11,543,544,551,552,555,556,187],{},[22,545,546,547,550],{},"Clear, low-effort questions don't just produce better data — they reduce the hesitation and burden that drive abandonment, which is why question quality and ",[65,548,549],{"href":443},"form completion rate"," move together."," RoundPushPin pairs these question-design principles with ",[65,553,554],{"href":120},"conversational, one-at-a-time delivery"," and typed storage, so good questions also produce clean, ",[65,557,558],{"href":421},"queryable data",{"title":96,"searchDepth":97,"depth":97,"links":560},[561,562,563,564],{"id":474,"depth":97,"text":475},{"id":484,"depth":97,"text":485},{"id":495,"depth":97,"text":496},{"id":540,"depth":97,"text":541},"2026-02-16","The wording and order of your questions shape the answers you get — and whether people finish at all. This research-backed guide distills decades of survey methodology into practical rules for writing form questions.",[568,571,574],{"q":569,"a":570},"What makes a good form question?","It asks one thing, in plain concrete language, with balanced and exhaustive answer options. Good questions are interpreted the same way by everyone and can be answered with low effort.",{"q":572,"a":573},"Should I use open-ended or multiple-choice questions?","Use closed (multiple-choice) questions for anything you'll analyze — they're faster to answer and easier to compare. Reserve open text for genuine nuance, since it costs more effort and invites shortcutting.",{"q":575,"a":576},"Does question wording affect the answers people give?","Yes. Research shows wording, response options, and order systematically shape answers — the question is part of the measurement. Ask general before specific and avoid leading phrasing.","/images/knowledge/how-to-ask-the-right-questions-in-a-form.png",{},{"title":466,"description":566},[581,585,589],{"title":582,"url":583,"publisher":584},"Schwarz, N. (1999) — Self-reports: How the questions shape the answers","https://doi.org/10.1037/0003-066X.54.2.93","American Psychologist",{"title":586,"url":587,"publisher":588},"Krosnick, J. A. (1991) — Response strategies for coping with the cognitive demands of attitude measures in surveys","https://doi.org/10.1002/acp.2350050305","Applied Cognitive Psychology",{"title":590,"url":591,"publisher":592},"Tourangeau, R., Rips, L. J., & Rasinski, K. (2000) — The Psychology of Survey Response","https://doi.org/10.1017/CBO9780511819322","Cambridge University Press","knowledge/how-to-ask-the-right-questions-in-a-form",[595,135,458],"question design",[],"HIEGdx8r65NlxYASsg8N80CMjzRFLezd3XLsgzvoIeo",{"id":599,"title":600,"author":6,"body":601,"date":670,"description":671,"draft":105,"extension":106,"faqs":672,"image":680,"isPillar":105,"meta":681,"navigation":118,"path":67,"pillar":302,"pillarName":303,"seo":682,"sources":683,"stem":686,"tags":687,"takeaways":689,"updated":670,"__hash__":690},"knowledge/knowledge/conditional-logic-in-forms.md","Conditional Logic and Skip Logic in Forms",{"type":8,"value":602,"toc":664},[603,606,610,620,624,633,637,651,655],[11,604,605],{},"Conditional logic — also called skip logic or branching — shows, hides, or reorders questions based on what a respondent has already answered. It is how a form adapts to each person so they only ever see questions that apply to them.",[15,607,609],{"id":608},"what-is-skip-logic-in-a-form","What is skip logic in a form?",[11,611,612,615,616,619],{},[22,613,614],{},"Skip logic is a rule that changes the path through a form based on an answer."," \"If the respondent selects ",[37,617,618],{},"No",", skip the three follow-up questions\" is skip logic; so is routing enterprise and individual users down different branches. Instead of one rigid sequence, the form becomes a set of paths, and each respondent travels only the relevant one.",[15,621,623],{"id":622},"why-use-conditional-logic","Why use conditional logic?",[11,625,626,629,630,632],{},[22,627,628],{},"Because relevance reduces length, and length drives abandonment."," Showing only applicable questions is ",[37,631,39],{}," — a long-standing UX principle for cutting cognitive load (Nielsen Norman Group) — and shorter, more relevant paths align with the finding that questionnaire length lowers participation and response quality (Galesic & Bosnjak, 2009). Conditional logic lets a form be comprehensive for the few without being long for everyone.",[15,634,636],{"id":635},"whats-the-difference-between-skip-logic-and-branching","What's the difference between skip logic and branching?",[11,638,639,650],{},[22,640,641,642,645,646,649],{},"They're the same idea at different scales. ",[37,643,644],{},"Skip logic"," usually means jumping over individual questions; ",[37,647,648],{},"branching"," means whole alternative sections or paths."," Both are conditional logic — rules connecting an answer to what comes next.",[15,652,654],{"id":653},"how-roundpushpin-models-conditional-logic","How RoundPushPin models conditional logic",[11,656,657,660,661,663],{},[22,658,659],{},"RoundPushPin represents logic as a visual graph of edges between questions rather than tangled nested rules."," You draw the paths — this answer leads here, that answer leads there — and the renderer evaluates the edges as the respondent moves through the form. The result is comprehensive forms that still feel short, which is exactly what ",[65,662,457],{"href":443}," rewards.",{"title":96,"searchDepth":97,"depth":97,"links":665},[666,667,668,669],{"id":608,"depth":97,"text":609},{"id":622,"depth":97,"text":623},{"id":635,"depth":97,"text":636},{"id":653,"depth":97,"text":654},"2026-02-18","Conditional logic shows or hides questions based on previous answers, so each respondent only sees what's relevant. This guide explains skip logic, branching, and how RoundPushPin models it as a visual graph.",[673,675,678],{"q":609,"a":674},"Skip logic is a rule that changes the path through a form based on an answer — for example, skipping follow-up questions when someone answers 'No'. The form becomes a set of paths, and each respondent travels only the relevant one.",{"q":676,"a":677},"Does conditional logic improve completion?","Generally yes, because it hides irrelevant questions and shortens each respondent's path, and survey research links shorter, lower-burden forms to higher completion. It lets a form be thorough for the few without being long for everyone.",{"q":636,"a":679},"They're the same idea at different scales: skip logic usually jumps over individual questions, while branching routes respondents down whole alternative sections. Both connect an answer to what comes next.","/images/knowledge/conditional-logic-in-forms.png",{},{"title":600,"description":671},[684,685],{"title":129,"url":130,"publisher":131},{"title":308,"url":126,"publisher":127},"knowledge/conditional-logic-in-forms",[688,648,135],"skip logic",[],"Ufo2TZpfqD-PimyDABjq9SpoJlF48eGm8i9EBc8KQ78",{"id":692,"title":693,"author":6,"body":694,"date":840,"description":841,"draft":105,"extension":106,"faqs":842,"image":852,"isPillar":105,"meta":853,"navigation":118,"path":854,"pillar":302,"pillarName":303,"seo":855,"sources":856,"stem":859,"tags":860,"takeaways":862,"updated":840,"__hash__":863},"knowledge/knowledge/question-types-explained.md","Form Question Types, Explained",{"type":8,"value":695,"toc":834},[696,699,703,706,732,736,745,811,815,821,825],[11,697,698],{},"A form question type is the input format a question uses — short text, long text, multiple choice, dropdown, rating, opinion scale, yes/no, date, file upload — and it determines both the effort a respondent spends and the shape of the data you get back. Choosing the right type is part of asking the right question.",[15,700,702],{"id":701},"what-are-the-main-form-question-types","What are the main form question types?",[11,704,705],{},"They fall into a few families:",[49,707,708,714,720,726],{},[52,709,710,713],{},[22,711,712],{},"Text"," — short text, long text, email, URL, phone, number. Flexible, but open text is costly to answer and to analyze.",[52,715,716,719],{},[22,717,718],{},"Selection"," — multiple choice, dropdown, radio, yes/no. Fast to answer and easy to analyze because answers are constrained.",[52,721,722,725],{},[22,723,724],{},"Scale"," — rating and opinion scales for measuring degree or sentiment.",[52,727,728,731],{},[22,729,730],{},"Special"," — date, file upload, and display-only statements.",[15,733,735],{"id":734},"when-should-you-use-open-text-vs-multiple-choice","When should you use open text vs multiple choice?",[11,737,738,741,742,744],{},[22,739,740],{},"Use closed (selection) questions for anything you'll analyze, and reserve open text for genuine nuance."," Open questions demand more effort, which invites ",[37,743,491],{}," — respondents taking shortcuts when a question is burdensome (Krosnick, 1991) — and the free-text answers are far harder to compare. A well-built set of choices usually yields cleaner, more analyzable data than an open box.",[746,747,748,764],"table",{},[749,750,751],"thead",{},[752,753,754,758,761],"tr",{},[755,756,757],"th",{},"Aspect",[755,759,760],{},"Open text",[755,762,763],{},"Multiple choice",[765,766,767,779,790,800],"tbody",{},[752,768,769,773,776],{},[770,771,772],"td",{},"Effort to answer",[770,774,775],{},"Higher",[770,777,778],{},"Lower",[752,780,781,784,787],{},[770,782,783],{},"Ease of analysis",[770,785,786],{},"Hard (free text)",[770,788,789],{},"Easy (constrained values)",[752,791,792,795,798],{},[770,793,794],{},"Risk of satisficing",[770,796,797],{},"Higher on long forms",[770,799,778],{},[752,801,802,805,808],{},[770,803,804],{},"Best for",[770,806,807],{},"Genuine nuance, unknowns",[770,809,810],{},"Anything you'll measure",[15,812,814],{"id":813},"do-rating-scales-need-care","Do rating scales need care?",[11,816,817,820],{},[22,818,819],{},"Yes — the scale you offer shapes the answer."," Schwarz (1999) showed that the range and labeling of response options change how people respond, so use a consistent number of points, label them clearly, and keep scales balanced. An unbalanced or vague scale measures your design as much as the respondent's opinion.",[15,822,824],{"id":823},"how-question-type-connects-to-your-data","How question type connects to your data",[11,826,827,830,831,833],{},[22,828,829],{},"Because RoundPushPin maps each question to a typed database column, the question type you choose becomes the column's type — a rating is an integer, a date is a timestamp, a yes/no is a boolean."," That means the right type produces clean, ",[65,832,558],{"href":421}," automatically, with no parsing after the fact.",{"title":96,"searchDepth":97,"depth":97,"links":835},[836,837,838,839],{"id":701,"depth":97,"text":702},{"id":734,"depth":97,"text":735},{"id":813,"depth":97,"text":814},{"id":823,"depth":97,"text":824},"2026-02-20","Short text, multiple choice, rating scales, dates, file uploads — each question type collects a different kind of data. This guide explains when to use each and how the type you pick affects answer quality and analysis.",[843,846,849],{"q":844,"a":845},"What are the main types of form questions?","They group into text (short/long, email, number), selection (multiple choice, dropdown, radio, yes/no), scale (rating, opinion), and special (date, file upload, statements). Selection and scale types are easiest to analyze.",{"q":847,"a":848},"When should I use a dropdown vs radio buttons?","Use radio buttons for a few mutually exclusive options the user should see at once; use a dropdown to save space when there are many options. Both store a single constrained value, which keeps analysis clean.",{"q":850,"a":851},"Are rating scales reliable?","They can be, if designed carefully: keep a consistent number of points, label them clearly, and keep the scale balanced. Research shows the range and labeling of options shape the answers, so scale design is part of measurement.","/images/knowledge/question-types-explained.png",{},"/knowledge/question-types-explained",{"title":693,"description":841},[857,858],{"title":586,"url":587,"publisher":588},{"title":582,"url":583,"publisher":584},"knowledge/question-types-explained",[861,134],"question types",[],"aEoTRuziAA3Wr8b9jGMGzdUl9_KafNRMahwZwwdQtIw",{"id":865,"title":866,"author":6,"body":867,"date":1002,"description":1003,"draft":105,"extension":106,"faqs":1004,"image":1014,"isPillar":105,"meta":1015,"navigation":118,"path":1016,"pillar":302,"pillarName":303,"seo":1017,"sources":1018,"stem":1026,"tags":1027,"takeaways":1030,"updated":1002,"__hash__":1034},"knowledge/knowledge/ab-testing-forms.md","How to A/B Test Forms (and Read the Results)",{"type":8,"value":868,"toc":995},[869,872,878,882,888,892,898,936,943,947,961,965,971,975],[11,870,871],{},"A/B testing a form means showing two versions of it to comparable, randomly assigned groups and measuring which one performs better — usually on completion rate. Done properly it tells you what actually works instead of what you assume works; done sloppily it produces confident, wrong conclusions.",[11,873,874],{},[326,875],{"alt":876,"src":877},"Diagram of A/B testing a form: incoming traffic split into branch A and branch B, then measuring completion to pick the winner","/images/knowledge/diagrams/ab-branches.png",[15,879,881],{"id":880},"can-you-ab-test-a-form","Can you A/B test a form?",[11,883,884,887],{},[22,885,886],{},"Yes — a form is well suited to A/B testing because it has a clear, measurable outcome: did the person finish it."," You split incoming respondents randomly between version A and version B, keep everything else equal, and compare completion. Random assignment is the core idea from controlled experiments (Kohavi, Tang & Xu, 2020): it's what lets you credit the difference to your change rather than to chance or to who happened to see which version.",[15,889,891],{"id":890},"what-should-you-ab-test-on-a-form","What should you A/B test on a form?",[11,893,894,897],{},[22,895,896],{},"Test one meaningful change at a time, so you can attribute any difference to it."," High-leverage things to test on a form:",[252,899,900,906,916,925,931],{},[52,901,902,905],{},[22,903,904],{},"Length"," — fewer fields vs more (the change most likely to move completion).",[52,907,908,911,912,915],{},[22,909,910],{},"One question at a time vs all-on-one-page"," — the ",[65,913,914],{"href":120},"conversational format"," vs a classic layout.",[52,917,918,921,922,187],{},[22,919,920],{},"Question wording"," — since ",[65,923,924],{"href":78},"wording shapes answers and effort",[52,926,927,930],{},[22,928,929],{},"Question order"," — front-loading easy questions vs sensitive ones.",[52,932,933],{},[22,934,935],{},"The call to action and intro copy.",[11,937,938,939,942],{},"Changing several things at once is fine for shipping, but then you won't know ",[37,940,941],{},"which"," change caused the result.",[15,944,946],{"id":945},"how-do-you-read-ab-test-results","How do you read A/B test results?",[11,948,949,952,953,956,957,960],{},[22,950,951],{},"Compare the primary metric between variants and ask whether the difference is real or noise — using a significance test, not eyeballing."," Compute completion rate for each variant and a confidence interval or p-value; a gap that isn't statistically significant is not yet a result. The most common mistake is ",[37,954,955],{},"peeking"," — repeatedly checking and stopping the moment it looks significant — which dramatically inflates false positives (Evan Miller, \"How Not to Run an A/B Test\"). Decide your metric and stopping rule before you start, and read per-question drop-off too, so you can see ",[37,958,959],{},"where"," a variant helped or hurt.",[15,962,964],{"id":963},"how-long-should-you-run-a-form-ab-test","How long should you run a form A/B test?",[11,966,967,970],{},[22,968,969],{},"Long enough to reach the sample size you set in advance, and across full business cycles — not until it looks good."," Estimate the sample with a power calculation based on your baseline completion rate and the smallest improvement worth detecting; smaller effects need much larger samples. Run for whole weeks to avoid day-of-week bias, and avoid stopping early on an exciting-but-underpowered result.",[15,972,974],{"id":973},"how-roundpushpin-helps-you-test-and-read-forms","How RoundPushPin helps you test and read forms",[11,976,977,980,981,984,985,989,990,994],{},[22,978,979],{},"Because RoundPushPin stores responses relationally, the metrics an A/B test needs are already in the data — no tracking project required."," Completion rate and per-question drop-off come straight from the database with a ",[65,982,983],{"href":421},"SQL query",", and because you can run ",[65,986,988],{"href":987},"/knowledge/one-template-many-versions","one master template in many versions",", standing up an A and a B variant is quick — see ",[65,991,993],{"href":992},"/features/ab-testing","RoundPushPin's A/B testing feature",". Structured data is what turns a form test from guesswork into a measurable experiment.",{"title":96,"searchDepth":97,"depth":97,"links":996},[997,998,999,1000,1001],{"id":880,"depth":97,"text":881},{"id":890,"depth":97,"text":891},{"id":945,"depth":97,"text":946},{"id":963,"depth":97,"text":964},{"id":973,"depth":97,"text":974},"2026-03-08","A/B testing a form means showing two versions to comparable groups and measuring which converts better. This guide covers what to test, how to read the data without fooling yourself, and how long to run a test.",[1005,1008,1011],{"q":1006,"a":1007},"What is A/B testing for forms?","It's a controlled experiment: visitors are split randomly between two versions of a form, and you compare a metric — usually completion rate — to see which performs better. Random assignment is what lets you attribute the difference to the change rather than to chance or audience.",{"q":1009,"a":1010},"How big a sample do I need to A/B test a form?","Enough to detect the effect size you care about — smaller expected improvements need larger samples. Decide the sample size before you start using a calculator, and don't stop early just because a result looks significant; peeking inflates false positives.",{"q":1012,"a":1013},"What metric should I track for a form A/B test?","Usually completion rate (finishers ÷ starters), plus per-question drop-off to see where a variant helps or hurts. Pick one primary metric before the test so you're not cherry-picking afterward.","/images/knowledge/ab-testing-forms.png",{},"/knowledge/ab-testing-forms",{"title":866,"description":1003},[1019,1022],{"title":1020,"url":1021,"publisher":592},"Kohavi, R., Tang, D., & Xu, Y. (2020) — Trustworthy Online Controlled Experiments: A Practical Guide to A/B Testing","https://doi.org/10.1017/9781108653985",{"title":1023,"url":1024,"publisher":1025},"Evan Miller — How Not to Run an A/B Test","https://www.evanmiller.org/how-not-to-run-an-ab-test.html","Evan Miller","knowledge/ab-testing-forms",[1028,456,1029],"a/b testing","analytics",[1031,1032,1033],"A/B testing splits the same traffic randomly between two or more form branches and compares completion.","Read results with a significance test and a sample size set in advance — never stop early on a peek.","Because RoundPushPin stores responses relationally, completion and drop-off come straight from your data.","gaHsci9_Oq3iPyBAVOygobW9R42nO8j_fdmxhPWoR-s",{"id":1036,"title":1037,"author":6,"body":1038,"date":1120,"description":1121,"draft":105,"extension":106,"faqs":1122,"image":1132,"isPillar":105,"meta":1133,"navigation":118,"path":1134,"pillar":302,"pillarName":303,"seo":1135,"sources":1136,"stem":1140,"tags":1141,"takeaways":1144,"updated":1120,"__hash__":1148},"knowledge/knowledge/lead-generation-forms.md","How to Design a Form That Generates Leads",{"type":8,"value":1039,"toc":1113},[1040,1043,1047,1056,1060,1070,1074,1086,1090,1096,1100],[11,1041,1042],{},"A lead-generation form turns interest into a contactable, qualified lead — but only if people finish it. The design decision that matters most isn't the colour of the button; it's how much effort you ask for before someone has any reason to trust you.",[15,1044,1046],{"id":1045},"what-makes-a-lead-generation-form-convert","What makes a lead-generation form convert?",[11,1048,1049,1052,1053,1055],{},[22,1050,1051],{},"Low effort and high relevance."," People weigh the effort of filling in a form against what they get for it, and abandon when the effort feels too high. Survey research is consistent here: longer forms reduce participation and response quality (Galesic & Bosnjak, 2009), and abandonment — ",[37,1054,355],{}," — tracks respondent burden (Peytchev, 2009). A converting lead form keeps the ask small and the value obvious.",[15,1057,1059],{"id":1058},"how-many-fields-should-a-lead-form-have","How many fields should a lead form have?",[11,1061,1062,1065,1066,1069],{},[22,1063,1064],{},"As few as you can actually act on — often an email plus one or two qualifiers."," Baymard Institute found the average checkout asks 11.3 fields when around 8 suffice; lead forms suffer the same bloat. Every extra field is another reason to leave, so drop anything you won't use to route, qualify, or follow up. If you can't name what a field is ",[37,1067,1068],{},"for",", cut it.",[15,1071,1073],{"id":1072},"should-a-lead-form-be-conversational","Should a lead form be conversational?",[11,1075,1076,1079,1080,1082,1083,1085],{},[22,1077,1078],{},"Often yes — asking one question at a time lowers the perceived effort that drives abandonment."," A ",[65,1081,914],{"href":120}," makes a multi-field form feel like a series of small, easy steps rather than a wall, which is exactly the burden the research links to completion. Pair it with ",[65,1084,68],{"href":67}," so each person only sees the fields relevant to them.",[15,1087,1089],{"id":1088},"how-do-you-capture-more-information-without-losing-leads","How do you capture more information without losing leads?",[11,1091,1092,1095],{},[22,1093,1094],{},"Use progressive profiling — ask the minimum now, request more later."," Capture an email and one qualifier on the first form, then ask follow-up questions on a later visit or step, once the person is already engaged. You get a short first form (high completion) and a complete profile over time, instead of trading one for the other.",[15,1097,1099],{"id":1098},"how-roundpushpin-helps-you-generate-leads","How RoundPushPin helps you generate leads",[11,1101,1102,1105,1106,1109,1110,1112],{},[22,1103,1104],{},"RoundPushPin's conversational design lifts completion, and because responses are stored relationally you can see exactly where leads drop off."," You can A/B test a shorter form against a longer one and read the winner from the data (see ",[65,1107,1108],{"href":1016},"A/B testing forms","), measure ",[65,1111,457],{"href":443}," per question, and keep every lead in one queryable place ready for your CRM.",{"title":96,"searchDepth":97,"depth":97,"links":1114},[1115,1116,1117,1118,1119],{"id":1045,"depth":97,"text":1046},{"id":1058,"depth":97,"text":1059},{"id":1072,"depth":97,"text":1073},{"id":1088,"depth":97,"text":1089},{"id":1098,"depth":97,"text":1099},"2026-03-10","A lead-generation form only works if people finish it. This evidence-based guide covers what actually drives lead form conversion — fewer fields, lower effort, and asking for commitment in the right order.",[1123,1126,1129],{"q":1124,"a":1125},"How many fields should a lead generation form have?","As few as you can act on — usually an email plus one or two qualifiers. Research links longer forms to lower completion, and Baymard found most forms ask more fields than they need. Collect the rest later.",{"q":1127,"a":1128},"Do shorter forms always generate more leads?","Shorter forms usually lift completion, but the goal is qualified leads, not just volume. Cut fields you don't act on; keep the one or two that route or qualify the lead, and gather the rest after the first conversion.",{"q":1130,"a":1131},"What's the best way to ask for more information without losing leads?","Progressive profiling: ask the minimum up front, then request more on later visits or steps once the person is already engaged. It keeps the first form short while still building a full profile over time.","/images/knowledge/lead-generation-forms.png",{},"/knowledge/lead-generation-forms",{"title":1037,"description":1121},[1137,1138,1139],{"title":125,"url":126,"publisher":127},{"title":448,"url":449,"publisher":127},{"title":451,"url":452,"publisher":453},"knowledge/lead-generation-forms",[1142,456,1143,458],"lead generation","marketing",[1145,1146,1147],"A lead form only generates leads if people finish it — completion is the constraint, not the form's looks.","Fewer fields and lower effort raise completion; research ties form length to drop-off.","Ask only what you'll act on now; collect the rest later with progressive profiling.","ra3EWzgpGm6eU4kPpp6ZlgTDUS68CHplk5wqELupV2Y",{"id":1150,"title":1151,"author":6,"body":1152,"date":1268,"description":1269,"draft":105,"extension":106,"faqs":1270,"image":1278,"isPillar":105,"meta":1279,"navigation":118,"path":1280,"pillar":302,"pillarName":303,"seo":1281,"sources":1282,"stem":1286,"tags":1287,"takeaways":1289,"updated":1268,"__hash__":1293},"knowledge/knowledge/form-friction.md","Form Friction: What Causes It and How to Reduce It",{"type":8,"value":1153,"toc":1261},[1154,1157,1161,1167,1171,1181,1185,1190,1231,1235,1245,1249],[11,1155,1156],{},"Form friction is the sum of everything that stands between a respondent and the submit button — every extra field, moment of confusion, or irrelevant question that makes finishing feel like work. Reduce it and more people complete; ignore it and they leave.",[15,1158,1160],{"id":1159},"what-is-form-friction","What is form friction?",[11,1162,1163,1166],{},[22,1164,1165],{},"Form friction is any effort or hesitation a form imposes on its way to \"submit\"."," It's the cognitive and physical cost of answering — reading, deciding, typing, recovering from errors — plus the doubt a confusing or intrusive question creates. Friction isn't one thing; it's the accumulation of small costs, and each one is a chance to lose someone.",[15,1168,1170],{"id":1169},"what-causes-friction-in-forms","What causes friction in forms?",[11,1172,1173,1176,1177,1180],{},[22,1174,1175],{},"Mostly length and cognitive load, then irrelevance and confusion."," Longer forms reduce participation and response quality (Galesic & Bosnjak, 2009), and when a question is burdensome people ",[37,1178,1179],{},"satisfice"," — taking mental shortcuts or abandoning rather than answering well (Krosnick, 1991). On top of that: fields that don't apply, vague or double-barrelled wording, and unclear error messages each add friction.",[15,1182,1184],{"id":1183},"how-do-you-reduce-form-friction","How do you reduce form friction?",[11,1186,1187],{},[22,1188,1189],{},"Remove reasons to stop, one at a time:",[252,1191,1192,1198,1209,1217,1225],{},[52,1193,1194,1197],{},[22,1195,1196],{},"Ask fewer questions"," — cut anything you won't act on.",[52,1199,1200,911,1203,1205,1206,1208],{},[22,1201,1202],{},"Show one question at a time",[65,1204,914],{"href":120}," is ",[37,1207,39],{},", a long-standing way to cut cognitive load (Nielsen Norman Group).",[52,1210,1211,1214,1215,187],{},[22,1212,1213],{},"Hide irrelevant fields"," with ",[65,1216,68],{"href":67},[52,1218,1219,1222,1223,187],{},[22,1220,1221],{},"Phrase questions plainly"," — see ",[65,1224,79],{"href":78},[52,1226,1227,1230],{},[22,1228,1229],{},"Make errors recoverable"," — clear, inline, specific.",[15,1232,1234],{"id":1233},"does-removing-friction-hurt-your-data","Does removing friction hurt your data?",[11,1236,1237,1240,1241,1244],{},[22,1238,1239],{},"No — lower friction usually improves data, because burdened respondents satisfice."," Krosnick (1991) showed that high effort pushes people toward low-quality shortcut answers, so reducing burden tends to raise answer quality, not lower it. The exception is removing a genuinely necessary question — friction reduction means cutting the ",[37,1242,1243],{},"unnecessary",", not the important.",[15,1246,1248],{"id":1247},"how-roundpushpin-reduces-form-friction","How RoundPushPin reduces form friction",[11,1250,1251,1254,1255,1257,1258,1260],{},[22,1252,1253],{},"RoundPushPin is built to keep friction low: one question at a time, relevant fields only, and clean validation — with the data still fully structured underneath."," Conversational delivery and graph-based ",[65,1256,68],{"href":67}," cut the length and irrelevance that drive abandonment, and you can measure the payoff in ",[65,1259,457],{"href":443}," straight from your data.",{"title":96,"searchDepth":97,"depth":97,"links":1262},[1263,1264,1265,1266,1267],{"id":1159,"depth":97,"text":1160},{"id":1169,"depth":97,"text":1170},{"id":1183,"depth":97,"text":1184},{"id":1233,"depth":97,"text":1234},{"id":1247,"depth":97,"text":1248},"2026-03-12","Form friction is the effort and hesitation between a respondent and 'submit'. This research-backed guide breaks down what causes friction — length, cognitive load, irrelevant and unclear questions — and how to cut it.",[1271,1273,1276],{"q":1160,"a":1272},"Form friction is anything that raises the effort or hesitation between a respondent and submitting — too many fields, confusing questions, irrelevant steps, unclear errors, or a layout that feels long. More friction means more abandonment.",{"q":1274,"a":1275},"What causes the most form friction?","Length and cognitive load. Research links longer forms to lower completion and quality, and burdensome questions push people to take shortcuts or quit. Irrelevant fields, vague wording, and poor error handling add more.",{"q":1184,"a":1277},"Ask fewer questions, show one at a time, hide irrelevant fields with conditional logic, phrase questions plainly, and give clear inline error recovery. Each removes a reason to hesitate or leave.","/images/knowledge/form-friction.png",{},"/knowledge/form-friction",{"title":1151,"description":1269},[1283,1284,1285],{"title":586,"url":587,"publisher":588},{"title":308,"url":126,"publisher":127},{"title":129,"url":130,"publisher":131},"knowledge/form-friction",[1288,135,456,458],"friction",[1290,1291,1292],"Form friction is the effort and hesitation between a respondent and 'submit' — and it drives abandonment.","The biggest sources are length and cognitive load; irrelevant fields, vague wording, and bad errors add more.","Cut friction by asking less, one question at a time, with relevant fields, plain wording, and clear errors.","ejJmvZfkmuywxW7gFZeCCJ_4RTkOxIw2UC_A0zHbkHE",{"id":1295,"title":1296,"author":6,"body":1297,"date":1383,"description":1384,"draft":105,"extension":106,"faqs":1385,"image":1394,"isPillar":105,"meta":1395,"navigation":118,"path":1396,"pillar":302,"pillarName":303,"seo":1397,"sources":1398,"stem":1408,"tags":1409,"takeaways":1411,"updated":1383,"__hash__":1415},"knowledge/knowledge/what-to-ask-on-a-form.md","What to Ask (and Not Ask) on a Form",{"type":8,"value":1298,"toc":1376},[1299,1302,1306,1318,1322,1328,1332,1346,1350,1359,1363],[11,1300,1301],{},"Every field on a form is a trade: more data for you, more effort and more drop-off for the respondent — and, for personal data, more legal exposure. Deciding what to ask, and what to leave off, is one of the highest-leverage choices in form design.",[15,1303,1305],{"id":1304},"how-do-you-decide-which-fields-to-include","How do you decide which fields to include?",[11,1307,1308,1311,1312,1315,1316,187],{},[22,1309,1310],{},"Work backward from what you'll actually do with each answer."," If a field doesn't route the response, qualify a lead, personalize a follow-up, or satisfy a genuine requirement, it shouldn't be there. This is also the GDPR principle of ",[22,1313,1314],{},"data minimisation"," — collect only what's necessary for your stated purpose (Article 5). Minimisation is both good law and good ",[65,1317,457],{"href":443},[15,1319,1321],{"id":1320},"what-should-you-not-ask-on-a-form","What should you not ask on a form?",[11,1323,1324,1327],{},[22,1325,1326],{},"Anything you won't use — and sensitive data you don't truly need."," Beyond the obvious \"cut vanity fields\", be careful with sensitive topics. Tourangeau and Yan (2007) found that sensitive questions produce more misreporting and more refusals, so adding them costs you both data quality and completions. If you don't need it, don't ask it.",[15,1329,1331],{"id":1330},"how-do-sensitive-questions-change-your-data","How do sensitive questions change your data?",[11,1333,1334,1337,1338,1341,1342,80],{},[22,1335,1336],{},"They lower honesty and raise refusals — so ask them sparingly and carefully."," When a question feels intrusive or socially loaded, people skip it or answer inaccurately (Tourangeau & Yan, 2007). If you genuinely need sensitive information: explain ",[37,1339,1340],{},"why"," you're asking, keep it optional where you can, and place it late — after the respondent has invested effort and has some reason to trust you (see ",[65,1343,1345],{"href":1344},"/knowledge/building-trust-in-forms","building trust in forms",[15,1347,1349],{"id":1348},"should-fields-be-required-or-optional","Should fields be required or optional?",[11,1351,1352,1355,1356,1358],{},[22,1353,1354],{},"Require only what you truly need to proceed; defer or drop the rest."," Forcing optional fields to be mandatory inflates abandonment and breeds junk answers from respondents who ",[37,1357,1179],{}," under pressure (Krosnick, 1991). A short set of genuinely-required fields plus optional or progressively-collected extras beats one long required form.",[15,1360,1362],{"id":1361},"how-roundpushpin-helps-you-ask-the-right-things","How RoundPushPin helps you ask the right things",[11,1364,1365,1368,1369,1371,1372,187],{},[22,1366,1367],{},"RoundPushPin makes minimal, relevant forms easy — and keeps the data typed and queryable so you only collect what you'll use."," Graph-based ",[65,1370,68],{"href":67}," shows sensitive or follow-up questions only when relevant, and because every field maps to a typed column, it's clear exactly what you store — the foundation of ",[65,1373,1375],{"href":1374},"/knowledge/form-data-ownership","data ownership and privacy",{"title":96,"searchDepth":97,"depth":97,"links":1377},[1378,1379,1380,1381,1382],{"id":1304,"depth":97,"text":1305},{"id":1320,"depth":97,"text":1321},{"id":1330,"depth":97,"text":1331},{"id":1348,"depth":97,"text":1349},{"id":1361,"depth":97,"text":1362},"2026-03-14","Every field you add costs completion and risk. This research-backed guide explains how to decide what to ask, what to leave off, and how sensitive questions change both your data quality and your legal exposure.",[1386,1389,1391],{"q":1387,"a":1388},"How do you decide which fields to put on a form?","Start from what you'll actually do with each answer. If a field doesn't route, qualify, personalize, or fulfil a real need, cut it. Every field costs completion, and under GDPR you should collect only what's necessary.",{"q":1321,"a":1390},"Anything you won't use, and sensitive data you don't truly need — research shows sensitive questions raise misreporting and refusals. If you must ask something sensitive, explain why, make it optional where possible, and ask it late.",{"q":1392,"a":1393},"Should form fields be required or optional?","Make required only what you genuinely need to proceed; mark the rest optional or defer it. Forcing optional fields to be required inflates abandonment and encourages junk answers.","/images/knowledge/what-to-ask-on-a-form.png",{},"/knowledge/what-to-ask-on-a-form",{"title":1296,"description":1384},[1399,1403,1404],{"title":1400,"url":1401,"publisher":1402},"Tourangeau, R. & Yan, T. (2007) — Sensitive questions in surveys","https://doi.org/10.1037/0033-2909.133.5.859","Psychological Bulletin",{"title":586,"url":587,"publisher":588},{"title":1405,"url":1406,"publisher":1407},"Regulation (EU) 2016/679 (GDPR) — Article 5, data minimisation","https://eur-lex.europa.eu/eli/reg/2016/679/oj","EUR-Lex, European Union","knowledge/what-to-ask-on-a-form",[595,1314,1410,458],"privacy",[1412,1413,1414],"Decide fields by what you'll act on — every field costs completion, and GDPR says collect only what's necessary.","Sensitive questions increase misreporting and refusals (Tourangeau & Yan, 2007); ask them only if needed, and late.","Keep required fields minimal; defer or drop the rest rather than forcing them.","bxIdGpoSliDGGguGfP_6vI3hYQzp3v9UMUBAZvuyqU4",{"id":1417,"title":1418,"author":6,"body":1419,"date":1514,"description":1515,"draft":105,"extension":106,"faqs":1516,"image":1524,"isPillar":105,"meta":1525,"navigation":118,"path":1344,"pillar":302,"pillarName":303,"seo":1526,"sources":1527,"stem":1535,"tags":1536,"takeaways":1539,"updated":1514,"__hash__":1543},"knowledge/knowledge/building-trust-in-forms.md","How to Build Trust in Your Forms (So People Complete Them)",{"type":8,"value":1420,"toc":1507},[1421,1424,1428,1438,1442,1460,1464,1474,1478,1487,1491],[11,1422,1423],{},"A form asks people to hand over their data, and people only do that for a site they trust. Trust isn't a nice-to-have on a form — it's a precondition for completion, and it's especially fragile the moment you ask for something personal.",[15,1425,1427],{"id":1426},"why-does-trust-matter-for-form-completion","Why does trust matter for form completion?",[11,1429,1430,1433,1434,1437],{},[22,1431,1432],{},"Because submitting a form is an act of trust, and doubt converts directly into abandonment."," When credibility is low, people hesitate, skip fields, or leave — and the effect is sharpest on sensitive questions, where distrust drives both refusals and inaccurate answers (Tourangeau & Yan, 2007). Earning trust isn't separate from conversion; it ",[37,1435,1436],{},"is"," part of conversion.",[15,1439,1441],{"id":1440},"what-makes-a-form-look-trustworthy","What makes a form look trustworthy?",[11,1443,1444,1447,1448,1451,1452,1455,1456,1459],{},[22,1445,1446],{},"The elements people notice, and the meaning they assign to them."," Fogg's ",[37,1449,1450],{},"Prominence-Interpretation Theory"," (2003) explains online credibility as a two-step process: a person has to ",[22,1453,1454],{},"notice"," an element (prominence), then ",[22,1457,1458],{},"interpret"," it as good or bad. So trust on a form is built from noticeable, positively-interpreted cues — a clean, professional design, a real organization clearly behind the form, plain language, and no jarring or excessive questions (Nielsen Norman Group). Sloppiness and surprises read as risk.",[15,1461,1463],{"id":1462},"how-do-you-reassure-people-about-their-data","How do you reassure people about their data?",[11,1465,1466,1469,1470,1473],{},[22,1467,1468],{},"Tell them what you'll do with it, why you're asking, and prove you ask for little."," Concretely: state the purpose in plain language, link a privacy notice near the submit action, keep the form ",[65,1471,1472],{"href":1396},"minimal",", and when you must ask something sensitive, explain why and place it late — after the person has invested effort. Transparency is what lowers the refusals that distrust causes (Tourangeau & Yan, 2007).",[15,1475,1477],{"id":1476},"do-trust-signals-actually-change-behaviour","Do trust signals actually change behaviour?",[11,1479,1480,1483,1484,1486],{},[22,1481,1482],{},"Yes — but only the ones people notice and believe."," Prominence-Interpretation Theory is a useful filter: a trust cue does nothing if it isn't noticed, and backfires if it's interpreted as hollow. Genuine signals (a real company, a clear privacy explanation, a short honest form) beat generic badges. Test which cues move ",[65,1485,457],{"href":443}," for your audience rather than assuming.",[15,1488,1490],{"id":1489},"how-roundpushpin-helps-you-earn-trust","How RoundPushPin helps you earn trust",[11,1492,1493,1496,1497,1501,1502,1506],{},[22,1494,1495],{},"RoundPushPin supports trustworthy forms by default: clean conversational design, minimal relevant questions, and self-hosted data you genuinely control."," Because responses live in ",[65,1498,1500],{"href":1499},"/knowledge/self-hosted-forms","your own database",", \"we keep your data private\" isn't a slogan — you decide where it lives and how long you keep it, which is the substance behind ",[65,1503,1505],{"href":1504},"/knowledge/gdpr-compliant-forms","GDPR-compliant"," trust claims.",{"title":96,"searchDepth":97,"depth":97,"links":1508},[1509,1510,1511,1512,1513],{"id":1426,"depth":97,"text":1427},{"id":1440,"depth":97,"text":1441},{"id":1462,"depth":97,"text":1463},{"id":1476,"depth":97,"text":1477},{"id":1489,"depth":97,"text":1490},"2026-03-16","People won't hand over data to a form they don't trust. This research-backed guide covers how visitors judge credibility, the trust signals that matter on forms, and how to reassure people about their data.",[1517,1519,1521],{"q":1427,"a":1518},"Filling in a form means handing over data, which people only do when they trust the site. Low credibility raises hesitation and abandonment — and on sensitive questions, distrust increases refusals and misreporting.",{"q":1441,"a":1520},"Credibility comes from elements people notice and judge positively — clear design, a real organization behind it, plain language about why you ask, visible privacy/security cues, and no surprising or excessive questions.",{"q":1522,"a":1523},"How do you reassure people about their form data?","Tell them plainly what you'll do with it and why each question is asked, link a privacy notice, keep the form minimal, and place any sensitive question late with an explanation. Transparency reduces refusals.","/images/knowledge/building-trust-in-forms.png",{},{"title":1418,"description":1515},[1528,1532,1534],{"title":1529,"url":1530,"publisher":1531},"Fogg, B. J. (2003) — Prominence-Interpretation Theory: explaining how people assess credibility online","https://doi.org/10.1145/765891.765951","CHI '03 / Stanford Web Credibility Project",{"title":1450,"url":1533,"publisher":131},"https://www.nngroup.com/articles/prominence-interpretation-theory/",{"title":1400,"url":1401,"publisher":1402},"knowledge/building-trust-in-forms",[1537,1538,456,458],"trust","credibility",[1540,1541,1542],"People only submit data to a form they trust — low credibility raises hesitation and abandonment.","Credibility is what users notice and how they interpret it (Fogg's Prominence-Interpretation Theory).","Reassure with clear purpose, visible privacy cues, minimal asks, and sensitive questions placed late.","tzUin9YU-8HMjkplypyURGhSFed0__aoIDxr88QnEPQ",[],1780692424593]