You have a hypothesis of a new feature that would improve x on your product and you don't have any data backing up your decision as this feature is new territory. How do you know this hypothesis is better to test now than other hypothesis, and what is the best way to test it without spending any time coding or even designing it?

Do you put a fake button to see if people are interested in this? Do you sent an email and see how many people interact to see what is upcoming? Do you make people test a website that already has this to see how they react?

I feel like doing user interviews for qualitative data in this case can be misleading because if 6 participants say that they would use the feature it doesn't mean that the rest of the people will.

So the question is, how do you know what to test at the right time so you can move fast?


Really good question! I used to have this conundrum for a while and then I found the solution in the Google Design Sprint.

You can find more information about it online but basically, the methodology answers your question exactly : "What is the the next step right now?"

It was created by Google Ventures (the company that acquires new startups for Google and helps them get on the right track) and now the methodology is open to use by anyone.

In a nutshell: In 4 days you bring in all your stakeholders and you run a series of exercises: Monday - Mapping and Sketching, Tuesday - Decisions and Storboarding, Wednesday - Prototyping and Thursday - Testing. In one week you can clarify the vision of your organization and know what the next step is.

You should try it! It works wonders and it saves so much time!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.