Module 3: Prototyping, Testing & Experimentation
Why should you use this method?
- Reduce the time it takes to validate a solution idea
- Remove distractions & quickly find out how you can achieve impact
How can you apply this method?
1. Give your idea a catchy name
Don’t linger on this step for too long. Find a short, descriptive name for each functionality. The goal here is to have a name you can remember them by in your conversations.
2. Describe the intended (game-changing) impact
This is the first most important step. What’s the impact / outcome you want to achieve?
3. Identify the key function to deliver that impact
This is the second most important step. What’s the ONE function my idea must perform to do that?
4. Describe your target customer
5. Observe whether doing the key function delivers the impact
Ask yourself “How can I give myself the ability to observe whether doing this accomplishes that impact?”. Observe it and answer the question “Does performing that key function deliver the impact?”
What if the idea has many functions?
It’s possible that, at the beginning of a conversation, an idea for a solution is being discussed. That solution can have many parts that add more or less value to the final impact you want to achieve.
For example, Facebook is a solution with many parts: User accounts, login, password reset, newsfeed, friends, photo upload, video upload, etc. Not all these features have the same value in delivering the impact of Facebook as a solution. The same is true for most ideas, which is why you need to prioritize functions of every new idea.
How to prioritize your functions?
In one column, list all the functions that your idea would perform in the life of your customer.
In the second column, prioritize the functions ruthlessly by how likely they are to accomplish the impact.
Finally, identify the 1-2 critical aspects / functions of your idea, those that are most likely to accomplish the impact.