Synthetic comments C1 and C5 concern access, C2 clarity, C3 access plus clarity and C4 no issue.
Survey design and interpretation / Survey guide
Survey methods · Worked example
Code open survey comments with a reviewable codebook
Build a small survey-comment codebook, retain multi-theme cases and distinguish theme mentions from the number of respondents.
Opens product registration. Example questions are not imported automatically.
PLAN A BOUNDED FOLLOW-UP
Write access, clarity and no-issue definitions; keep C3 in both issue codes and retain an uncertainty/reviewer column.
Have another reviewer code the same small sample using the definitions, discuss disagreements and version the codebook before applying it more broadly.
Synthetic planning example. A repeat survey alone does not establish causation.
From question to next step
Make the feedback useful.
Set the decision
Ask after a specific onboarding task. Explain that comments can be skipped and should avoid identifying colleagues.
Invite relevant voices
Write access, clarity and no-issue definitions; keep C3 in both issue codes and retain an uncertainty/reviewer column.
Choose an action
Have another reviewer code the same small sample using the definitions, discuss disagreements and version the codebook before applying it more broadly.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Synthetic comments C1 and C5 concern access, C2 clarity, C3 access plus clarity and C4 no issue.
Choose an action to test
Write access, clarity and no-issue definitions; keep C3 in both issue codes and retain an uncertainty/reviewer column.
Check the experience again
Have another reviewer code the same small sample using the definitions, discuss disagreements and version the codebook before applying it more broadly.
A useful starting point
Free-text pilot questions
A reviewer has five short comments about an onboarding process. One comment mentions two issues; another reports no issue. Review code definitions before reporting theme totals.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
What information or access was missing when you first tried the task?
Separate missing information from unavailable permissions without asking for credentials.
Which instruction was difficult to interpret?
Identify wording or sequencing ambiguity for a clarity code.
What worked without a problem?
Preserve no-issue evidence rather than selecting only complaints.
Is there another explanation we should consider for the difficulty you described?
Leave room for competing explanations and uncertain coding.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. What information or access was missing when you first tried the task? Which instruction was difficult to interpret? What worked without a problem? Is there another explanation we should consider for the difficulty you described?
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 information or access was missing when you first tried the task? | Optional short open text | Separate missing information from unavailable permissions without asking for credentials. |
| Which instruction was difficult to interpret? | Optional short open text | Identify wording or sequencing ambiguity for a clarity code. |
| What worked without a problem? | Optional short open text | Preserve no-issue evidence rather than selecting only complaints. |
| Is there another explanation we should consider for the difficulty you described? | Optional short open text | Leave room for competing explanations and uncertain coding. |
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
Limits to preserve
Themes can overlap. A coded comment is not automatically a distinct respondent, and a volunteered comment sample does not establish issue prevalence.
Coding note: five comments, six theme mentions and one multi-theme case. Retain the codebook and disagreement notes; do not claim population prevalence.
Before you send it
Check what your wording assumes.
Tell us only what was wrong with onboarding.
What worked without a problem?
The revision preserves evidence that could challenge a complaint-only interpretation.
Run a focused feedback cycle
Plan the invitation, review and follow-up.
When and whom to ask
Ask after a specific onboarding task. Explain that comments can be skipped and should avoid identifying colleagues.
Who reviews the finding
The qualitative reviewer owns code definitions; the process owner investigates examples without treating counts as blame.
What to check after a change
Recode a small unchanged sample with the revised definitions and check agreement through discussion, not an invented reliability score.
Handle responses carefully
Remove names, credentials and unnecessary personal details before sharing comments. Do not promise anonymity if comments can be linked back to a person.
A worked measurement study
Inspect the data. Trace the decision.
Every record here is synthetic. Use the rule to review your own evidence before taking action.
Keep evidence and inference separate
Observed
Five example comments and proposed codes
Supports a transparent coding demonstration.
Unknown
Prevalence among everyone invited
Do not generalize volunteered comments to all users.
Next check
A second reviewer codes the unchanged sample
Revise unclear code boundaries and retain contrary cases.
Invented records · inspect every count
| Invented comment ID | Invented text | Proposed codes |
|---|---|---|
| C1 | Could not open the required tool | Access |
| C2 | The first-step instruction was unclear | Clarity |
| C3 | Tool access was missing and the instruction was unclear | Access; clarity |
| C4 | Nothing blocked the first task | No issue |
| C5 | The needed permission arrived late | Access |
On small screens, scroll a wide table sideways to see all columns.
| Code | Include when | Exclude or leave unresolved |
|---|---|---|
| Access | A required tool, account or permission was unavailable or late. | Do not assign access from a vague negative comment alone. |
| Clarity | The person identifies unclear instructions, wording or sequence. | Do not assign clarity only because access was unavailable. |
| No issue | The person explicitly states no obstacle for the task. | Do not infer no issue from a blank answer. |
| Unresolved | The comment is too vague to distinguish a cause. | Keep the uncertainty; seek optional clarification without forcing an issue code. |
On small screens, scroll a wide table sideways to see all columns.
Download example data (.csv) · Download method worksheet (.json)
Read units and denominators with the source table. These are invented example records.
Work through the rule
Access appears in 3 of 5 comments; clarity in 2; no issue in 1. Six assigned theme mentions belong to five comments because C3 has two codes.
Coding note: five comments, six theme mentions and one multi-theme case. Retain the codebook and disagreement notes; do not claim population prevalence.
Before you send it
Questions, answered.
May one comment receive two themes?
Yes under this explicit multi-code rule. Report theme mentions and comments separately.
Should no-issue comments be discarded?
No. They can challenge a one-sided interpretation and belong in the coding record.
Does a code count prove the cause?
No. It identifies a pattern to investigate; verify process evidence before attributing a cause.
Can I load this example automatically?
No. Copy or download the free-text pilot questions and adapt them in your draft. The registration link does not import them. The calculation worksheet is a separate manual example; verify supported fields and features in your account.
Build with SurveyTeams
Adapt these pilot questions in SurveyTeams
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