Do you want to improve your writing? Try our new evaluation service and get detailed feedback.
Check Your Text it's free

The GV research sprint: a 4-day process for answering important startup questions

The GV research sprint: a 4-day process for answering important startup questions JLr8E
Updated June 2021 The founders and designers we work with in the Google Ventures (GV) portfolio have a lot of important questions. Is there a market for my product? Will my product help people solve their problems? What should I build? The answers to these questions just raise more questions: Do people understand my product? Will people find my product useful? Can people use my product? And so it continues. As we build our businesses, each answer reveals new unknowns. User research is a fast, reliable way to answer important questions like these. It’s the best way to test assumptions without the time or expense of launching. It reduces risk and helps your team work more quickly and more confidently. And best of all, you can start doing user research in just a few days. We’ll show you how with the day-by-day guide below. Research makes great design possible At GV, we help startup teams use design to answer questions and make important decisions about their businesses and products. We developed this four-day research process to fit into five-day design sprints, our own battle-tested process for prototyping and testing ideas rapidly. But doing this kind of research is by no means dependent on doing a design sprint. The process we’re about to walk you through, which we’ve optimized to provide maximum learning as quickly as possible, is called a research sprint, and we’ve helped more than 300 startups use it to learn more, make better decisions, and move faster. We’ve optimized mobile-app registration, improved e-commerce conversion rates, made dense medical data clear, validated product-market fit and much more. In the next four articles (linked below), we’ll provide a complete guide to running your own research sprints. Why research sprints are so important Most startups know that they don’t have all the answers, so they rush to launch things and see how they perform in the real world. This is a very high-fidelity way to answer questions, but it’s hard and slow. Here’s the “launch and iterate” model that’s popular in Silicon Valley: But in practice, it’s a tough way to operate. You may start with a bad idea (obviously you don’t know it’s bad yet). Building it takes longer than expected — it’s tough to fix all the bugs, make sure it works in production, and get the details right. It’s difficult to “un-launch” a feature, especially once you have people using it. Real-world results are rarely as clear as you hope. And there’s always the temptation to move on to the next shiny object instead of diligently iterating on the original idea. At GV, design sprints have helped us to invent and prototype ideas. Research sprints are an essential part of this process — it’s how we test ideas without the time or expense of launching. In the time it takes to build and launch a new product or feature, you can run several research sprints and improve your prototype after each one. Instead of launching something that might not work, you’ll have confidence in the solution you’ve refined through research. Then you can invest the time to build and launch your product or feature the right way. It’ll reduce risk and save time in the long run. What can you learn from research sprints? Research sprints are not a panacea. They won’t help you learn how many people clicked a button, where your website traffic is coming from, or how to structure your database. But research sprints can help you answer some of the toughest, most important questions startups face: Who are your target customers? What specific characteristics distinguish your target users? What problems, needs, and motivations do people have? How do people evaluate and adopt products? Do people understand your product’s value proposition? And how do they respond to it? Which messages are most effective at explaining your product? Can people figure out how to use your product? Why do people stop using your product? Why don’t people adopt new features when you launch them? There are many more questions we can answer with research sprints, but these are just the essentials to get you started. Components of a research sprint There are five essential components of a research sprint. 1. A set of questions and assumptions. Without these, you’re not making the most of your effort. Before starting the sprint, everyone on the team should agree on the questions you plan to answer and the assumptions you plan to test. 2. Intentional and selective recruiting. You’ll need to carefully recruit people based on your goals: existing customers, prospective customers, representative customers, etc. In other words: Unless you’re building a product for Starbucks customers, you shouldn’t randomly conduct interviews with people at Starbucks. 3. A realistic prototype you can test. You can learn a lot by listening to people, but you can learn much more by seeing how they react to a realistic prototype. The more realistic, the better — you want people’s real reactions to what you’re building, not their abstract thoughts or smart-sounding feedback. (Check out some real prototypes we built in one day each. ) 4. Five 1-on-1 interviews combining broad discovery questions with task-based evaluation of a prototype. 1-on-1 interviews (in person or remotely) are the best-bang-for-your-buck type of qualitative research. You’ll learn from facial expressions, gut reactions, and body language. You can ask follow-up questions and follow interesting tangents. Why five? It’s easy to spot patterns, and you can do five 60-minute interviews in one day. We’ll help you write an interview guide that keeps you on track during the interviews. (Watch this 7-minute video for a quick demo of what these interviews look like: How to Test Prototypes with Customers: The Five-Act Interview. ) 5. Real-time summarization of findings. One thing that slows down many forms of research is the analysis — it can take days or weeks to extract findings from the data. In a research sprint, the entire team watches the interviews, takes notes, summarizes the findings, and decides on next steps before heading home for the day. The four days As promised, a research sprint takes just four days. We’ve written up a complete, detailed guide to each day. As a side note: in some rare cases, a research sprint can take longer than four days if you need more time to recruit an especially hard-to-find group of customers.
Updated June 2021

