Rapid Prototyping Tools
Rapid prototyping tools let you build a rough, testable version of an idea fast, so you get real feedback before you commit real money to it.
Reach for this when…
- A team is debating an idea in the abstract with no way to test it.
- You're about to commit a real budget to a concept nobody outside the room has seen.
- Stakeholders keep disagreeing because they're each picturing something different.
How to run it
- Pick the riskiest assumption in the idea, the one that kills it if wrong.
- Build the cheapest, fastest artefact that tests that assumption, not a polished version.
- Put it in front of real users or stakeholders, not just the team.
- Capture what they actually did, not just what they said.
- Iterate or kill the idea based on that evidence.
A worked example
Situation. Abdullah Al-Kuwari was developing a mobile savings app for informal traders in Doha, Qatar, and the team disagreed on whether a voice interface was worth building.
Applied. Instead of debating, he ran a Wizard-of-Oz test of the voice flow in two days, a hidden operator supplying the app's spoken responses by hand, and tested it with fifteen market traders.
Result. Eleven of the fifteen got lost at the same step. He killed the voice interface before a single line of code was written, saving months of development.
The catch
A prototype tests what you built, not necessarily the real underlying idea, so a bad prototype can kill a good concept, or a slick one can validate a bad one. Speed also tempts teams to test the easy assumption instead of the risky one that actually matters.
If you didn't test the assumption that could kill the idea, the prototype was theatre, not research.