►
From YouTube: CI PM/UX Research Planning on 2020-08-18
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
Okay,
so
welcome
everyone
to
our
uxci
ux
research
planning
session
before
we
start
oops
well,
actually,
let's,
let's
just
start
with
the
first
agenda
item,
this
one
is
yours.
I
think.
B
Yeah,
so
this
is
just
an
update
on
the
ongoing
research
activity.
That's
going
on,
so
I
have
started
to
interview
people
who
express
their
interest
that
they
want
to
speak
further
or
they
want
to
share
more
about
their
experience
with
dark
and
so
for.
Five
out
of
six
interviews
are
done
and,
like
very
interesting,
insights
are
surfacing
things
that
we
clearly
did
not
get
to
see
on
the
feedback
issue.
B
So
I
think
that's
a
plus
that
that
kind
of
validates
that
this
was
a
good
effort
and
it
is
helping
us
in
seeing
a
few
things
that
people
were
not
commenting
in
commenting
publicly
on
the
issue.
B
Yeah
and
some
of
the
key
insights
that
I
saw
surfacing
in
the
conversations
were
first
of
all,
I
think
three
out
of
five
so
far.
They
think
they
feel
that
dag
is
very
crucial
to
determining
which
dependencies
could
be
cut
off
to
speed
up
the
pipelines
and
that's
something
that
they're
just
not
able
to
do
at
this
point
of
time
using
the
normal
visualization,
and
so
that
was
the
reason
they
would
love
to
have
this
visualization
available
to
them.
B
And
then
we
also
talked
about
the
alternate
tools
that
are
the
alternate
methods
within
gitlab
that
they
would
otherwise
employ
to
kind
of
achieve
or
accomplish
the
same
set
of
tasks,
and
they
also
like
they
gave
a
walk
through
of
that.
They
talked
about
tools
like
graph
wiz,
and
there
was
one
more
a
custom
tool
created
by
someone
which
is
also
documented.
B
So
that
was
interesting
to
know
that
other
tools
also
exist
in
this
area
that
we
can
look
at
then
talking
about
colors
yeah.
It
did
come
up
by
itself,
even
though
there
was
not
a
dedicated
question
for
that
in
the
questionnaire,
but
still
everybody
kind
of
made
a
comment
on
the
color
that
they
are
not
very
confident
that
this
is
helping
them
in
their
workflow
and
they're
kind
of
confused
about
what
value
it
is
communicating.
B
Nobody
really
likes
to
switch
between
the
two
visualizations
which
are
available
at
this
point,
and
even
though
we
are
saying
that
we
are
providing
this
special
set
of
information
in
the
second
tab,
they
still
need
to
look
at
the
new
set
of
information
in
context
to
the
regular
set
of
information.
I
mean
they
still
want
to
look
at
the
status.
They
still
want
to
see
what
field
and
what
went
through
and
for
that
they
have
to
keep
switching
between
tabs,
which
it
is
not
a
very
desirable
experience
yeah.
B
C
B
So
when
they
look
at
colors,
sometimes
what
happens
is
they
understand
that
the
gradients
are
mostly
for
them
to
lead
from
source
to
a
target
in
terms
of
jobs,
but
sometimes
the
source
and
targets
have
the
same
color,
and
sometimes
it's
the
color
when
they
overlap
it
gets
too
messy
and
they're
not
able
to
kind
of
figure
out
if
there's
a
pipeline
at
the
back
and
which
way
the
pipeline.
B
If
there's
something
going
on
in
the
back
and
which
way
things
are
turning
and
it
it
it's
a
lot
confusing
and
because
they
have
they
were
showing
live
examples
and
they
were
clicking
and
interacting
with
the
graph.
So
it
is
very
well
documented
the
kind
of
usability
issues
they're
facing
while
interaction.
C
C
I
don't
want
to
jump
into
too
much
details,
but
this
is
this
is
super
useful
thanks,
vitica
for
sharing.
A
A
Okay,
so,
oh
okay!
So
thanks
for
adding
that,
by
the
way
what
I
did
when
I
was
reading
through
the
issues
in
my
feature
label
area,
I
created
a
new
feature
label
that
we
could
probably
use
as
it's
it's
called
pipeline.
A
A
So
here's
where
there's
overlap,
I
think
visualization
of
the
the
dag
has
the
dag,
has
its
own
feature:
label
ci
dags
that
jason
owns,
and
I
think
dag
visualization
falls
under
that.
But
if
you're
going
to
be
also
trying
to
make
the
two
of
them
work
together,
both
the
pipeline
graph
and
the
dag
visualization,
then
you're
going
to
have
to
also
consider
the
issues
under
my
feature
label,
which
is,
I
think,
it's
called
ci
graphs
and
analytics
so
I'll.
A
So,
for
example,
you
to
go
when
I
start
ranking
one
of
the
reasons
jason
and
I
create
those
separate
buckets,
so
I
can
start
ranking
them
within
the
bucket
and
then
figuring
out
where
I
need
research
to
be
done
for
some
things
that
are
not
clear
to
me
before.
I
start
scheduling
some
of
these
issues,
so
you
and
I
can
figure
out
which
one
of
those
are
also
related
to
feedback.
A
You
got
when
you're
researching
the
dag
so
that
we
don't
have
duplicate
issues
in
the
dag
feature
label
bucket,
as
well
as
in
mine.
Does
that
make
sense.
B
A
No
because
this
one
is
specific
to
I
mean
I
actually
don't
use
a
feedback
about
that,
this
specific
to
anything
that
you're
doing
to
the
dag.
But
you
were
mentioning
that
what
some
of
the
feedback
insight
you
got
was
switching
between
the
dag
visualization
and
the
regular
pipeline
graph,
because
there's
some
data
they
need
from
the
pipeline
graph
right
if
the
the
feedback,
if
you
we
decide
that
part
of
that
feedback
we
want
to,
I
don't
know
stories,
I'm
just
going
to
create
something
completely
unrelated
hypothetical.
A
Let's
say
they
wanted
the
dad
colors
to
show
up
on
the
regular
pipeline
graph
saying
for
this
job
go
to
the
blue
job
in
the
dag
view.
That
would
be
adding
something
on
the
pipeline
graph.
That
would
be
not
under
the
epic
that
you
just
shared
but
under
a
feature,
a
story
with
the
future
label
graphs
and
analytics.
A
It's
it's.
It's
tricky
right
because
there's
a
lot
of
overlap
and
it
bleeds
over
between
the
work
we
do
on
some
future
labels
and
others.
Okay,
let
me.
A
So
if
I
combine
the
two,
I
think
it
came
up
to
be
about
70
yeah,
so
this
is
feature
label
make
that
I'm
going
to
make
that
a
link
for
the
ci
graphs
and
analytics,
and
it
will
take
you
to
the
list
of
issues
under
that.
I
haven't
had
a
chance
to
prioritize
them.
Yet
this
list
of
69
issues
about
graph
and
analytics,
but
some
of
them
do
have
to
do
with
ways
that
they
want
the
pipeline
graph
to
be
improved.
A
B
A
A
Good
great
yeah,
you
could
just
ping
us
and
ask
us
which
yeah
sounds
good
is
is
also
the
insights
and
the
links
to
like
the
the
recordings
of
the
the
interviews.
Is
it
going
to
be
in
dovetail
or
is
it
in
a
research
issue
as
well.
B
I
would
put
everything
in
dovetails,
so
dr
lottery
had
a
has
a
place
for
the
dog
visualization
feedback
exercise.
I
will
just
go
and
add
all
of
these
and,
along
with
the
analysis
and
everything.
A
D
So
we're
keeping
all
of
the
research
artifacts
in
dovetail
right
now.
Now
you
can
save
it
to
your
google
drive
if
you
want,
but
if
you
want
to
look
for
like
the
project,
it's
in
dovetail,
and
so
our
research
issue
that's
raised
as
an
issue
will
reference
the
dovetail.
A
Project
so
so
my
and
then
my
next
question
is
so
the
research.
So
when
I
create
a
research
issue
for
something
that's
still
valid
in
the
past,
we
would
link
to.
We
would
put
our
notes
in
there
and
we
would
link
to
the
recording
from
the
research
issue.
But
now
the
research
issue
will
just
link
to
one
project
in
duct
tale
and
everything
else
is
there:
okay,
yeah.
D
But
we
are
okay
and
yeah,
and
then,
once
you
do
the
hard
work
of
analyzing
and
coming
up
with
your
insights,
there
is
a
process
and
adam,
I
think,
posted
the
link
to
the
page
in
the
ux
team
meeting
today
about
creating
the
actionable
insights
in
the
it's,
not
the
research
project.
It's
the
other
project,
the
one
that
you
guys
use
as
pm's
and
using
the
actual
insights
label,
and
that
just
means
like
these
are
things
that
we
have
to
take
action
on.
D
D
That
way,
which
also
means
that
the
non-actual
insights-
so
maybe
it's
just
informational,
like
nine
out
of
ten
people
like
blue,
that's
informational,
it's
not
really
something
you
have
to
take
action
on
that
will
live
right
now,
solely
inside
of
dovetail
so
dovetail
will
have
both
the
actionable
insights
because
you
create
them
there
and
the
informative
ones,
and
then
the
actionable
ones
will
get
kind
of
copied
again
manually
into
that
other
project
in
gitlab.
A
D
Did
it
for
mine
I'll
see
if
I
can
find
my
it's,
it's
super
easy.
It's
it's
just
that
one!
I
just
don't
remember
what
the
project
name
is.
Is.
A
The
is
the
the
whole
way
we
should
be
doing
it
to
incorporate
dovetail.
Is
that
captured
anywhere
in
the
handbook
or
yeah?
I
was
going
to
just
copy
okay,
I
want
to
do
it
right
and
create
rework
for
us,
but
I
haven't
done
this.
I
haven't
used
dovetail
extensively,
except
for
one
time
I
try
to
go
out
there
and
try
to
figure
out
how
to
initiate
a
recording.
Until
I
found
out
from
laurie.
You
know
you
just
record
and
zoom
you.
You
store.
D
But
if
you
don't
do
that,
you
run
the
risk
of
putting
structure
around
your
project
in
a
way
that
might
hinder
your
ability
to
do
your
data
analysis.
I
was
talking
to
dimitri
earlier
and
he
was
struggling
with
his
tags
because
you
can
come
up,
you
can
create
tags
in
the
beginning.
You
can
create
tags
during.
D
You
can
create
tags
at
the
end
and
he
was
struggling
with
how
many
tags
he
had
and
trying
to
figure
out
which
tag
went
with
what
highlight
because
you
basically
highlight
and
then
you
kind
of
tag
it
and
one
of
the
pieces
of
advice
that
I
had
for
him
was
create
the
tags
as
you
go
as
you
read
through
the
notes.
You're
like
oh,
that
deals
with
you
know,
color
something
with
color
or
color
confusion,
and
then
you
can
come
back
to
that
tag
and
use
it.
D
The
more
you
read
through
the
notes,
but
what
also
happens
is
the
more
you
read
through
the
notes,
the
more
you
tend
to
refine
the
tags.
So
now,
maybe
it's
not
color
confusion.
Maybe
now
it's
confusion
between
what
the
red
and
the
green
mean,
because
they
think
it's
like
go
and
stop
or
stop
and
go
so
then
you
can
go
back
and
change
the
tag.
You
can
add
one,
but
it's
it's
yeah.
D
It's
just
like,
and
I
didn't
expect
that
that
just
happened
to
me
when
I
was
using
it
for
the
first
time
so
go
through
make
a
little
test
project,
see
see,
get
some
familiarity
with
it
and
yeah,
and
it's
just
so
flexible,
so
don't
don't
be
afraid
to
make
it
do
what
you
need
it
to
do,
but
don't
expect
there
to
be
structure
sitting
there
already
for
you.
That's,
I
think
the
worst
part
about
the
tool.
A
You're
so
used
to
having
templates
when
we
do
issues
and
all
that
okay
yeah,
I
went
out
there
and
I
looked
at.
I
think
I
created
a
project
for
a
customer
call
that
I
was
anticipating.
I
think
I
deleted
it
afterwards.
I
didn't
know
what
I
was
doing
but
I'll
I'll
go.
You
know
what
and
I
realized
those
for
example,
those
those
interviews
we
did,
I
think,
four,
four
or
five
of
them
lori,
for
when
we
were
researching
machine
learning,
yeah
pipeline.
A
D
D
Yeah
just
play
around
with
it,
don't
worry
about
like
making
anything
for
posterity
or
anything
just
play
around
with
it
see
how
it
feels
see
what
the
flow
is
for
you,
how
you
like
to
organize
things.
You
can
also
go
into
anybody
else's
project
in
there.
You
can
click
and
see
how
other
people
are
doing
it
and.
A
B
That's
how
I'm
slowly
learning
dovetail.
I
mean,
I
still
don't
know
the
best
practices,
but
I
look
into
other's
project
and
for
tar
glory.
I
had
a
question
that
are
the
tags
project
specific
or
the
namespaces:
they
are
not.
They
do
not
get.
D
Shared
across
interesting
yeah
because
they
could
be
problematic,
but
it
could
be
good,
so
they
don't
get
shared.
There
is
a
thing
called
an
extension.
I
think
that's
what
they
call
it.
It's
a
different
kind
of
tag
and
it
lives
in
a
different
folder,
and
somebody
has
to
create
them.
But,
like
me,
like
an
admin
has
to
create
them.
Those
can
be
seen
across
projects,
but
the
navigability
to
where
they
live
is
stupid.
This
is
which
mom
put
out
there.
D
It's
like
three
layers
in
in
the
drop
down
menu,
so
it's
not
as
user
friendly
as
I
would
like
it
to
be,
and
I
don't
know
how
helpful
it
actually
would
be,
because
I
I
don't
know
if
the
meaning
of
one
tag,
even
though
it's
the
same
word,
welcome
to
english
would
mean
the
same
thing
for
another
project,
so
we
haven't
really
dived
into
that
too
much.
Yet.
B
Okay,
so
it
would
be
my
responsibility
if
I
find
something
which
is
relevant
for
some
other
team.
It
would
be
my
responsibility
to
communicate
that
to
them.
D
Yeah,
so
if,
if
it's
an
actionable
insight,
you
put
it
into
that
gitlab
project
and
you
tag
the
appropriate
people.
So
part
of
that
process
that
I
linked
to
and
the
agenda
here
is
tagging
the
pm
and
the
designer
who
are
tagged
part
of
that
effort.
So
if
it's
something
for
a
different
team
like
the
growth
team
or
something
tag,
jeff
tag
tim
or
whoever
the
pm
is,
and
they
should
be
able
to
see
that
and
then
take
action
on
it.
D
To
it-
and
you
certainly
can
like
there's
no
there's
no
proper
process,
I
think
around
artifacts
like
that.
Yet,
but
if
it's
part
of
the
project
you
want
to
keep
it
there,
I
would
you
should
you
might
want
to
also
link
to
your
mural
back
on
that
research
issue
that
you
opened
as
well
in
case
somebody
came
across
it
there,
ultimately
we're
hoping
that
we
can
export
part
of
these
dovetail
projects
back
into
our
research
insights,
repo,
I
love
ours,
but
I
don't
know
if
it
would
ever
export
that
kind
of
artifacts.
D
I
think
we're
working
on
trying
just
to
get
the
insights
push
back
in
there
so
at
least
have
something
of
record:
that's
ours.
So
it's
it's
a
little
clutchy
right
now,
a
little
all
over
the
place,
but
I
always
I
I
have
a
minor
library
science.
So
I
always
err
on
the
side
of
cross
cross
linking
everything
everywhere,
just
in
case.
A
D
Oh
I'm
already
hearing
it
multiple
source
of
truth,
yeah
yeah
well,
and
I
don't
look
at.
I
know
it's
so
weird,
so
I
look
at
dovetail
as
a
tool.
I
I
personally
don't
look
at
it
as
a
repository.
I
look
at
it
as
a
tool
to
get
to
the
end,
which
is
the
insights
we
are
store,
be
mainly
because
we're
also
still
pulling
those
actionable
ones
back
out
and
putting
them
into
a
gitlab
project,
but
we're
storing
the
informational
ones
in
there
as
well.
A
Okay,
oh
whoa,
is
this
a
half
hour
session?
It
is
okay,
yeah,
go
ahead,
yeah
number
three.
B
What
what
I'm
doing
in
the
interviews
is
people
are
generally
talking
about
how
they're,
interacting
with
the
dog
and
the
significance
of
their
action
in
context
with
their
role
in
the
company
and
what
they're
trying
to
accomplish.
So
I
think
it's
pretty
easy
to
extract
the
jobs
to
be
done
from
there.
So
what
I'm
thinking
is
I
mean,
whichever
jobs,
to
be
done.
We
extract
from
these
interviews.
We
can
go
ahead
and
document
it
in
the
gdp
document
that
we
have
created
for
ci.
B
I
mean
I'll
do
that,
so
this
is
a
good
way.
I
mean
from
each
of
the
interviews
that
we
conduct.
We
would
often
end
up
having
informations,
which
are
very
relevant
to
our
stage
group,
and
it
could
be
of
a
different
nature.
It
might
not
be
very
useful
for
that
particular
research
exercise,
but
I
mean
this
is
a
very
good
example
that
we
can
still
get
jtvds
from
the
same
interviews
and
populate
our
document.
A
B
I
was
thinking
in
the
same
cell.
We
would
put
links
to
different
issues.
C
A
B
Okay,
yeah,
I
mean
we
can
change
our
process
midway
as
well
and
depending
on
our
experience
with
interacting
with
this
job.
A
Yeah
yeah
whoa,
okay,
so
this
also
will
help
drive
what
we
put
on
our
handbook
page
for
ci,
jtbd,
right,
yeah,
yeah,
okay,
great
okay,
two
minutes
left!
Oh,
we
just
have
a
couple
announcements.
D
I
am
I'm
going
to
go
to
I
don't
they
call
them
cabins
but
they're,
not,
I
think,
they're
like
little,
I
don't
know
containers
I
reimagined.
It's
called
the
getaway
getaway.
Yes,
where
so
there
there's
some
down
near
you
and
then
there's
some
here
like
in
two
hours.