►
From YouTube: CI & PA UX Research Planning on 2020-10-14
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
welcome
to
this
week's
cipa
ux
research
planning
session.
I
think
nadia
s
may
be
joining
later.
She
has
an
item
on
the
agenda,
but
we'll
get
started
so
our
usual
two
questions.
What
research
issues
are
in
progress
and
then
also
what
are
the
upcoming
problem
validation?
A
I
did
nadia
had
one
about
problem
validations
listed
under
ux
research,
so
I
moved
it
down
there
so
for
the
one
agenda
item
2
for
the
ux
research
in
progress,
we
just
kicked
off
me
and
vitika
talking
about
it.
Yesterday,
the
research
I'm
calling
it
ux
research
on
the
key
metrics
for
analyzing
pipelines,
but
it's
really
also
going
to
be
first
synthesizing.
A
What
research
has
already
been
done
on
pipeline
metrics?
I
think
there's
even
a
link
to
a
customer
interview
as
well
on
what
pipeline
metrics
are
valuable
to
them.
I
had
a
question
for
lori
on
that.
I
found
in
a
slack
thread
that,
when
nadia
reached
out
september
23rd
to
to
jackie
about
what
what
the
release
team
has
done
so
that
we
can
leverage
those
findings,
jackie
had
shared
a
link
to
a
customer
interview.
A
In
dovetail,
I
was
going
to
add
it
to
the
description
of
my
research
issue,
but
I
know
our
research
issues
eventually
become
change
from
confidential
to
no
longer
confidential.
In
that
case,
should
I
not
link
to
the
dovetail
recording
of
that
customer
call
or.
B
No,
you
can.
The
dovetail
access
is
just
for
people
at
gitlab.
So
even
if
somebody
clicks
it
they're
not
going
to
be
able
to
see
it
unless
they
have
a
seat
and
we're
only
giving
people
who
worked
at
the
company.
So
you
should
be
okay
and
you
can
just
say
it
like
internal
link
only
and
the
when
you
put
it
in
there
too,.
A
Okay,
all
right
so
I'll
add
that
to
the
the
description
of
our
ux
research
and
and
laura
since
so
that's
good
to
know,
customers,
even
they
click
on
link.
They
can't
get
access,
but
I
think
I'll
just
call
it
customer
call
instead
of
naming
the
customer
right,
because
we
don't
even
want
to.
B
A
Yeah,
okay,
so
I'll
just
put
link
to
customer
call
about
metrics,
okay,
thanks
lori
for
that
perfect,
so
I
think
if,
after
we
had
a
chance
to
kind
of
digest,
all
of
the
research
that's
been
done
today
take
into
account
those
suggestions
if
vitica-
and
I
realize
that
we
do
want
to
do
a
little
bit
of
live
interview
with
customers
we'll
do
it
out
of
that
same
issue
as
well.
A
If
there's
something
that
comes
up-
and
I
don't
know,
there's
there's
we're
trying
to
decide
between
ten
metrics
and
narrow
it
down
to
five,
and
we
couldn't
find
a
specific
findings
about
which
of
those
ten
were
even
most
valuable,
we'll
we'll
do
some
recruiting
and
and
interviewing.
I'm
super
excited
about
this.
The
work
that's
already
been
done.
I
know
it
wasn't
related
specifically,
but
it's
it's
pretty
relevant.
A
So
that's!
What's
in
progress,
I
saw
there
are
some
discussions
with
kenny
and
the
two
other
pms
in
verify
in
slack,
and
I
redirected
them
to
add
their
comments
to
this
issue
so
that
we
can
keep
it
long-term.
Knowing
that
slack
conversations
are,
I
think,
90-day
temporary
until
they're
wiped
yeah
yeah.
B
B
B
A
B
A
No,
that
makes
that
makes
sense.
I'll
probably
go
do
that
right
now,
thanks
laurie.
Let's
see,
I
think
if
it's
the
it
says
that
I'm
trying
to
to
short
shortcut.
B
A
A
A
Okay,
okay,
gotcha
sounds
good,
so
I
guess
we
can't
have
confidential,
maybe
once
it
promotes
it,
it
automatically
makes
it
unconfidential,
but
I
think
we
could
still
make
epics
confidential
I'll
I'll
play
with
it
I'll
play
with
it,
and
if
I
can't
make
a
combination
I'll
go
through
and
scrub
it
and
kenny's
already
adding
stuff
to
it
all
right.
Thanks
for
that
suggestion,
lori
go
back
and
do
that
next,
any
other
discussion
we
want
to
have
on
that.
A
C
C
We
we,
like,
we
said
that
at
the
beginning,
let's
talk
to
our
existing
user
first
to
understand
like
what's
their
experience,
but
then
again
emily
asked
me
again
if
we'd
like
to
interview
actually,
should
we
validate
that
we
only
want
to
interview
gitlab
users,
and
then
I
thought
maybe
we
should
like
use
the
same
problem
validation
and
extend
it
and
interview
also
like
non-gitlab
users,
maybe
just
slightly
modify
it
a
bit
with
some
of
the
questions
and
then
see
if
the
like,
where
all
the
gaps,
but
originally
we
started
with
this
research
targeting
only
gitlab
users.
C
B
So
jove,
I
know
you
shared
the
issue
with
me
and
I
apologize.
I
haven't,
got
a
chance
to
to
read
through
it
yet,
but
it
sounds
so
just
so.
I
know
I
heard
you
right.
It's
not
your
fault,
make
sure
I
was
listening.
You
and
nadia
want
to
talk
to
internal
git
lab
no.
C
B
Okay,
all
right,
I
just
wanted
to
make
sure
that
that
was
the
thing,
so
that
makes
perfect
sense.
I
I
do
wonder
so,
as
you
know,
as
you,
you
guys
know
andre
and
I
are
trying
to
talk
to
people
who
don't
use
git
lab,
but
do
do
ci
pipelines
in
jenkins
circle,
ci
and
github
and
travis
and
getting
their
take
on
the
offering
process.
B
I
wonder
if
you
could
use
any
of
this
like.
I
want
to
make
sure
that
what
we're
asking
them
is
very
similar
to
what
you
and
nadia
want
to
learn
from
current
users,
because
we
should
solicit
very
similar
question
feedback
from
the
from
the
questions
from
people,
because
the
goal
I
would
assume
is
still
the
same:
how
how
is
it
working
for
them?
B
You're
talking
to
people
who
are
doing
it
and
have
some
experience
with
it,
we're
talking
to
people
who
have
not
yet
used
our
tool
to
do
it,
but
the
questions
should
be
very,
very
similar,
so
I'd
like
to.
I
will
look
at
that
issue
after
this
meeting
this
morning,
but
I'd
like
to
collaborate
on
on
that
research
in
those
respects,
because
I
think
it's
very
very
similar,
in
fact
like
you-
could
also
argue
that
we
could
be
talking
to
those
people
for
our
research.
But
we
just
don't
have
enough
time
to.
B
Yeah,
one
of
the
things
you
might
want
to
take
into
consideration
dove
is
the
level
of
experience
the
people
you
talk
to,
will
that
you
want
them
to
have
with
git
lab
and
with
ci
pipelines
in
particular
thinking
how
many
pipelines
do
you
need
them
to
have
been,
have
created
or
modified?
B
How
recently
do
you
need
them
to
do
that?
I
found
that
a
lot
of
people.
I
talk
to
don't
go
in
there
and
fiddle
with
the
pipelines
that
much
they're
set
up
at
some
point
in
the
fut
in
the
past,
and
they
just
run
until
something
breaks,
and
then
somebody
has
to
go
in
there
and
change
it,
but
they
don't
tend
to
change
their
code
enough
to
change
pipelines
frequently.
So
that
might
be
a
question
that
you
want
to
ask
and
think
about
the
type
of
person
you
want
to
talk
to.
B
C
Another
question
that
I've
debated
like
I
think
I
have
like
the
answer,
but
I
just
want
to
throw
it
out
so,
like
the
type
of
organization.
A
C
B
Okay,
I
don't
know
if
this
would
validate
that
for
you,
if
you're
asking
them
to
give
you
feedback
on.
C
A
It
depends,
I
think,
if
you're
going
after,
like
enterprise
size
customers,
most
of
them
are
not
using
get
lab
sas
they're
using
self-hosted
self-managed.
So
were
you
going
to
limit
your
research
to
users
of
our
gitlab.com?
A
Okay?
In
which
case
I
don't
know,
I
think
it
might
be
good
to
get
a
variety
from
each
area,
because
I
think
their
problems
are
going
to
be
different.
I
know
problems.
The
really
complex
pipelines
tend
to
be
with
very
large
customers
that
are
also
trying
to
make
it
easier
for
more
teams
within
the
organization
to
edit
and
author
pipelines,
which
is
very
different
from
your
much
smaller
companies.
C
That's
that's
for
sure,
and
I'm
I'm
pretty
sure
we'll
get
like
different
response
from
different
enterprise,
like
the
question
is
like
normally,
when
you
do
this,
when
you
do
research,
do
you
aim
for
the
large
enterprise
or
the
small
medium.
A
C
B
Yeah
yeah,
I
was
just
going
to
say
I
I
would
agree
with
tal.
I
think
you
might
need
to
talk
to
both
their
practices
are
so
widely
different
in
enterprise.
You
tend
to
have
more
specific
jobs
like
like.
You
can
be
much
more
specialized
in
large
enterprises
where,
in
the
small
and
medium
business
you
might
have
one
or
two
people
doing
everything,
and
so
they
have
a
different
set
of
goals,
challenges
versus
the
enterprise
level
as
well.
B
So,
like
you
love
enterprise,
you
tend
to
have
a
lot
more
devops
teams
right
because
they
that's
just
they
have
the
ability
and
the
money
and
the
budget
to
have
devops.
So
devops
is
setting
up
pipelines
for
somebody
else,
they're
not
even
using
the
pipelines
that
they
create,
but
small
medium
business.
They
may
be
devops
but
they're
also,
probably
coding
the
code
too,
so
they're
setting
up
their
own
pipelines
and
using
it.
So
the
question
is:
do
you
need
to
talk
to
people
who
create
pipelines
on
behalf
of
others?
B
And
do
you
also
need
to
talk
to
people
who
create
pipelines
for
their
own
immediate
use
instead
of
creating
it?
On
behalf
of
other
people,
I
would
say:
you'd
want
to
talk
to
both
because
both
bring
unique
challenges
to
the
situation
and
as
a
product
that
is
trying
to
be
everything
to
everybody.
We
want
to
make
sure
that
we
get
both
of
those
perspectives.
A
I'm
looking
through
your
screener
is
your
question
so
that
you
can
edit
a
certain
screener
question
to
get
a
specific
customer
size.
C
Yeah,
like
what's
the
company
size
or
the
team
size
that
can
be
like
because,
like
there
are
cases
where
you
have
like
a
large
enterprise,
but
the
team
is
operating
like
like
small,
like
if
it's
like
a
very
small
team,
and
usually
they
operate
as
like,
like
a
mini
startup.
If
it's
a
large
team,
then
normally
they
would
work
as
as
a
large
enterprise
and
agree,
I
mean.
C
Ideally,
we
want
to
talk
to
both
and
obviously
we'll
get
like
different
answers
and
different
points
of
inspection
from
from
both
types
of
customers,
and
the
only
concern
that
I
have
is
that
I'll
have
so
many
unknowns
or
so
many
things
that
I
can
work
on
and
because
of
the
variety
of
the
answers
that
I'll
get.
C
It
will
be
hard
for
me
to
understand,
like
what
is
a
problem
that
we
need
to
that
you
need
to
tackle
and
what
is
it,
but
maybe
it's
because
of
the
way
I
structure
this
research,
because
I
I
see
that
from
this
research
there
will
be
like
plenty
of
other
problem
validations
that
we
will
do
because
a
lot
of
those
questions
are
very
general
to
questions,
and
we
did
it
in
purpose
mean
idea,
because
we
are
also
doing
our
first
steps
in
this
world.
C
B
That
should
give
you
a
good
sense
of
am
I
hearing
consistent
things
from
these
two
groups
and
if
you're
not,
let's
chat,
because
it
might
mean
you
need
to
pull
in
like
a
two
or
three
more
people
for
each
group.
Just
so
you
can
get
some
consistent
answers,
but
I
think
five
and
five
would
be
a
good
start.
A
Hey
dove,
I'm
looking
at
your
the
draft
screener
as
well,
linked
to
from
your
research
issue.
A
I
think
you
might
just
specifically
ask
them:
how
have
you
interacted
with
pipelines
and
then
you
know
option
a
I.
I've
offered
them
from
from
scratch.
India
option
b,
which
is
I've
edited
a
little,
but
you
know,
and
then
option
c
could
be
both
or
something.
Oh
wait
are
these
check
boxes
where
they
can
select
multiple
choice,
options
yeah,
because
you
want
to
pinpoint
actually
exactly
how
they
interact
with
the
pipeline.
C
A
I
think
part
of
the
screener,
because,
because
you're
going
to
talk
to
two
different
groups
of
users,
one's
that
author
from
scratch,
which
is
very
important
to
you
for
your
research
and
ones
that
just
interact
minimally
with
when
they
have
to
edit
something
then
from
the
screener,
you
can
group
those
interviews
together
closer
together,
so
that
it
it's
easier
to
keep
in
mind.
These
are
the
group.
These
are
the
five
that
truly
author
things
from
scratch
and
then
the
next
five,
for
example.
A
I'm
not
I'm
not
not
necessarily
dictating
the
number,
but
the
next
group
would
be.
These
are
the
ones
that
minimally
interact
with
it,
but
they
have
their
own
different
problems
of
hey
are
whoever
originally
author
it
now.
This
is
the
problem
of
how
I
I
can
edit
you
know
or
not,
but
if
but
if
you
add
that
as
a
screener
question,
then
you
would
know
what
type
of
use
that
is,
how
do
you
yeah?
How
do
you
interact
with
pipelines.
A
Exactly
and-
and
I
I
had
that
problem
right
lori
when
I
was
trying
to
do
research
on
ml
pipelines,
I
didn't
have
a
specific
question
like
that,
and
so
some
of
them
had
kind
of
general
knowledge
about
it,
but
they
weren't
truly
the
users
who
were
hands
on
with
creating
the
pipelines
for
for
for
machine
learning
and
ai
projects.
So
I
realized
that
was
a
big
miss
from
the
start.
In
my
screener.
A
And,
and
maybe
after
you've
interviewed
all
the
folks
that
author
pipelines
from
scratch
that
there's
so
much
detail
there,
you
want
to
defer
as
a
separate
research
the
the
users
that
only
edit
minimally
the
pipeline
and
not
actually
do
the
primary
offering.
A
Well,
well,
dove
is
taking
notes
there.
Let
me
see
what
else
is
on
our
agenda,
any
other
anything
else
you
want
to
discuss
on
that
dove,
be
I
don't
want
to
move
on
too
quickly.
A
Okay,
I
saw
nadia
linked
to
that
issue,
so
so
I
I
can
get
to
it
from
that
link
in
the
agenda
in
agenda
item
3b.
A
I
had
a
question
and
generally
for
what
all
of
you
think-
and
I
think
lori
will
probably
have
some
guidance
on
this.
I
was
going
to
separately
by
90.
I
was
going
to
separately,
do
a
problem,
validation
for
and
I
let
me
not
not
dashboard.
I
must
type
pipeline
oops
pipeline
metrics
and
I'm
like
is
it
re?
Would
it
be
at
this
point
redundant
for
me
to
do
an
additional
problem,
validation
or
just
synthesize?
The
problem
validation?
That's
already
been
done
in
the
past.
B
A
B
D
Sorry
I
was
looking
at
the
discussion
guide
for
release
teams,
research
and
it
feels
like
most
of
their
questions.
They
are
focused
around
the
tasks
that
the
release,
managers
or
people
of
like
yeah
yeah.
That
position
would.
A
Perform
okay,
in
which
case,
and
I
and
I
was
pretty
sure
they
were
focused
on
more
release
stuff,
in
which
case
I'll
just
start,
a
draft
problem,
validation,
a
an
opportunity,
canvas
vitica
and
we
can
throw
in
their
assumptions
from
their
finding
and
then
we
would
tailor
it
for
our
jobs
to
be
done
for
ci,
okay
and
so
yeah
good,
because
the
reason
I
asked
when
I
looked
at
the
other
research
issues,
other
teams
had
they
linked
to
an
opportunity
canvas,
but
that
is
tied
to
problem
validation.
A
So
I'll
just
get
one
started.
If,
in
the
end
we
decide,
we
don't
need
it,
we
can
just
close
our
our
opportunity,
canvas
okay.
So
we
can
note.
D
D
Yeah,
so
this
is
an
activity
that
I'm
trying
to
initiate,
and
I
thought
everybody
should
be
aware
of
this.
So
this
is
nothing
nothing
on
a
very
large
scale,
but
something
internal
only
kind
of
a
async
design
very
similar
to
what
the
source
code
team
had
done
very
recently
for
the
merge,
mr
widget,
for
like
the
mr
widget
sections
that
touch
upon
different
teams.
D
So
they
brought
together
all
the
ux
designers
or
the
product
managers,
and
they
got
to
drop
their
comments
like
what
they
think
could
be
improved
on
those
and
how
there's
kind
of
an
inconsistency
and
how
we
can
fill
that
gap.
And
all
of
that.
So
nothing
concrete,
has
started
on
that
front.
But
something
has
just
been
initiated,
and
that
is
all
for
now.
D
A
Any
other
questions
on
that.
I
think
we're
two
minutes
over
time.
All
right
thanks
everyone.
I
will
load
the
the
recording
of
this
to
our
playlist.