►
Description
This video shows how to use a survey tool to create an interview script, use that script to take notes, and then use those notes to create distilled insights in 10min!
A
Hello-
I
was
talking
with
somebody
recently
about
this
idea
of
kind
of,
like
lean,
ux
research
and
doing
the
least
amount
of
research
needed
in
order
to
be
as
fast
as
possible
to
your
insights,
especially
with
like
the
data,
collection
and
data
summary,
because
I
know
that
can
take
a
lot
of
time.
So
I
wanted
to
kind
of
show
one
example
of
how
to
be
really
efficient
in
just
your
methodology
of
asking
the
questions
you
need
to
ask,
but
just
doing
everything
in
a
really
fast
and
kind
of
easier
way.
A
From
start
to
finish,
so
I'm
going
to
use
google
forms
for
this,
but
just
to
start
so
I
you
can
use
a
survey
tool
like
google
forms
or
qualtrics
to
put
in
your
script.
Basically,
so
you
can
put
in
blocks
of
text
for
what
you,
as
the
researcher
or
interviewer,
is
going
to
say
and
you
can
make
sure
to
include
pauses
just
like
any
other
script
and
then
you
can
go
through
and
I
create
a
first
section
or
block
or
page
or
whatever.
A
It
is
just
of
the
beginning
information
that
I
need
for
every
single
person,
and
I
end
it
with
a
mandatory
question
of
pressing
record.
This
means
that,
in
order
to
get
to
the
next
stage
of
all
my
questions,
I
need
to
make
sure
to
press
the
button
hit
record
and
in
order
for
me
to
do
that,
that's
going
to
always
remind
me
to
ask
the
the
person,
if
it's
okay
to
record
and
to
hit
record
and
then
you
could
just
go
through
and
put
in
each
question.
A
You
want
to
ask:
I
go
through
and
usually
put
required
on,
all
of
them
just
to
make
sure
I
don't
forget
which
questions
like
you
know,
just
in
case
I'm
skipping
around,
but
you
can
also
just
choose
which
ones
you
want
is
required
or
optional,
and
you
can
go
through
and
pretty
quickly
say.
If
you
want
it
to
be
a
short
answer
or
a
long
answer.
Multiple
choice
check
box
drop
down
all
of
those
sorts
of
things.
If
you
don't
know,
the
easiest
option
is
always
just
to
do
a
long
answer
text.
A
But
if
you
do
think
you
kind
of
do
understand,
you
need
to
know
like
this
one.
This
is
a
code
quality
research
and
we
are
asking
whether
these
people
use
code,
quality
tools
on
their
entire
repository,
a
single
project,
multiple
projects
and
so
on
and
so
forth.
So
I
we
knew
that
there
was
going
to
be
a
couple
of
options
that
they
were
going
to
talk
about.
So
I
listed
those
options.
A
I
knew
that
it
was
only
going
to
be
one
of
them,
so
I
made
sure
it
could
only
be
one
of
them
and
in
google
forms
and
most
other
things
you
can
include
an
option
or
another
for
additional
text
that
you
can
write
in
as
you're
giving
this.
So
what
you
do
is
you
you
have
all
of
these.
You
write
all
of
your
questions.
A
A
I
like
to
do
it
as
just
a
note
on
my
desktop
that
just
has
the
url
that
says
you
know
code
quality
script
and
that
way
you
know
if
I
remember
freaking
out
the
last
minute
and
say
like
oh,
my
gosh,
I
need
to
prepare
for
my
interview.
All
I
have
to
do
is
hit
that
url.
It
pops
open
this
view
of
the
google
form
and
I'm
ready
to
go,
and
I
need
everything.
Everything
is,
is
all
good
and
then
the
real
benefit
of
this
or
any
real
survey
tool
comes
in
the
responses.
A
If
it's
a
pretty
quick
interview-
and
this
works
for
in
any
sort
of
interview
that
you're
asking
semi-open
or
open
questions
that
you
do
have
some
feeling
of
an
answer
to
it-
won't
really
work
for
things
like
completely
understanding
a
workflow.
If
you
don't
understand
any
of
it,
because
that's
going
to
be
something
where
you're
going
to
basically
have
the
user.
Take
you
on
a
journey.
So
that's
going
to
be
a
lot
more
different
from
user
to
user,
but
basically
any
other
type
of
question
or
research.
A
You
should
be
able
to
answer
in
this
format
just
because
you're
going
to
be
guiding
them
through
each
question
and
as
you
do
it,
you
get
used
to
what
the
notes
are
going
to
be
and
what
the
answers
are.
So
you
can
get
better
at
your
note
taking
as
well,
so
you
can
be
see
like
I.
I
realized
that
it
was
happening
every
commit,
so
I
started
to
notice
the
theme
of
it
just
being
every
commit,
so
I
became
much
faster
at
taking
notes
for
each
one.
A
That's
fine
like
this!
So
now
I
have
each
question.
I
asked
to
each
person
here
in
each
answer
right
here.
So
then
what
I
do
is
I
take.
I
put
the
extra
column
right
here.
I
put
it
as
summary
and
you
could
like
freeze
the
first
two
columns.
You
know
if
you
want,
which,
if
you're
dealing
with
like
a
lot,
you
know
that
can
make
it
easier
because
then
you
can
just
keep
going
through
and
just
keep
annotating
for
each
whoops,
not
that
for
each
question.
A
And
then
you
just
copy
them
right
there
and
I
usually
like
to
have
it.
If
you
have
two
screens,
you
can
have
two
different
screens,
it's
all
csv,
so
I
just
kind
of
copy
and
paste
and
then
I'll
just
like
delete
it
later,
but
you
have
the
data
right
there.
So
it's
all
on
one
screen,
and
you
say
you
know
this
question:
if
you,
if
you
format
everything
correctly,
so
you
have
your
sections
so
for
us
we
had
our
goals
needs
and
our
workflow
of
our
sections
for
our
questions.
A
That's
we
answered
those
questions
and
asked
them
in
the
same
order.
So
all
of
this
is
the
exact
same
order
and
they're
all
grouped
together.
So
for
the
question
for
this
question,
I
look
at
the
answers
that
I
need.
I
create
the
insights.
I
write
it
in
a
way
that
makes
sense
to
my
stakeholders
and
then
you
can
transfer
that
information
to
dovetail
so
and
then
you
know
class,
you
know
for
dovetail.
You
can
link
the
other
issue,
link
other
things.
You
need
as
needed.
A
This
can
be
a
much
faster
way
to
get
at
it.
In
order
to
summarize,
I
think,
nine
to,
I
think
it
was.
I
think
it
was
nine
people
it
took
me,
I
believe,
a
total
of
two
hours
to
summarize
all
of
that
for
interview
data.
I
also,
if
you
don't
remember
certain
things
I
you
can
go
in
and
annotate
for
your
notes.
A
What
time
you
think
that
question
was
answered
in
the
interview,
so
that
can
kind
of
help
you
go
back,
because
you
can
always
check
your
data
before
and
validate
things
as
well
same
thing
to
you
know,
just
say:
go
and
read
back
or
listen
back
for
that.
If
you
don't
know
so,
it
took
me
about
three
hours
for
interview
data,
which
is
a
lot.
That's
gosh,
less
than
a
quarter
of
the
time
that
it
would
take
to
go
tag.
A
Everything
summarize
and
distill
those
tags
and
then
bring
those
insights
and
then
really
distill
those
insights
into
something
to
put
into
the
issue
so
yeah.
If
you
want,
you
can
do
this
for
real
any
survey
tool,
all
the
tools,
don't
really
matter,
because
it's
all
just
google,
you
know
just
sheets
just
csv
files.
A
So
as
long
as
any
tool
can
you
can
upload
or
download
that
you
should
be
able
to
use
this
same
sort
of
format
and
as
long
as
you
have
a
survey
tool
that
can
export
in
csv,
you
can
use
this
method
as
well.
So
yeah
there
you
go.
This
isn't
any
sort
of
formal
thing
in
gitlab.
This
is
just
a
handy
tool
that
I've
started
to
use.