Idea Development
Testing & Feedback
Test early, test often, and listen with open ears. You’ve created a prototype — now it’s time to see how people actually respond to it. Will they get it? Will they want it? Will it work in the way you hoped? The only way to know is to test — and to welcome feedback like a pro.
Why Testing Matters
Even the most brilliant ideas have blind spots. Testing helps you:
Find out what works (and what doesn’t);
Discover what’s confusing, clunky, or missing;
Learn how users actually behave — not just what they say;
Avoid spending weeks building the wrong thing.
“You’re not launching. You’re learning.”
What to Test
You don’t need to test everything — just the most critical assumptions.
Ask:
Do people understand my solution?
Can they use it easily?
Does it solve the problem I think it does?
What surprises them (in a good or bad way)?
How to Get Feedback
Use this 3-Question Feedback Test:
Grab a notebook or open a new doc and do this:
What stood out to you?
(Find out what’s memorable, useful, or confusing.)What would you change or improve?
(Uncover friction points or gaps.)Would you use this or recommend it? Why or why not?
(Get a sense of real-world appeal.)
Activity: Run a Quick Test
Share your prototype with at least 3 people who match your target user.
Ask them the 3 feedback questions above.
Record key quotes and observations.
Reflect with your team: What should we change based on what we heard?
Test in person or over video call — whatever helps you see their reactions.
Make Sense of What You Heard
After testing, take 15–20 minutes to debrief as a team:
Patterns matter more than one-off comments.
Real Talk
Not all feedback is equal — listen to your target user first;
Don’t get defensive. Stay curious;
Testing is ongoing. You’ll test again after every improvement;
The goal isn’t to prove your idea — it’s to improve your idea.