Set the decision
Clarify filtered result counts.
Product and software research / Survey guide
Product and software research · A focused questionnaire
Facet count comprehension survey
Clarify filtered result counts.
Opens product registration. Example questions are not imported automatically.
WHAT TO READ · WHAT TO TEST
Observation
Users read facet counts as totals after filtering.
Interpretation boundary
Feedback does not verify backend counts.
Next experiment
Explain the counting scope beside facets.
Illustrative scenario. These are not real response counts or findings.
From question to next step
Make the feedback useful.
Invite relevant voices
Ask after an adult respondent has encountered this specific situation. For draft-copy testing, show the actual material first; accept none or not applicable when the issue did not occur.
Choose an action
Explain the counting scope beside facets.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Users read facet counts as totals after filtering.
Choose an action to test
Explain the counting scope beside facets.
Check the experience again
After testing this change—Explain the counting scope beside facets.—ask people who encountered the changed arrangement whether this original issue still occurred or did not occur: “Users read facet counts as totals after filtering.” Invite a concrete explanation, including none or not applicable. Compare participant context and sample differences; a before-and-after survey alone does not establish causation.
A useful starting point
Three questions for this specific decision.
Clarify filtered result counts. These prompts examine count meaning, filter interaction, explanation need. Choose only questions your audience can answer. A missing detail can be answered with none; do not assume an issue occurred.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
What did the count represent?
Read for count meaning. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
Which filter changed it unexpectedly?
Read for filter interaction. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
What counting explanation was missing?
Read for explanation need. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. What did the count represent? Which filter changed it unexpectedly? What counting explanation was missing?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| What did the count represent? | Optional free text; none or not applicable accepted | Read for count meaning. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
| Which filter changed it unexpectedly? | Optional free text; none or not applicable accepted | Read for filter interaction. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
| What counting explanation was missing? | Optional free text; none or not applicable accepted | Read for explanation need. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
Make questions optional where appropriate. If you add a rating scale, label its endpoints, keep one idea per question, and retain a follow-up for reasons. These examples are not a validated measurement instrument.
Read the answers carefully
What these answers cannot establish.
Feedback does not verify backend counts.
Users read facet counts as totals after filtering. This is an illustrative pattern, not observed customer data. Feedback does not verify backend counts.
Before you send it
Check what your wording assumes.
Would you agree that this entire experience was clear and easy?
What did the count represent?
The first wording assumes a positive outcome and combines clarity with ease. The revised prompt asks about the concrete situation; respondents may report no difficulty.
Before you send it
Questions, answered.
Who should answer?
Product users who attempted the specific interface or workflow task; use synthetic examples without private records. Ask only about the step each person actually encountered; voluntary responses are not automatically representative.
What does the first question help explain?
Read for count meaning. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. It supports this decision: Clarify filtered result counts.
What should I preserve in the second answer?
Read for filter interaction. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
How should I read the third answer?
Read for explanation need. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. Feedback does not verify backend counts.
What would a practical follow-up look like?
Explain the counting scope beside facets. After testing this change—Explain the counting scope beside facets.—ask people who encountered the changed arrangement whether this original issue still occurred or did not occur: “Users read facet counts as totals after filtering.” Invite a concrete explanation, including none or not applicable. Compare participant context and sample differences; a before-and-after survey alone does not establish causation.
Can I load this automatically in SurveyTeams?
The page offers text, CSV, JSON and Markdown downloads plus manual copying. Registration does not import the questionnaire. Use account-supported features and verify your own response-handling arrangements.
Inside the product
Create a manual draft and check the questions
The real SurveyTeams screenshot shows a separate labelled synthetic event survey. It demonstrates the manual builder, not this questionnaire already loaded and not the task described in the software being evaluated.
- Start a draft with this decision in mind: Clarify filtered result counts.
- Copy or select only applicable questions from this page. Add them as optional text prompts; the download is an editorial definition, not a product importer.
- Preview the respondent wording. Feedback does not verify backend counts. Explain your actual response handling before distribution.
Creation and preview were exercised in the observed account. Distribution, results and other features are separate workflows and depend on account conditions.
Build with SurveyTeams
Adapt these questions in your own survey.
Use these examples to draft your questionnaire. Create a survey draft, add questions, and check the respondent preview in SurveyTeams. Additional features depend on your account and plan.
Create your survey in SurveyTeams
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗Continue exploring