►
From YouTube: 2019 07 11 Release UX Research Engagement
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
A
How
will
you
pace
with
our
features,
so
Laurie
I
think
you
know
we
just
kind
of
started.
Integrating
with
you
and
I
felt
like
we
needed
to
do
a
synchronous
meeting
with
the
Argus
group
to
see
okay.
What
do
we
have
on
your
plate?
Do
you
know
what
the
priority
is?
Do
you
have
everything
you
need
and
even
giving
us
some
coaching
on
how
to
engage
with
you
a
little
bit
better.
B
No
I
appreciate
that
yeah,
Mike
and
I
were
talking
just
the
other
day
about
that,
and
this
is
perfect.
It's
only
my
first
month
here
so
I'm
still
getting
used
to
can
I
call
a
meeting
came
to
me,
or
is
it
just?
You
know
to
put
it
in
the
issue,
so
I
appreciate
this
Karina
very
much
so
I've
been
here,
mufe
I'm,
also
working
in
the
ops
in
the
secure
areas
as
well
as
defend
whenever
it
comes
online.
So,
unfortunately
you're
not
my
only
team
that
I
get
to
work
with.
B
Fortunately,
as
I
get
to
learn
everything
else,
but
I've
got
to
balance
everything
as
well
as
what
you
guys
have
for
me
in
terms
of
research
and
our
like
the
not
the
perfect
process,
but
what
we
just
what
we
strive
to
do
is
we
would
like
to
do
the
research
milestone
before
you
need
to
consume
it,
because
we
want
to
give
you
time
to
be
able
to
consume
it.
It
will
take
us
a
month
to
do
a
research
project
most
of
the
time.
B
The
main
time
it
that
is
chewed
up
is
with
recruiting,
because
we
need
to
find
people
to
talk
to,
and
it
just
takes
time
to
do
it.
I've
done
it
for
years.
I
can't
do
it
faster
than
two
weeks
unless
it's
like
car
loans
and
you
can
go
to
the
Starbucks
and
find
somebody,
but
if
it's
really
technical
people
it
just
takes
time.
So
what
we
would
like
to
do
is
like
we
strive,
you
do
a
kickoff
call
or
a
sync
around
the
8th,
their
7th
of
the
month.
B
B
So
we
also
kickoff
recruiting
because
again
it's
going
to
take
like
two
weeks,
and
so
while
the
recruiting
go,
is
going
we're
I'm
working
with
you
guys
to
refine
those
questions
and
the
discussion
guide,
and
things
like
that.
So
once
we
get
people
scheduled,
begin
hop
right
into
doing
the
sessions
with
them,
and
then
we
do
the
sessions
and
typically
from
what
I
understand
they're
about
half
an
hour
long
here,
I've
done
hour-long
sessions
before
other
places.
B
If
we
have
things
that
are
very
small
pieces
like
that
small
tile,
like
a
small
thing,
to
get
feedback
on,
that
might
be
like
a
10
or
15
minute
discussion.
What
we
can
do
is
put
a
couple
of
those
together
and
do
a
longer
session
with
somebody
that
that's
perfectly
fine,
the
only
trick
is.
We
have
to
be
talking
to
the
right
people
in
that
session.
So
sometimes
what
you
want
to
find
out
is
from
a
different
persona
than
the
one
that
the
other
thing
is
needing
to
be
found
out
for
them.
B
So
that
just
complicates
it,
because
we
can't
use
the
same
recruit
it
just
it
just
takes
more
time.
For
that
kind
of
thing,
so
then
we
do
our
sessions
and
then,
by
the
end
of
the
month,
before
the
last
day
of
the
month,
usually
like
that
last
week,
you'll
get
another
invite
from
me
for
the
wash-up
meeting,
where
we
kind
of
go
over
what
we
learned
and
the
insights
and
stuff
too
and
like
I,
told
the
incident
management
team.
When
we
do
this
sessions,
I
really
highly
encourage
all
of
y'all.
B
To
show
up,
be
my
note
takers
be
there
to
listen
to
what
the
customers
are
saying.
Even
if
there
are
internal
people
they're
still
our
customers
right
so
I
would
love
for
you
guys
to
come.
I'll
send
you
separate
invites
so
what
I
do
is
I
send
an
invite
to
the
customer,
so
they
have
like
a
little
standalone,
invite
for
their
themselves
and
I.
B
Welcome
those
questions
that
come
from
your
perspective
and
you
know
other
things
that
are
going
on
that
I
may
not
be
aware
of
so
maybe
we
can
work
that
question
in
or
something
like
that,
so
I'm
totally
open
to
that
kind
of
thing
as
well
and
then
usually
after
each
session,
I
like
for
people
to
stick
around
three
to
five
minutes,
who've
observed,
does
this
chat
say
like
what
you
guys
think?
Would
you
like
what
was
like
the
aha
moment
of
that?
B
Do
we
want
to
change
anything
for
the
next
session
and
change
a
question
or
put
a
new
one
in
things
like
that?
So
do
a
little
retro,
really
quick
retro
after
each
session
and
yeah,
so
that
that's
kind
of
my
process
in
in
the
UX
research
teams
process
here,
as
as
it
is
now
good
change,
but
that's
what
we're
doing
now
so.
A
When
you,
when
we
close
out
that
and
we
do
the
retro-
is
there
sort
of
an
outcome
or
a
recommendation
from
you
as
far
as
around
the
persona,
or
is
it
just
for
collecting
information
you're
helping
us
pull
it
together?
Your
help,
you,
your
expertise,
is
rooting
through
the
right
questions
and
approaching
the
questions
the
right
way
so.
B
B
You
should
do
these
things,
and
this
is
why
you
should
do
those
things
and
what
I
like
to
do
is
if
I
can
to
beyond
what
we're
doing
a
list
of
quick
wins:
go
change
these
tiny
little
things
right
now
you
make
people
happy,
and
here
are
some
long-term
things
that
you
might
have
to
plan
a
little
bit
longer
for
it's,
not
a
label
change
or
something
like
that.
They're
do
bigger
pieces
and
then
typically,
there's
like
a
whole
nother
group
of
things.
B
Other
things
we've
learned
that
will
probably
feed
into
other
stuff
from
the
product
manager
perspective,
just
not
very
specific
features
that
were
clear.
That
came
out
of
the
research,
so
that's
part
of
it.
So
each
one
of
those
becomes
an
issue
and
get
lab
and
it
kind
of
gets
attached
to
the
research
issue
or
epic,
depending
on
how
we
want
to
organize
stuff,
so
it
kind
of
all
gets
in
there,
and
then
we
can
talk
about
them
there.
We
can
talk
about
them
in
a
meeting.
However,
you
guys
want
to
continue
those
conversations.
Okay,
very.
B
Think
it's
the
research
team
for
the
user
personas
now
I
see
that
there's
some
marketing,
personas
I'm,
not
sure
who
built
those
but
I,
also
know
that
the
designers
have
helped
with
some
of
the
persona
stuff
too
I.
Think
like
the
jobs
to
be
done,
and
things
like
that
that
they've
contributed
to
that.
So
it's
kind
of
a
joint
effort
but
I
think
it
ultimately
falls
on
the
UX
research
teams
lap
to
make
sure
it's
got
what
it
needs
and
it's
accurate
and
it's
there
because
I
notice,
it's
not
there.
B
C
C
Large
is
the
group
that
were
actually
interviewing
and
that's
like
question
number
one
and
based
on
your
answer,
question
number
two
would
be.
How
do
we
know
like
this
is
the
right
direction,
because
I
mean
we
have
so
many
different,
personas
or
subject
that
were
aiming
you
know,
but
to
use
the
tool
or
specific
stage
and
I
mean
it
differs
between
whoever's
getting
the
answer.
B
Exactly
yeah
I,
because
I
watched
that
one
video
Karina
that
you
put
up
on
Google,
Docs
or
YouTube
yeah,
so
typically,
what
you
would
want
is
around
five
to
six
people
per
persona.
Now.
That
being
said,
it
also
depends
on
your
priority,
for
the
feature
I
mean.
Sometimes
you
are
going
to
make
that
feature
for
everything
everyone
is
going
to
use
it.
Okay,
it's
all
the
people,
but
sometimes
a
feature
is
really
going
to
be
focused
on
this
one
persona
initially
and
that's
fine.
B
So
I
would
encourage
the
product
managers
here,
those
ladies
to
look
at
the
features
and
see
what
is
your
gut
telling
you?
What's
the
industry
telling
you
who
would
be
our
target
market
for
that
MVC?
Initially,
let
us
go
talk
to
those
people
and
then
we'll
know,
maybe
the
second
version
and
the
third
version
who
those
people
would
be
and
as
we
pull
them
in
for
other
studies.
I
can
take
that
information
and
talk
to
them
about
it,
so
you
don't
have
to
necessarily
wait.
B
C
C
A
What
are
the
things
when
we
talk
about
the
different
personas
and,
like
you
said,
trying
to
bring
to
focus
in
and
I
think
what
you
were
referring
to?
My
video
was
the
tech
best
way.
The
dichotomy
of
how
get
lab
has
really
been
developer.
First,
persona,
yeah
and
I
I
ran
in
against
it
as
I
started
to
break
open.
Some
release
manager
features
in
the
sense
of
developers
were
kind
of
saying:
hey.
No,
this
you
can't
mess
with
they
get
tags
like
this
like
this.
A
Is
it
doesn't
make
sense
for
us
you're
going
to
confuse
us,
and
so
my
goal
is:
is
that
as
we
crack
open
this
release
manager
persona
and
features
around
it?
I
don't
want
to
trample
on
our
most
valuable
customer
right.
I
want
I,
want
to
keep
the
peace
and
make
sure
that
I'm
serving
the
release
manager
but
I'm
keeping
that
developer
perspective
in
place
and
I
don't
know.
If
that's
me,
we
have
to
articulate
but
I,
just
in
general,
that's
what
I'll
be
focusing
on
when
we
start
to
crack
open
these
non
developers,
personas
sure.
B
Sure
no
I
totally
get
it
and
it
may
be
that
we
know
that
developer
persona
more
than
we
do
these
non
developer
personas
in
it,
and
it
may
be
that
we
don't
need
to
talk
to
them
about
everything
we
may
already
know
really
what
they
need,
but
we
don't
know
what
this
release
persona
release
manager
needs.
We
don't
know
what
the
other
ones
need,
so
maybe
focusing
on
those
in
the
initial
stages
and
then
pulling
them
all
together
later
or
just
asking
some
internal
people
to
some
internal
does
hey
what?
A
That's
good
advice,
I
think
that's
kind
of
what
happened
last
time.
It's
like
we
have
community
speak
up.
We
had
developers
speak
up
like
this,
wouldn't
make
sense
to
me
so
yeah,
maybe
that's
the
best
route
for
larger
things.
We
might
take
a
linear
like
an
antagonist.
You
sort
UX
research
to
the
realistic
search,
I,
don't
know,
but
yeah.
A
D
C
I
I
understand
what
we're
going
to
do
right
now
for
like
the
closest
releases,
and
we
have
concrete
issues
that
we
want
to
start
researching.
Thinking
about
the
bigger
picture
we
have
a
few
user
community
and
that's
coming
up
is
that
something
that
we
want
to
push
there
to
the
customers,
even
like
different
questionnaires,
are
different.
B
Yeah
we
could
yeah
I
I've,
actually
asked
Christy
our
UX
director
to
see
what's
going
on
with
that,
because
I'm
like
a
little
customers
all
in
one
place,
that's
awesome.
I
want
my
hands
on
all
of
them
right
exactly
yeah.
We
were
talking
about
like
some
specific
swag
for
UX
research
and
things
like
that
and
I
mean
I
would
love
to
be
able
to
grab
a
couple.
B
We
were
using
Survey
Monkey,
but
we're
moving
to
a
different
tool,
but
we
might
be
able
to
still
use
Survey
Monkey
for
at
least
the
first
customer
event,
but
editing
rate
we
could
like
give
them
a
QR
code.
Go
to
take
the
survey
get
a
little
scrunchy
or
whatever
we've
going
on.
We
can
send
it
to
him
yeah,
but
that's
a
great
idea
and
I'm
I'm,
hoping
that
we'll
be
able
to
to
do
something
like
that.
But
if
I
can't
go
or
anybody
here
on
the
UX
team
can't
go.
I
have
no
problem
with
you.
A
C
My
any
feature
priority,
meaning
if
it's
one
of
the
direction
features
if
it's
an
OPR,
if
it's
top
priority,
the
UX
research
should
go
it's
a
priority.
Listen
of
course,
probably
the
most
of
the
things
don't
fall
into
that
like
really
organized
category,
in
which
I
guess,
Karina
and
I
would
need
to
agree.
Yeah.
A
Some
of
them
were
toppling
on
to
a
couple
of
issues
that
probably
are
combined,
and
the
expectation
are
supposed
to
achieve
out
of
those
is
not
clear
so
just
to
confirm
what
I
have
I
have
merged
trains
run
books,
the
NBC
dashboard,
and
is
there
something
else
I'm
missing,
I
had
feature
flags.
I
know
you
want
to
do
UX
research
for
future
Flags,
two
three.
E
A
So,
where
we
stand
today,
Laurie
we
have
these
four,
it's
gonna
take
you
a
month.
You
have.
Other
teams.
Is
your
capacity
to
take
one
thing
only
at
a
time
from
us
or
do
you
feel
like
you
have
room
for
two
or
like
what
is
your
capacity
just
even
in
a
really
like,
let's
just
think
of
it
as
like,
a
release
I'm
thinking
about
that?
Getting
that
information
just
synthesized
and
time
for
yeah
the
next
release.
B
B
Balance
that
with
all
of
the
the
recruiting
and
stuff
so
I
would
say
one
now,
and
that
doesn't
mean
that
I
can't
help
I'm,
hi,
Anna
or
Mike
do
like
a
usability
test
or
a
survey
or
something
else.
I
can
mentor.
And
you
can
you,
ladies,
do
mentor.
You
guys
doing
research
as
well.
So
that's
that's
working
that
in
but
one
solo
project,
all
on
me
per
month,
I
think
is,
is
good
for
right
now,
until
I
get
into
it
more
I
suspect
it
probably
won't
change,
but
we
are
hiring
I.
D
B
Holly
also
has
her
own
group
of
things
that
she's
been
working
on
too,
so
it's
yeah
and
Katherine's
got
like
four
different
groups,
she's
working
with
as
well.
So
it's
we're
all
we
all.
We
don't
have
enough
people
to
be
honest
with
you.
We
just
yeah
yeah.
We
just
we
just
don't,
and
so
that's
that's
a
problem,
but
that
doesn't
mean
like
that's
one
project.
B
That
doesn't
mean
it's
one
topic
so,
like
I
said
earlier,
if
they're
small
bite-size
things
that
I
can
fit
in
hours
worth
of
sessions,
don't
do
them
because
I
can
recruit
once
for
it
for
that
session
and
that's
cool.
We
just
have
to
determine
the
prior
month,
which
ones
these
are
and
do
we
have
assets.
If
we
need
anything,
do
we
have
all
the
stuff
that
we
need
to
do
those
sessions
for
that
next
month
and
and
I'm?
B
E
Awesome
to
hear
because
I
think
most
of
the
the
h's
that
we
have
a
finale.
Yes,
we
need
a
lot
of
your
availability
there,
but,
for
example,
a
usability
test
we
can
tackle
ourselves,
but
I
need
is
like
help
putting
the
survey
together
or
at
least
know
it
to
look
in
the
right
direction.
I
think
that's
where
the
mecca
for
it's
going
to
happen
between
us,
but
I.
Think
if
most
of
the
things
it's
really
a
bit
of
better
planning
because
of
this
nation's
that
I
open.
E
It's
like
I
know
that
you
need
research
for
this.
We
already
have
something
even
developed.
That's
why
one
of
them
is
like
a
suggestion
for
a
method
testing.
But
how
do
you
move
forward
with
this
like?
How?
How
do
you
even
tackle
research,
because
I
have
never
done
it
would
get
laughs?
I
didn't
care,
train
wants
anyone
to
say
she
mentored
me
and
I.
Did
it
myself,
but
it
would
be
awesome
to
discuss
or
case
don't
have
to
help
if
I
need
a
scope
for
yeah.
B
Yeah
I'm
totally
happy
to
help
you
like
refine
the
hypothesis,
the
objectives,
the
questions,
the
script,
that
I'd
probably
even
do
the
recruiting
for
you.
If
that
would
be
okay,
since
we've
got
access
to
our
tool
and
I,
don't
think
you
guys
do
yet
I'll
be
happy
to
do
that
and
then
I
can
even
run
one
of
the
sessions
for
you
high
on
it.
B
So
that's
the
kind
of
mentoring
I'm
offering
for
you
and
my
kin,
and
you,
ladies
too,
if
you
want
to
get
into
user
research,
so
yeah,
so
you
can
feel
comfortable
and
then,
as
we
go
on
more
and
more
you,
you
need
me
less
and
less,
but
yeah
I
don't
want
to
leave
you
in
in
a
way
that
you're
not
you're.
Unsure
of
what
to
do.
C
B
Yeah,
there's
we're
gonna,
have
a
call
today
with
Qualtrics,
which
is
our
new
tool
that
we're
going
to
use
for
surveys
and
stuff
and
I
want
to
ask
them
about
the
site.
Intercept
survey,
I've
used
it
at
Rackspace
and
basically
it's
like
one
of
those
little
pop-ups
and
you
could
put
like
one
or
two
questions
in
there
and
say
like
how's
it
going
what
you
know.
What
other
feedback
would
you
like
to
give
us
that
kind
of
thing
and
we
couldn't
propagate
that
throughout
the
whole
at
least
the
whole
web
version?
A
I
do
have
another
call
coming
up,
I
had
I
have,
but
I
wanted
to
just
kind
of
be
like
it
Chris
with
you
guys
on
what
I
think
the
next
action
is
and
and
where
we
go
from
here
and
I,
read
I,
think
you
and
I
should
group
together,
get
our
stories
and
then
roll
and
then
basically
Rica
Munich
ate
that
out
they
how
we're
gonna
attack
the
limited
resources
we
have
and
how
we
want
to
approach
check.
Well,.