Microsurveys: the one-question survey people actually answer

Surveys fail on effort arithmetic. Ten questions in an email costs the respondent ten minutes of their day for your benefit — so only the very engaged (or very angry) pay it, and response rates show it. A microsurvey inverts every term: the cost is seconds, the moment is now, the topic is the thing on their screen. Participation multiplies, and — just as important — the sample changes: you start hearing from the quiet middle instead of only the motivated edges.

The context does double duty. Answers to “what almost stopped you from ordering?” asked at the order are concrete — “the shipping cost appeared late” — where the same question a week later by email retrieves a fog (“something about checkout?”). Feedback decays; microsurveys harvest it fresh.

The pattern behind all of them: name the moment, ask about their experience rather than your quality, and make the first response a tap where possible. The full question bank is in 40 customer feedback questions.

The honest weakness of the classic microsurvey: one closed question produces one data point. “Was this helpful? — No” is a smoke alarm with no address. Teams historically patched this by adding a comment box (which most people skip) or growing the survey (which kills the response rate that justified it).

The current fix is to make the microsurvey conversational: keep the one-tap opener, and let a follow-up react to the answer — “you said no — what were you looking for?” The visitor still controls the cost (a tap, and words only if willing), but the willing now leave reasons instead of verdicts. Why the chat format specifically lifts answer depth is covered in conversational surveys.

• One prompt per visitor per session — and a long cool-down after an answer or a dismissal. The channel survives on restraint.
• Fire on completion, not interruption. After the order, after the export, after the article — never over a form half-filled.
• Inline placement for page questions. A prompt sitting in the page’s content flow reads as part of the page; a modal reads as an ambush. The placement options are covered in website feedback widgets.
• Rotate moments, not lengths. Need five answers? Five prompts at five moments, each tiny — never one prompt with five questions.
• Read what comes back, weekly. Ten minutes over fresh answers, or automatic theming if the volume outgrows that — collection without reading is theater.

What is a microsurvey?

A microsurvey is a very short survey — typically one question, at most three — shown in context: on a specific page, after a specific action, or at a specific moment in a product. The small ask and the live context are why microsurveys get response rates that long-form surveys never see.

How long should a microsurvey be?

One visible question is the ideal; two or three is the ceiling before completion drops noticeably. If you need more answers than that, run several microsurveys at different moments rather than growing one of them into a form.

What is a good microsurvey question?

One that names the moment it appears in: 'What almost stopped you from completing your order?' after checkout, 'Is anything unclear on this page?' on pricing, 'Did this article answer your question?' at the end of a docs page. Specificity to the moment is what makes the single question count.

What's the difference between a microsurvey and a feedback widget?

A feedback widget is the always-available channel (a button any visitor can open, about anything); a microsurvey is a targeted prompt you initiate at a chosen moment with a specific question. Most sites benefit from both: the widget catches the unprompted, the microsurvey asks the silent majority.