►
From YouTube: UX Research Screener Template Walkthrough
Description
Welcome to this walkthrough of how to fill out the screener template per GitLab's validation workflow: https://about.gitlab.com/handbook/product-development-flow/#validation-phase-2-problem-validation
A
Everybody's
watching
your
type
right
now
so
the
first
two
questions
are
really
standard.
It's
just
getting
people's
agreement,
so
we
can
record
them
and
share
it
with
people
like
a
lab.
So
we
need
to
keep
those
two
in
there.
It
doesn't
disqualify
them
if
they
say
no
it
just
it's
just
for
you
and
Emily
when
she
recruits
to
know.
A
So
this
is
also
the
question
where
people
tend
to
add
stuff,
especially
that
is
specific
to
their
project,
so
read
through
the
list
and
see
if
there's
something
that
we
should
add
in
here.
That's
specific
to
the
release
management.
We
just
add
it
anywhere.
You
want,
because
we
can
randomize
it
in
Qualtrics.
A
B
B
B
A
A
B
A
A
B
B
B
A
B
It
wouldn't
necessarily
exclude
them,
but
talking
to
people
who
use
our
environments-
and
then
it's
super
important
to
manually,
improve
releases
would
give
us
insight
into
how
they're
doing
that
within
at
lab.
Whereas
if
they're
not
using
it
a
lot
of
environments,
but
it's
very
important
to
orchestrate
releases
across
many
groups
or
approve
releases,
then
they
would
be
the
use
case
that
we're
trying
to
resolve
gotcha.
A
B
A
I'm
gonna
change,
my
only
approving
releases
or
from
our
promotions
to
production
is
very
important.
It
is
so
I
am
gonna
use
certain
language
down.
There
is
an
essential
part
of
my
job
and
important
to
my
company,
and
so
what
I'm
gonna
do
is
that's
like
a
Likert
question,
so
it's
like
I
agree
completely
I
somewhat,
which
serves
like
a
stamp
no.
B
A
So
then,
now
we
have
answers
that
we
can
compare
across
people
and
we've
defined
what
important
means
to
us
and
what
they
want
them
to
tell
us.
So
alright
and
I'm
gonna
do
this.
So
when
we
talk
about
frequency,
we
want
to
give
people
a
time
frame
to
think
of
it
in
so.
In
the
last
week,
in
the
last
30
days,
yeah.
B
A
B
It
would
be
I,
don't
know,
I,
don't
know,
that's
kind
of
why
I'm
asking
a
question
I'm
not
sure
like
if
we
were
to
say
that
the
ideal
is
for
people
to
be
released
into
production
whenever
they
want
at
well
from
an
engineer's
perspective
and
how
are
people
coordinating
those
releases
to
production
if
developers
are
allowed
to
release
that?
Well,
so
it
clearly
could
be
multiple
times
a
day
or
less
than
that.
So
I
think
what
you
have
here
makes
sense.
Okay,.