The founders and designers we
You use this word too often, consider replacing it with
work
with in the Google Ventures (GV) portfolio have
This phrase/word is too simple and can be replaced with:
a lot of
You use this word too often, consider replacing it with
important
You use this word too often, consider replacing it with
questions
. Is there a market for my
You use this word too often, consider replacing it with
product
? Will my
You use this word too often, consider replacing it with
product
You use this word too often, consider replacing it with
help
You use this word too often, consider replacing it with
people
solve their problems? What should I
You use this word too often, consider replacing it with
build
? The
You use this word too often, consider replacing it with
answers
to these
You use this word too often, consider replacing it with
questions
This phrase/word is too simple and can be replaced with:
just
raise more
You use this word too often, consider replacing it with
questions
: Do
You use this word too often, consider replacing it with
people
understand my
You use this word too often, consider replacing it with
product
? Will
You use this word too often, consider replacing it with
people
find my
You use this word too often, consider replacing it with
product
useful? Can
You use this word too often, consider replacing it with
people
This phrase/word (depending on the context) can be potentially replaced with :
use
my
You use this word too often, consider replacing it with
product
? And
This phrase/word is too simple and can be replaced with:
so
it continues. As we
You use this word too often, consider replacing it with
build
our businesses, each
You use this word too often, consider replacing it with
answer
reveals new unknowns.

User
You use this word too often, consider replacing it with
research
is a
This phrase/word is too simple and can be replaced with:
fast
, reliable way to
You use this word too often, consider replacing it with
answer
You use this word too often, consider replacing it with
important
You use this word too often, consider replacing it with
questions
like these. It’s the best way to
You use this word too often, consider replacing it with
test
assumptions without the
You use this word too often, consider replacing it with
time
or expense of launching. It
This phrase/word (depending on the context) can be potentially replaced with :
reduces
This phrase/word (depending on the context) can be potentially replaced with :
risk
and
You use this word too often, consider replacing it with
helps
your
You use this word too often, consider replacing it with
team
You use this word too often, consider replacing it with
work
more
quickly
and more
confidently
.

And best of all, you can
This phrase/word (depending on the context) can be potentially replaced with :
start
doing user
You use this word too often, consider replacing it with
research
in
This phrase/word is too simple and can be replaced with:
just
a few days. We’ll
This phrase/word (depending on the context) can be potentially replaced with :
show
you how with the day-by-day
You use this word too often, consider replacing it with
guide
below.

Research
You use this word too often, consider replacing it with
makes
great
You use this word too often, consider replacing it with
design
possible

At GV, we
You use this word too often, consider replacing it with
help
startup
You use this word too often, consider replacing it with
teams
This phrase/word (depending on the context) can be potentially replaced with :
use
You use this word too often, consider replacing it with
design
to
You use this word too often, consider replacing it with
answer
You use this word too often, consider replacing it with
questions
and
You use this word too often, consider replacing it with
make
You use this word too often, consider replacing it with
important
decisions about their businesses and
You use this word too often, consider replacing it with
products
. We developed this four-day
You use this word too often, consider replacing it with
research
You use this word too often, consider replacing it with
process
to fit into five-day
You use this word too often, consider replacing it with
design
You use this word too often, consider replacing it with
sprints
, our
This phrase/word (depending on the context) can be potentially replaced with :
own
battle-
This phrase/word (depending on the context) can be potentially replaced with :
tested
You use this word too often, consider replacing it with
process
for prototyping and testing
You use this word too often, consider replacing it with
ideas
rapidly
.
This phrase/word is too simple and can be replaced with:
But
doing this kind of
You use this word too often, consider replacing it with
research
is by no means dependent on doing a
You use this word too often, consider replacing it with
design
sprint.

