Transition ideas from abstract concepts to actionable next steps and start to learn about their viability in the real world
Rapid Experimentation is a hallmark for building out innovative solutions. The more quickly you can start to learn about your ideas, get them into tangible form, and test them - the sooner you and your team can iterate on your solutions based on real-world feedback. Do this together as a team after you've decided on a list of prioritized concepts you want to advance and explore
Identify the ideas to test
Work with your team and/or users to identify ideas you want to learn about. At this point, the ideas should be articulated as detailed concepts - where you have a sense for who it's for, what you're trying to accomplish, how that might be accomplished, what's involved, etc.
Align on what you need to learn
Use the Rapid Experimentation Template provided to build a learning plan. As a team, start the learning plan by determining the most important questions that are critical to the success of your concepts.
Determine your success metrics
Discuss what measures will help gauge success. What indicators would signal that you have been successful in your test? For example, what audience behaviors or attitudes would indicate your idea is worth moving forward? Then, determine how to measure the size or extent of these behaviors or attitudes, as needed.
Plan your tests and prototypes
As a team, figure out the simplest and leanest way to test out your concepts. Determine if prototypes or mock-ups are needed to support your tests. If so, think small and scrappy. Plan for tests and prototypes that are simple to execute (i.e., can be accomplished in days or weeks vs. months).
Check your assumptions
As a team, check your assumptions about what would need to be true for your test to work. This provides your team an opportunity to address potential barriers before you run your experiment.
Determine next steps
Establish next steps. Agree on a reasonable window of time for coordinating the execution of these tests. Discuss how the team will reconvene to share learnings from these tests.
Run your tests
Build your prototypes and mock-ups as needed. Put your experiments out in the world. Capture your learnings and metrics in your template.
Assess and repeat
When your cycle of experiments conclude, reconvene as a team. Conduct a retrospective, review what you learned as a team. Based on these learnings, discuss next steps (i.e., adopt, adapt, or abandon). Repeat and iterate the testing cycle above - until you've reached the desired level of understanding about whether your idea is desirable, feasible and viable.