►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everyone,
so
my
name
is:
will
lighthizer
I'm
a
senior
ux
researcher,
and
today
I'm
going
to
be
talking
about
different
tips
that
you
can
use
to
maximize
your
participant,
recruiting
efforts
across
your
studies.
A
A
So
as
I'm
recruiting,
I'm
asking
myself
a
set
of
questions,
many
of
which
you
see
there
on
the
slide.
So
you
know,
am
I
using
the
right
tool
to
get
participants?
How
do
I
know
if
I
getting
the
right
participants
if
you're
asking
yourself
some
of
those
same
questions,
then
this
presentation
might
be
useful
to
you.
A
So
the
goal
of
this
discussion
is
really
to
provide
just
some
high
level
general
tips,
because
a
lot
of
these
tips,
if
you
put
them
into
use,
can
really
help
reduce
headaches
later
on.
And
what
I'm
referring
to
are
things
like
situations
where
you
feel
like
you
need
to
do
additional
rounds
of
recruiting
because
you're
not
getting
the
right
data
the
first
time
around
or
feeling
like
you're,
getting
participants
that
don't
really
match
what
you're
looking
for
so
you're
having
to
throw
them
out
and
kind
of
start
from
scratch.
A
We
do
have
a
laundry
list
of
different
resources
internally
and
externally,
so
everything
that
I'm
covering
today
is
only
scratching
the
surface.
This
could
be
like
a
semester-long
course
that
I
could
teach
on
just
this.
One
topic
so
feel
free
to
check
out
those
links.
If
you
have
time
so
my
first
tip
this
is
kind
of
an
obvious
one,
knowing
your
potential
users-
and
this
is
something
that
the
first
presentation
touched
on.
A
A
And
first
you
want
to
really
understand
that
deeper
representation
of
the
user
that
you're
trying
to
target.
So,
first,
you
can
discuss
with
other
team
members
about
that
target
user
kind
of
going
through
an
exercise
to
figure
out
okay,
who's,
the
persona
or
who's
the
type
of
user
that
uses
this
type
of
feature
within
git
lab.
You
can
also
leverage
existing
data
that
you
might
have
within
dovetail
or
user
testing,
and
then
we
also
have
information
specific
to
different
personas.
A
So
if
you
know
that
you
want
to
target
system
admins,
we
already
have
you
know
personas
around
that
and
then
stuff,
like
our
doc
site,
also
has
useful
information
as
well,
so
this
screenshot
that
I
have
from
the
doc
site.
Provided
me
some
interesting
information
around
the
backup
and
restore
task
which
showed
me
that
you
know
git
lab.
This
is
for
self
managed
users
only.
So
this
helps
me
know.
Okay,
these
are
the
people
that
I
need
to
recruit
for
the
the
study.
A
So,
if
no
information,
you
know
existing
information
exists,
you
can
kind
of,
like
I
said,
before-
collaborate
in
different
ways
through
like
a
mural
board
which
have
been
shown
a
couple
times
throughout
this
larger
discussion
and
then
also
having
like
an
issue
that
you
build
out
with
other
people
and
and
have
more
of
an
async
discussion
about
who
that
persona
is
next.
My
second
tip
is
around
finding
the
right
balance
with
survey
screener
length.
A
So
when
I'm
talking
about
screeners
by
definition,
the
questions
should
screen
out
anyone
who's
not
qualified
to
participate
in
your
study.
So,
as
you
develop
those
questions,
you
should
really
figure
out.
Okay,
what
questions
will
really
help
me
get
to
the
target
users
that
I'm
trying
to
get
to
and
which
ones?
I
might
not
necessarily
need
to
ask
like
things
that
are
not
necessarily
screening
anybody
out.
Those
types
of
questions
could
be
eliminated
altogether
or
just
included
in
your
main
set
of
study
questions.
A
Also,
if
you're
looking
for
a
very,
very
specific
type
of
user,
you
know,
of
course,
you're
going
to
need
more
questions,
typically
to
get
that
through
the
screener
keeping
in
mind.
There
are
some
limitations
around
that
in
some
cases,
so
for
user
testing,
for
example,
you
can
only
add
up
to
six
screener
questions
for
a
study
and
then
in
general,
the
longer
a
screener
survey
goes.
A
A
There
are
some
additional
workarounds
to
this,
though,
within
some
of
the
tools
that
we
use
so
for
user
testing,
for
example,
it
allows
filters
that
I've
included
a
screenshot
here,
where
you
can
specify
different
things
that
are
known
about
their
panel
and
that
can
help
reduce
some
questions.
A
One
thing
I
would
note
here
is
that
for
something
like
current
role,
especially
right
now,
that's
being
called
like
the
you
know
the
great
resignation
you
know,
people
are
constantly
changing
jobs,
changing
careers.
A
A
Well,
the
one
reason
I
bring
this
up
around
obscuring
screener
questions.
Is
that
there's
a
very
small
percentage
of
users
who
use
you
know
our
different
platforms,
user,
testing,
user,
zoom
respondent,
other
platforms
as
well
that
are
not
100
truthful
when
they're
answering
those
screener
questions,
so
there
are
some
people
trying
to
gamify
those
and
trying
to
get
the
incentive
by
providing
what
answers
they
think
the
researcher
wants
to
hear.
A
A
A
better
example
to
ask
that
type
of
question
would
be
to
say
which
of
the
following
tools:
do
you
primarily
use
for
devops
and
then
kind
of
listing
those
out,
so
some
of
the
ways
that
this
example
helps
a
little
bit
better
than
to
use
gitlab
is
that
the
question
does
not
give
away
the
desired
answer.
So
when
you
read
to
use
gitlab,
you
automatically
think
well,
they're,
probably
going
to
want
somebody
with
get
lab
experience
for
this
type
of
study
and
then
for
this
question.
A
Another
example
is:
how
familiar
are
you
with
gitlab
the
way
we've
worded
this
and
some
of
the
response
options
that
you
see
underneath
are
kind
of
biased,
as
you
saw
in
the
the
previous
question,
so
we're
probably
looking
for
someone
who
has
some
familiarity
with
gitlab
a
better
way
to
do
this
would
be
to
ask
you
know
how
familiar
or
unfamiliar
are
you
with
gitlab?
It
doesn't
automatically
give
away
that
we're
trying
to
look
for
someone
with
familiarity,
but
it
it
provides
kind
of
different
ends
of
that
spectrum.
A
So
that's
a
good
way
to
just
see.
Okay,
what's
what
is
my
participant
group?
You
know
what's
their
experience
level
with
get
lab,
because
you
may
be
doing
a
study
where
you're
wanting
to
get
at
learnability,
so
you
might
want
to
per
se
participants
that
are
not
as
familiar
with
it
and
then
you
might
be
doing
other
studies
where
you
want
people
that
are
super
familiar
with
gitlab
then.
My
final
example
here
is:
do
you
have
experience
with
merge
requests?
A
A
So.
This
gives
a
couple
of
good
examples
of
ways
to
improve
your
existing
screener
questions
and
then
my
final
tip
that
I'm
going
to
cover
here
is
being
skeptical
when
reviewing
data
from
potential
participants,
and
so
since
we
know
that
participants
in
some
cases
are
trying
to
gamify
screeners,
it's
good
to
have
a
keen
eye
when
looking
at
some
of
that
data
that
we're
getting
back
from
the
screeners
so
trying
to
look
for
inconsistencies
or
unexpected
responses,
things
that
don't
really
match
up
based
on.
A
You
know
what
we'd
expect
to
see
for
that
potential
participant,
so
I've
included
some
examples
there
of
things
to
keep
in
mind
as
you're.
Looking
through
that
information,
so
some
of
the
best
practices
that
you
can
use
when
reviewing
that
data
is,
you
know,
examine
a
participant
against
the
rest
of
the
participants
that
you
know
fit
into
that
target
group.