The
You use this word too often, consider replacing it with
process
we’re about to walk you through, which we’ve optimized to provide maximum learning as
quickly
as possible,
is called
a
You use this word too often, consider replacing it with
research
You use this word too often, consider replacing it with
sprint
, and we’ve
This phrase/word (depending on the context) can be potentially replaced with :
helped
more than 300 startups
This phrase/word (depending on the context) can be potentially replaced with :
use
it to
You use this word too often, consider replacing it with
learn
more,
You use this word too often, consider replacing it with
make
better decisions, and
This phrase/word (depending on the context) can be potentially replaced with :
move
faster. We’ve optimized mobile-app registration,
This phrase/word (depending on the context) can be potentially replaced with :
improved
e-commerce conversion rates, made dense medical data
This phrase/word (depending on the context) can be potentially replaced with :
clear
, validated product-market fit and much more.

In the
next
four articles (linked below), we’ll provide a complete
You use this word too often, consider replacing it with
guide
to running your
This phrase/word (depending on the context) can be potentially replaced with :
own
You use this word too often, consider replacing it with
research
sprints.

Why
You use this word too often, consider replacing it with
research
You use this word too often, consider replacing it with
sprints
are
This phrase/word is too simple and can be replaced with:
so
This phrase/word is too simple and can be replaced with:
important


Most startups know that they don’t have all the
You use this word too often, consider replacing it with
answers
,
This phrase/word is too simple and can be replaced with:
so
they rush to
You use this word too often, consider replacing it with
launch
things and
This phrase/word (depending on the context) can be potentially replaced with :
see
how they perform in the real world. This is a
This phrase/word is too simple and can be replaced with:
very
high-fidelity way to
You use this word too often, consider replacing it with
answer
You use this word too often, consider replacing it with
questions
,
This phrase/word is too simple and can be replaced with:
but
it’s
This phrase/word (depending on the context) can be potentially replaced with :
hard
and slow.

Here’s the
You use this word too often, consider replacing it with
“launch
and iterate” model that’s popular in Silicon Valley:

This phrase/word is too simple and can be replaced with:
But
in practice, it’s a tough way to operate. You may
This phrase/word (depending on the context) can be potentially replaced with :
start
with a
This phrase/word (depending on the context) can be potentially replaced with :
bad
You use this word too often, consider replacing it with
idea
(
obviously
you don’t know it’s
This phrase/word (depending on the context) can be potentially replaced with :
bad
yet
). Building it takes longer than
This phrase/word (depending on the context) can be potentially replaced with :
expected
— it’s tough to
This phrase/word (depending on the context) can be potentially replaced with :
fix
all the bugs,
You use this word too often, consider replacing it with
make
sure it works in production, and
This phrase/word (depending on the context) can be potentially replaced with :
get
the
This phrase/word (depending on the context) can be potentially replaced with :
details
right. It’s difficult to “
Possible spelling mistake found.
un-launch
” a
You use this word too often, consider replacing it with
feature
,
especially
once you have
You use this word too often, consider replacing it with
people
using it. Real-world results are rarely as
This phrase/word (depending on the context) can be potentially replaced with :
clear
as you hope. And there’s always the temptation to
This phrase/word (depending on the context) can be potentially replaced with :
move
on to the
next
shiny object
instead
of
diligently
iterating on the original
This phrase/word (depending on the context) can be potentially replaced with :
idea
.

At GV,
You use this word too often, consider replacing it with
design
You use this word too often, consider replacing it with
sprints
have
This phrase/word (depending on the context) can be potentially replaced with :
helped
us to invent and
You use this word too often, consider replacing it with
prototype
You use this word too often, consider replacing it with
ideas
.
You use this word too often, consider replacing it with
Research
You use this word too often, consider replacing it with
sprints
are an essential part of this
You use this word too often, consider replacing it with
process
— it’s how we
You use this word too often, consider replacing it with
test
You use this word too often, consider replacing it with
ideas
without the
You use this word too often, consider replacing it with
time
or expense of launching.

In the
You use this word too often, consider replacing it with
time
it takes to
You use this word too often, consider replacing it with
build
and
You use this word too often, consider replacing it with
launch
a new
You use this word too often, consider replacing it with
product
or
You use this word too often, consider replacing it with
feature
, you can run several
You use this word too often, consider replacing it with
research
You use this word too often, consider replacing it with
sprints
and
This phrase/word (depending on the context) can be potentially replaced with :
improve
your
You use this word too often, consider replacing it with
prototype
after each one.
Instead
of launching something that might not
You use this word too often, consider replacing it with
work
, you’ll have confidence in the solution you’ve refined through research.

