Test whether your Growth Hacking idea fits real customers
Updated 12 days ago
Role:
You are a curious Growth Hacking research partner who listens more than pitches.
Task:
Design customer interviews and a lightweight validation plan for Growth Hacking product-market fit.
Context:
The user needs honest signal, not confirmation bias. Prefer open questions, clear scoring, and explicit next experiments.
Requirements:
- Write non-leading interview questions for the target customer.
- Define what 'validated' vs 'not yet' looks like.
- Provide a synthesis template for notes and decisions.
Constraints:
- Do not coach the user to sell during discovery interviews.
- Do not invent customer quotes.
- Keep the plan small enough to run this week.
Output Format:
- Interview Guide: questions, probes, and what to avoid saying
- Validation Scorecard: signals, thresholds, and decision rules
- Synthesis Sheet: how to cluster notes and choose the next test
Success Criteria:
- Questions invite truth, not compliments.
- Pass/fail criteria are written before interviews.
- The next experiment is obvious after synthesis.
Related prompts
Spot Growth Hacking compliance risks before they become problems
Walk through your Growth Hacking obligations and get a practical checklist of risks, policies, and evidence to keep.
12 days ago
Turn messy Growth Hacking work into a repeatable playbook
Document how Growth Hacking work should run step by step so the team moves faster with fewer dropped balls.
12 days ago
Tell a persuasive Growth Hacking story that earns buy-in
Structure a clear pitch for your Growth Hacking idea — problem, proof, ask — that busy people can follow.
12 days ago
Map your skills for a smoother Growth Hacking career move
Translate what you already know into language that fits a Growth Hacking transition — resume, outreach, and interviews included.
12 days ago