At what point do you move on and start testing something new?

When does it make sense to continue iterating because there’s still some juice left to squeeze? The Iterate Vs Move framework deals with this.

This is a great visualization of how iterations are important to experimentation, but can sometimes be deprioritized if other initiatives take precedence. Remember, testing and iterations are costly. Use this blueprint as a starting point in decision making whether to iterate vs. move on to the next test, and build this into your own prioritization framework.

Use Cases:

- Determine before the test if the iteration costs too much.

- Decide between iterating and moving to a new hypo.

‍