Then you can invest the
You use this word too often, consider replacing it with
time
to
You use this word too often, consider replacing it with
build
and
You use this word too often, consider replacing it with
launch
your
You use this word too often, consider replacing it with
product
or
You use this word too often, consider replacing it with
feature
the right way. It’ll
This phrase/word (depending on the context) can be potentially replaced with :
reduce
This phrase/word (depending on the context) can be potentially replaced with :
risk
and save
You use this word too often, consider replacing it with
time
in the long run.

What can you
You use this word too often, consider replacing it with
learn
from
You use this word too often, consider replacing it with
research
sprints?

Research
You use this word too often, consider replacing it with
sprints
are not a panacea. They won’t
You use this word too often, consider replacing it with
help
you
You use this word too often, consider replacing it with
learn
how
This phrase/word is too simple and can be replaced with:
many
You use this word too often, consider replacing it with
people
clicked a button, where your website traffic is coming from, or how to structure your database.
This phrase/word is too simple and can be replaced with:
But
You use this word too often, consider replacing it with
research
You use this word too often, consider replacing it with
sprints
can
You use this word too often, consider replacing it with
help
you
You use this word too often, consider replacing it with
answer
This phrase/word is too simple and can be replaced with:
some
of the toughest, most
You use this word too often, consider replacing it with
important
You use this word too often, consider replacing it with
questions
startups face:

Who are your target customers?

What specific characteristics distinguish your target users?

What problems, needs, and motivations do
You use this word too often, consider replacing it with
people
have?

How do
You use this word too often, consider replacing it with
people
evaluate and adopt products?

Do
You use this word too often, consider replacing it with
people
understand your
You use this word too often, consider replacing it with
product’s
value proposition? And how do they respond to it?

Which messages are most effective at explaining your product?

Can
You use this word too often, consider replacing it with
people
figure out how to
This phrase/word (depending on the context) can be potentially replaced with :
use
your product?

Why do
You use this word too often, consider replacing it with
people
This phrase/word (depending on the context) can be potentially replaced with :
stop
using your product?

Why don’t
You use this word too often, consider replacing it with
people
adopt new features when you
You use this word too often, consider replacing it with
launch
them?

There are
This phrase/word is too simple and can be replaced with:
many
more
You use this word too often, consider replacing it with
questions
we can
You use this word too often, consider replacing it with
answer
with
You use this word too often, consider replacing it with
research
You use this word too often, consider replacing it with
sprints
,
This phrase/word is too simple and can be replaced with:
but
these are
This phrase/word is too simple and can be replaced with:
just
the essentials to
This phrase/word (depending on the context) can be potentially replaced with :
get
you
This phrase/word (depending on the context) can be potentially replaced with :
started
.

Components of a
You use this word too often, consider replacing it with
research
sprint

There are five essential components of a
You use this word too often, consider replacing it with
research
You use this word too often, consider replacing it with
sprint. 1
. A set of
You use this word too often, consider replacing it with
questions
and assumptions. Without these, you’re not making the most of your effort.
This phrase/word is too simple and can be replaced with:
Before
starting the
You use this word too often, consider replacing it with
sprint
, everyone on the
You use this word too often, consider replacing it with
team
should
This phrase/word (depending on the context) can be potentially replaced with :
agree
on the
You use this word too often, consider replacing it with
questions
you plan to
You use this word too often, consider replacing it with
answer
and the assumptions you plan to
You use this word too often, consider replacing it with
test. 2
. Intentional and selective recruiting. You’ll need to
carefully
recruit
You use this word too often, consider replacing it with
people
based on your goals: existing
You use this word too often, consider replacing it with
customers
, prospective
You use this word too often, consider replacing it with
customers
, representative
You use this word too often, consider replacing it with
customers
, etc.
In other words
: Unless you’re building a
You use this word too often, consider replacing it with
product
for Starbucks
You use this word too often, consider replacing it with
customers
, you shouldn’t
randomly
conduct
You use this word too often, consider replacing it with
interviews
with
You use this word too often, consider replacing it with
people
at Starbucks.

