Contenido del curso
Listening to your user
Creating valuable ideas
Considering the outside world
Recap
Putting your ideas to the test
Going from idea to business
Getting people on board
Innovating in the real world
Six Prototyping Methods Before You Build Anything
Resumen
Prototyping is the fastest way to validate an idea before investing time and money, and choosing the right type of prototype can save you from building something nobody wants. You will learn six practical prototyping methods, when to use each one, and how they help you gather real feedback from users, whether you are an entrepreneur, product designer, or innovator testing a new concept.
What is the simplest way to start prototyping an idea?
The easiest entry point is storytelling, and you can do it right now with whatever idea you have in your head [0:22].
Storytelling means describing the experience or product to a potential user and collecting their reaction. It requires zero materials, zero setup, and zero technical skill. The catch? It leans heavily on the user's imagination. They have to picture what you are describing, and that picture may not match yours.
What is a prototype? A prototype is a basic first version of an idea built to gather feedback. It does not need to be functional or polished, only good enough to learn something useful from users.
Use storytelling as your starting point, then graduate to richer formats that give you more reliable signals.
How does role-play work as a prototype?
Role-play takes storytelling one step further by acting out the experience with the user [1:12]. You assign roles, add visual support if possible, and simulate the scenario together.
The magic here is participation. Once the user is inside the scene, they start reacting honestly: I would not do that, I would not feel comfortable stepping up here, If you told me that, I would not understand. That kind of feedback almost never surfaces during pure storytelling.
And yes, you can role-play sophisticated services too. Remember, a prototype is basic on purpose. Ask the user to imagine the missing pieces with you.
Why are physical models useful for feedback?
A model is a simple, tangible representation of your idea, often built with paper or basic materials [2:28]. You can start at low fidelity and slowly increase detail as you learn.
The famous example is the original Palm Pilot: a piece of wood and paper that let the founder simulate carrying and using the device long before any chip existed. Another example comes from Cinepolis, where an entire cinema was modeled on a tabletop so users could answer questions like:
- Would you buy popcorn here?
- Do you know where the gift shop is?
- What do you think about the restroom location?
It is much cheaper to move the gift shop on paper than to move it after construction. Models turn abstract ideas into something visual, which unlocks specific and honest feedback.
How do fake door and Wizard of Oz prototypes work?
Both methods let you test demand or experience without actually building the product. They are powerful because they measure real behavior, not just opinions.
What is a fake door test?
A fake door promotes a product or service that does not exist yet, just to measure interest [4:15]. The example in the class is Note It, a fictional product with a button that says Buy early access for $5. Nobody gets charged. The team simply counts clicks against a success threshold defined in their hypothesis.
What is a fake door prototype? It is a marketing test where you advertise a product that does not exist and count how many people show intent to buy. If demand hits your target, you build it. If not, you dodged a bad investment.
Fake doors also work offline. Imagine a coffee shop testing a new drink. Instead of buying ingredients for 50 servings, you add the drink to the menu board and count orders. When someone asks for it, you reply: We just ran out, it was super popular, come earlier next time. No harm done, and you now have real demand data.
What is a Wizard of Oz prototype?
The Wizard of Oz delivers the full experience of a working service, but the invisible processes are done manually behind the scenes [6:35]. The name comes from IBM's 1984 listening typewriter test, where users dictated text and watched it appear on screen as if by magic. Behind the wall, a human was typing everything they heard.
IBM validated interest in speech recognition before the technology existed. If users had not cared, the investment would have stopped there.
When should you run a pilot instead of a prototype?
A pilot is a short-term, limited launch where you actually sell your product or service, with the main goal of learning and improving [7:52]. Unlike the other methods, real money changes hands.
Instead of renting a full store in a premium neighborhood, you set up a small stand and observe. Maybe it works and you scale up. Maybe you discover the neighborhood is wrong entirely. Either way, the pilot answers questions no whiteboard can.
Here is a quick way to think about which method fits your moment:
- Storytelling: earliest stage, zero materials, tests basic understanding.
- Role-play: active user involvement, tests emotional and behavioral reactions.
- Model: visual and tangible, tests spatial or product decisions.
- Fake door: tests real demand before building.
- Wizard of Oz: tests full experience without full technology.
- Pilot: tests a real market with a limited version.
Now think about your own idea. Or borrow this one: a platform to lend items you are not using and rent items you only need temporarily. Make extra money renting your stuff, and rent instead of buy. How would you prototype it? Storytelling, role-play, model, fake door, Wizard of Oz, pilot, or something entirely new? Drop your prototype plan in the comments so we can keep building this thinking together.