Design customer surveys with clear objectives, unbiased questions, and analysis plans.
/survey-question-generator3-4 hrs → 15 min
Compared to doing it manually
/survey-question-generatorType this in Claude to run the skill
Most surveys ask leading questions, are too long, and produce data nobody can act on.
.claude/skills/ folder in your project/survey-question-generator in Claude to run the skill/jtbd-extractorExtract Jobs-to-be-Done statements from research data to uncover innovation opportunities.
/user-interview-analyzerTransform interview transcripts into structured insights with quotes, patterns, and recommendations.
/feedback-categorizerAnalyze and categorize customer feedback into actionable themes using affinity mapping.
/app-review-analyzerExtract themes, complaints, and feature requests from app reviews at scale.
Keep questions clear, specific, and unbiased. Avoid leading questions, double-barreled questions (two questions in one), and jargon. Use scales consistently. Test with a small group before sending widely.
5-10 minutes maximum for most surveys. Completion rates drop dramatically after 10 minutes. Prioritize ruthlessly — every question should earn its place. If you need more data, consider multiple shorter surveys.
Closed questions have predefined answers (scales, multiple choice) — easy to analyze, but limit responses. Open questions allow free text — rich insights, but harder to analyze. Use a mix, with open questions sparingly.
Run this skill inside your PM Operating System, or download it on its own.
Use all 70 skills, workflows, and sub-agents in a system that knows your company, product, and customers.