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
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
.
What do you think?
  • This is funny writingFunny
  • I love this writingLove
  • This writing has blown my mindWow
  • It made me angryAngry
  • It made me sadSad

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

Essay
  American English
29 paragraphs
1061 words
5.5
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