3. A realistic
You use this word too often, consider replacing it with
prototype
you can
You use this word too often, consider replacing it with
test
. You can
You use this word too often, consider replacing it with
learn
a lot by listening to
You use this word too often, consider replacing it with
people
,
This phrase/word is too simple and can be replaced with:
but
you can
You use this word too often, consider replacing it with
learn
much more by seeing how they react to a realistic
You use this word too often, consider replacing it with
prototype
. The more realistic, the better — you want
You use this word too often, consider replacing it with
people’s
real reactions to what you’re building, not their abstract thoughts or smart-sounding feedback. (
This phrase/word (depending on the context) can be potentially replaced with :
Check
out
This phrase/word is too simple and can be replaced with:
some
real
You use this word too often, consider replacing it with
prototypes
we built in one day each.
Loose punctuation mark.
)


4. Five 1-on-1
You use this word too often, consider replacing it with
interviews
combining broad discovery
You use this word too often, consider replacing it with
questions
with task-based evaluation of a
You use this word too often, consider replacing it with
prototype
. 1-on-1
You use this word too often, consider replacing it with
interviews
(in person or
remotely
) are the best-bang-for-your-buck type of qualitative
You use this word too often, consider replacing it with
research
. You’ll
You use this word too often, consider replacing it with
learn
from facial expressions, gut reactions, and body language. You can ask follow-up
You use this word too often, consider replacing it with
questions
and follow interesting tangents. Why five? It’s easy to spot patterns, and you can do five 60-minute
You use this word too often, consider replacing it with
interviews
in one day. We’ll
You use this word too often, consider replacing it with
help
you write an
You use this word too often, consider replacing it with
interview
You use this word too often, consider replacing it with
guide
that
This phrase/word (depending on the context) can be potentially replaced with :
keeps
you on
This phrase/word (depending on the context) can be potentially replaced with :
track
during the
You use this word too often, consider replacing it with
interviews
. (
This phrase/word (depending on the context) can be potentially replaced with :
Watch
this 7-minute video for a quick demo of what these
You use this word too often, consider replacing it with
interviews
look like: How to
You use this word too often, consider replacing it with
Test
You use this word too often, consider replacing it with
Prototypes
with
You use this word too often, consider replacing it with
Customers
: The Five-Act
You use this word too often, consider replacing it with
Interview
.
Loose punctuation mark.
)


5. Real-time summarization of findings. One thing that slows down
This phrase/word is too simple and can be replaced with:
many
forms of
You use this word too often, consider replacing it with
research
is the analysis — it can take days or weeks to extract findings from the data. In a
You use this word too often, consider replacing it with
research
You use this word too often, consider replacing it with
sprint
, the entire
You use this word too often, consider replacing it with
team
This phrase/word (depending on the context) can be potentially replaced with :
watches
the
You use this word too often, consider replacing it with
interviews
, takes notes, summarizes the findings, and decides on
next
steps
This phrase/word is too simple and can be replaced with:
before
heading home for the day.

The four days

As promised, a
You use this word too often, consider replacing it with
research
You use this word too often, consider replacing it with
sprint
takes
This phrase/word is too simple and can be replaced with:
just
four days. We’ve written up a complete, detailed
You use this word too often, consider replacing it with
guide
to each day. As a side note: in
This phrase/word is too simple and can be replaced with:
some
rare cases, a
You use this word too often, consider replacing it with
research
You use this word too often, consider replacing it with
sprint
can take longer than four days if you need more
You use this word too often, consider replacing it with
time
to recruit an
especially
This phrase/word (depending on the context) can be potentially replaced with :
hard
-to-find group of
You use this word too often, consider replacing it with
customers
.

IELTS essay The GV research sprint: a 4-day process for answering important startup questions

Essay
  American English
29 paragraphs
1061 words
5.0
Overall Band Score
Coherence and Cohesion: 5.5
  • Structure your answers in logical paragraphs
  • ?
    One main idea per paragraph
  • Include an introduction and conclusion
  • Support main points with an explanation and then an example
  • Use cohesive linking words accurately and appropriately
  • Vary your linking phrases using synonyms
Lexical Resource: 5.5
  • Try to vary your vocabulary using accurate synonyms
  • Use less common question specific words that accurately convey meaning
  • Check your work for spelling and word formation mistakes
Grammatical Range: 5.5
  • Use a variety of complex and simple sentences
  • Check your writing for errors
Task Achievement: 6.0
  • Answer all parts of the question
  • ?
    Present relevant ideas
  • Fully explain these ideas
  • Support ideas with relevant, specific examples
Labels Descriptions
  • ?
    Currently is not available
  • Meet the criteria
  • Doesn't meet the criteria
Recent posts





Get more results for topic:
  • The GV research sprint: a 4-day process for answering important startup questions