1. Focus on the specific BEHAVIOR.

A *specific* behavior is someone doing a specific action in a specific context.

Imagine your team wants to build an app that helps busy professionals to be less stressed and more calm. That's not a behavior. That's the objective you want to achieve with the app. So, what's the behavior? Let's say one of the behaviors the app will prompt people to take a meditation break outside. Great! The *specific* behavior is: people take a meditation break outside

2. Test with ten people. 

Ten people is all you need to do Snaptesting.

Imagine your team runs one test on 100 people. You have only tested one idea on 100 people. Whereas with ten people per Snaptest, you are learning faster and would have gone through ten iterations with your 100 people.

3. What does *success* look like?

6 people out of 10 doing your behavior is a homerun.

One-third of your testers will flake no matter what you do. 3 of 10 is worth investing in the next Snaptest. So, 6 out of 10 people doing your specific behavior is a homerun. You have a clear signal to take the next step.

4. Design + Launch your Snaptest in four hours of work (or less)

Yes, you can learn what you need in four hours of work (or less).

Snaptesting is meant to be quick and quantitative. Because you're focusing on the specific behavior, you'll learn new insights that will inform the next iteration. Snaptesting doesn't require you to know two, three, five, ten, steps ahead. Note: the four hours do not have to be consecutive. It can be split among different days or work chunks.

5. Fastest way to get an answer to STOP or Take the Next Step.

Snaptesting is the fastest way to get to a clear Go or No Go signal.

What's the next step? Well, that's up to you and your team. What do you do if you get data to STOP? Move onto a new specific behavior to Snaptest.

Please reload

  • Twitter Social Icon
  • Facebook Social Icon

Box 20456, Stanford, CA 94309​

© 2018 BJ Fogg