All 141 tools / Research and usability testing
Find leading, double-barrelled and hypothetical questions in an interview or survey script and rewrite them.
Research questionsFreeFor researchers, designers and product teams
30/day
free runs a day, no sign-in.
Before: what you give it
The example input, as typed in. You paste text, CSS, markup or notes.
Don't you think the new dashboard is easier to use? Would you pay for a tool that tracks your expenses? How do you find and share reports? Why did you stop using the old app? Tell me about the last time you split a bill with friends.
After: what comes back
The first lines of a real run on that input. Nothing here is edited by hand.
5 interview questions, 2 with nothing to fix
- Don't you think the new dashboard is easier to use?
leading: "Don't you think" tells people the answer you hope for
try: Ask neutrally: "How would you describe X?" or offer the scale's two opposite ends.
- Would you pay for a tool that tracks your expenses?
hypothetical: people are poor at predicting their own future behaviour; "would you" answers run optimistic
try: Ask about the last time: "Tell me about the last time you [did the thing]. What did you do?"
+ How do you find and share reports?
- Why did you stop using the old app?
why: "why" can sound like a demand for justification, and people produce tidy reasons after the fact
try: Ask "What led to that?" or "What was going on when you did that?"
+ Tell me about the last time you split a bill with friends.
... full output on the tool page
What you get
Each question marked with its problem and a suggested rewrite, with the clean ones shown as fine
What it cannot do
Checks wording patterns only; it cannot judge whether the questions answer your research goal.
Who it is for
- Researchers
- Designers
- Product teams
Free and Pro
| Free | 30 runs a day per IP address, up to 20,000 characters a run. |
|---|---|
| Pro | No daily limit, 300 requests a minute, up to 200,000 characters a run. |
Use it from your assistant
The tool is called lint_research_questions. Connect the server once, then ask for it by name or just describe the job. Install steps for each app.
claude mcp add --transport http designers https://designers.allthepossibles.com/mcp
curl -X POST https://designers.allthepossibles.com/api/research-lint -H 'content-type: application/json' -d '{"text":"Don'\''t you think the new dashboard is easier to use?\nWould you pay for a tool that tracks your expenses?\nHow do you find and share reports?\nWhy did you stop using the old app?\nTell me about the last time you split a bill with friends."}'
Try it here
The form starts with the same example input, so you can run it first and then swap in your own.
More in research and usability testing
- Usability numbers
Score SUS results and work out sample sizes for usability tests, A/B tests and surveys.
- Heuristic review
Get a Nielsen heuristic worksheet for a screen or flow, with signals showing where to look first.
- Critique plan
Plan a design critique for the stage the work is in, with timed rounds, roles and feedback to hold back.
- Trunk test
Check whether a page answers Krug's six trunk-test questions: site, page, sections, options, location, search
- Form check
Check a form's markup against Wroblewski's Web Form Design rules and get a fix for each finding
- Card sort analyser
Turn open card-sort results into a similarity matrix and suggested categories from participant agreement