►
From YouTube: UX Group conversation
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).
B
Hey
Sara
good
good
morning:
how
do
you
think
about
the
walk?
Choose
the
flow
through
the
application.
I
was
talking
with
the
head
of
product
at
digitalocean
recently,
and
he
said
he
regularly
every
two
weeks.
He
takes
one
of
the
flows
to
the
product
and
he
works
on
that
with
another
15
feet
and
no
one
is
super
fan
of
the
approach
because
they
find
a
lot
of
things
we
is
I.
Have
the
feeling
that
UX
research
at
github
is
a
bit
a
bit
more
focused
on
connect.
B
A
So
I
think
him.
We
haven't
really
done
too
much
user
journey
mapping
and
before-
and
this
is
something
that
our
designers
are
actually
starting
to
do
so.
Andy
is
one
of
the
first
people
on
the
the
UX
design
team
to
actually
tackle
and
creating
a
user
experience
map,
and
he
started
that
by
going
through
the
process
and
with
myself
and
some
of
the
other
people
on
the
security
and
just
getting
them
to
identify
where
problems
might
be
in
the
process.
So
that
kind
of
gives
us
our
assumptions.
C
The
only
thing
I'll
add
to
that
is
I
were
doing
the
same
for
onboarding
right
now
and
I
say
we.
But
it's
not
me
in
any
way,
Mattei
has
partnered
with
his
team
to
do
the
same
for
onboarding,
so
he
started
with
a
video
to
show
the
signup
process
through
onboarding
and
do
kind
of
heuristic
review
of
current
state,
and
then
he's
also
documented.
Both
the
current
journey
and
our
proposed
proposed
journey
for
the
future.
C
D
A
B
B
C
So
I
think
we're
the
beautification
comes
in
is
looking
at
the
contrast,
so
we
actually
had
so
I
use
an
example
that
I
saw
yesterday
an
issue
that
someone
brought
up.
Some
of
our
labels
have
nice
primary
colors
as
the
background,
but
the
foreground
color
is
like
a
weird
gray.
So
that's
a
contrast
issue,
but
by
solving
that
contrast
issue
by
updating
the
text
to
white.
It's
also
a
beautification
issue
make.
E
B
B
B
F
Carol
here
from
support,
quick,
one
I
have
noticed
on
straight-6
that
increasing
the
signup
time
or
reducing
the
signup
time
is
a
top
priority,
but
in
support
I
realized
that
per
day
we
are
getting
at
least
three
tickets
of
people
who
have
like
mistyped
their
email,
like
mr.
Latta,
in
via
email
and
I,
was
wondering.
Is
there
any
idea
like
how
we
can
make
sure
that
emails
are
correct?
Most
companies
do
the
double
email,
VIN
confirm
your
email,
but
I
don't
know
if
that
will
match
up
with
the
reducing
the
signup
time.
F
C
Thoughts
on
that,
what
perfect
timing
for
you
to
ask
that
question,
because,
as
a
team
we
were
just
discussing
that
this
morning,
so
my
answer
to
you
is
I
will
pass
that
feedback
on
to
matei
who's
the
primary
designer
on
this,
and
let
him
know
that
it's
a
problem,
thank
you
so,
and
Adam
or
I.
Just
to
address
your
question
even
more,
we
should
not
be
reducing
the
signup
time
like
that,
shouldn't
be
our
priority
over
making
it
a
good
experience
where
people
don't
have
to
call
in
over
in
this
typed
email.
C
C
G
C
Okay,
cool
thanks
Dimitri,
so
we
have
a
work
in
progress
handbook,
page
right
now
for
the
design
system.
The
point
of
it
is
to
do
two
things.
So
one
is.
We
want
to
get
all
of
the
things
that
have
been
in
our
collective
heads
around
like
when
we
say
design
system.
What
does
that
mean
to
get
lab,
because
that
can
mean
different
things
to
different
companies?
So
well,
I
think
it's
it's
it's
in
our
brains.
We
need
to
get
it
out
in
writing.
It's
also
things
like.
Why
are
we
even
doing
the
design
system?
C
Why
is
it
important?
What
is
the
value
that
it
brings,
and
how
do
you
measure
success
of
a
design
system?
Part
of
it
also,
though,
is
defining
the
process
for
how
we're
gonna
push
the
design
system
forward,
because
there's
a
good
foundational
start
there,
but
there's
still
a
ton
of
work
to
do
so.
This
is
the
reason
that
it's
work-in-progress
is.
C
This
is
very
much
a
collaborative
effort
between
the
UX
team,
the
engineering
team
and
the
product
management
team
and
engineering
is,
is
looking
at
the
proposed
page
right
now
to
think
about
what
the
processes
should
be
around,
how
we
actually
implement
designs
in
view
and
how
we
manage
our
CSS
and
some
things
like
that,
but
that
should
be.
That
should
be
coming
soon.
It's
out
there
and
available
for
anyone
to
see
and
to
comment
on
we've
gotten
lots
of
good
feedback.
So
far,
your
feedback
is
very,
very
welcome.
C
H
Hi,
it's
Oliver
from
the
secular
team.
I
have
a
different
question
about
UX
research
on
our
internal
workflow
or
usages
of
gait
lab
I'm,
particularly
interested
in
to
how
we
do
project
management
here,
because
this
seems
to
be
often
a
struggle
in
our
team
and
we
often
end
up
by
having
to
use
external
tools,
because
the
current
project
management
features
in
gate
lab
doesn't
fulfill
our
needs.
So
to
do
use.
Do
you
have
something
really
focused
on
gitlab
internal
more
closed?
A
This
is
a
really
interesting
question,
because
when
I
first
started
to
get
lab,
when
we
were
much
a
smaller
company,
we
didn't
actually
do
testing
with
internal
users,
and
the
reason
for
that
is
because
our
internal
users
outweigh
our
external
users
at
the
time.
So
we
wanted
to
make
sure
that
you
know
we
were
still
similar
to
the
external
users.
A
Obviously,
that's
kind
of
change
as
the
company's
grown
and
I
also
think
as
well.
I
know
that
these
are
real
within
the
kind
of
product
department
that
an
internal
stakeholder
request
is
worth
ten
times
the
value,
and
we
haven't
actually
done
much
research
with
internal
stakeholders,
we've
only
kind
of
just
started
doing
that,
but
it's
something
that
we
would
like
to
do
more
and
if
you'd
like
to
be
involved
with
that
you've
got
any
pain
points.
Anything
that
you're
really
struggling
with
them.
Please
just
reach
out
to
myself
or
Katherine.
A
Here
is
that
cleaner,
I
think
this
is
the
thing
that's
important
with
UX
research
we
have
to
triangulate.
Our
data
we
have
to.
You
know,
make
sure
that
we're
listening
to
all
the
different
channels
of
information
and
so
we'll
make
sure
that
if
you
just
even
have
a
just
a
coffee
chat,
wheels
we'll
make
sure
your
information
gets
to
the
right
place
on
the
right
people.
B
A
Fixes
can
implemented,
I
were
actually
moving
away
from
long
written
reports,
I
think
you're
poor.
It
was
you
who
pointed
it
out
to
me
so
that
PDF
reports
weren't
very
actionable
and
we
tried
to
remove
our
reporting
into
the
the
design
system.
But
still
we
didn't
feel
like
it
was
having
much
impact
and
I
did
some
user
interviews
with
the
product
team
we
could
to
ago,
and
I
spoke
to
more
individually,
and
they
told
me
that
they
don't
actually
go
back
and
read
the
PDF
reports
that
were
produced
in
the
past.
A
They'll
read
them
once,
and
the
problem
is,
is
that
insights
and
findings
are
kind
of
being
locked
away
in
those
reports
and
being
forgotten
about,
and
so
we
know
that
we
need
to
be
utilizing
issues
more
and
at
the
same
time
we
know
that
product
managers
are
facing
a
lot
of
different
and
like
internal
communications,
they're,
getting
sales
calls
and
that's
a
bit
of
information,
overload,
I,
guess
and
I
guess
we're
just
adding
to
that
noise.
So
something
that
we're
trying
to
do
actively
more
within
research
is
move.
A
Our
researchers
to
be
more
generative
would
do
more.
Like
discovery,
research
and
the
idea
is
this-
is
that
we'd
partner
work
with
product
managers,
we
conduct
user
interviews
with
them
and
then
that
way,
we
can
actually
have
a
discussion
about
what's
happened
and
within
the
interviews
there
and
then
in
the
moment,
when
we
both
witness
the
same
things
and
that
takes
away
some
of
the
written
documentation
that
we've
been
producing.
A
It's
very
clear
that
straightaway
we
have-
and
you
know,
actionable
things
that
we
need
to
take
forward
from
there's
a
little
bit
of
documentation
that
we
need
who
are
actually
one
of
our
okay.
Ours
is
to
try
and
use
get
libraries
our
research
repository.
So
this
is
a
kind
of
hot
topic
within
the
UX
research
world
in
general.
There's
a
lot
of
researchers
out
there
that
are
struggling
to
kinda
document,
their
research
findings
and
a
lot
of
research
that
use
confluence,
who
just
don't
want
to
carry
on
using
it
anymore.
A
Who
would
like
a
better
way,
you're
kind
of
tagging
findings
and
being
able
to
search
them,
and
it's
called
like
an
atomic
research
approach.
So
it's
a
quick
way
of
writing
down
your
findings
from
studies
and
then
being
able
to
put
them
into
something
like
a
repository
tuck
them
efficiently.
So
you
might
tag
them
with
like
persona
or
stage
group
or
whatever
you
want
really
and
then
obviously,
we
already
know
that
caleb
was
a
great
search
functionality
and
so
we'd
be
able
to
pull
insights
related
to
a
particular
topic
together
and
I.
A
Think,
first
and
foremost,
the
kind
of
people
who
will
use
that
research
repository
of
probably
researchers
and
designers
and
when
they're,
trying
to
triangulate
information.
But
it's
there
for
anybody
across
gitlab.
We
know
it's
our
single
source
of
truth
about
what
I
use
as
a
talking's.
It
was
about.
B
A
We
notice
that
the
shooter
did
this
and
then
we
would
support
that
with
a
video
clip,
and
so
we
end
up
with
individual
kind
of
findings
and
then
what
we'd
be
able
to
do
is
it's
to
be
able
to
group
those
findings
together,
probably
using
an
epic
and
then
we'd
be
able
to
transfer
them
because
it
obviously
it
will
be
within
the
get
web
group
on
say,
like
a
project
managers
board.
So
then
action.
A
So,
therefore,
when
we
enter
these
and
this
data
into
the
repository
there's
a
second
step
that
we
have
to
do,
we
have
to
comb
through
all
the
research
like
that
we've
done
perhaps
over
the
last
month
and
then
pull
those
finals
together
to
be
able
to
say
confidently
like
this
is
statistically
significant
and
I.
Think
that's
the
problem
of
maybe
putting
them
straight
into
the
seee
projects.
Is
that
something
could
get
actioned
when
it
isn't
really
an
problem?
We
need
to
make
sure
that
there's
multiple
users
experiencing
the
same
thing
so.
B
So
getting
that
data,
that's
a
very
expensive
proposition
like
getting
one
case
versus
getting
so
many
cases.
It's
significant
that
you're
sure
it's
a
problem
should
we
should
we
trust
the
judgment
of
the
researchers
themselves
to
make
to
make
it
more
effective,
like
you
can
see
like
oh
well,
this
is
what
this
user
did.
They're,
probably
not
important
what
this
user
did.
This
is
probably
a
problem.
I
can
relate
to
that
or
is
that
dangerous?
Is
that
too
much
bias,
I
think.
A
It
can
be
dangerous,
I
also
think
it
depends
on
what
the
issue
is.
Sometimes
if
it's
like,
hey,
I
use
a
flow,
for
example,
people
can
do
silly
things,
they
can
do
tough
things
and
just
do
it
themselves
and
it
might
be
really
obvious
and
we
might
be
watching
it
as
researchers.
I'm
think
hey.
This
just
seems
a
bit
weird.
It
just
is
probably
just
this
person,
but
the
same
time
like
something
like
an
accessibility
issue
like
something
that
you
know.
A
One
person,
experiences
who's,
perhaps
colorblind
and
is
struggling
weird,
and
you
know
the
colors
that
we've
used
within
an
interface.
Then
we
know
that
if
one
person
is
run
into
that
problems
and
there
will
be
over
probably
other
people
who
want
into
that
issue
as
well.
So
at
that
point
as
researchers,
we
could
make
a
call
and
say
hey:
this
really
needs
looking
in
so
we've
had
one
person
experience
it,
but
we
know
colorblindness
isn't
like
it
isn't
like
what
it
isn't.
A
science
of
one
person,
sorry
I,
know
Bell,
you
know,
I
tried
something.
C
Just
I
needed
my
mic
by
accident,
so
the
only
thing
I'll
add
everything
sara
has
said
is
that
one
of
the
benefits
of
the
insights
repository
as
she's
envisioning.
It
is
to
also
extend
the
longevity
of
the
relevance
of
the
research
findings
that
we
have
so
sometimes
the
research
finding
is
isn't
relevant
to
just
one
question
or
one
user
group.
It's
something
that
should
actually
persist
over
time
that
we
should
be
able
to
go
back
and
reference
without
having
to
do
additional
research,
so
by
making
it
bite-size,
but
storable
and
cat
is
did
differently
categorizable.
C
B
I
I
So
I
added
this
to
the
agenda
dock
that
I'll
just
vocalize
it.
What
I
guess
this
question
could
be
for
both
of
you.
What
are
you
most
excited
about
in
the
upcoming
release
or
releases
you.
C
So
maybe
this
is
because
we
had
our
first
group
feedback
session
this
morning
and
matei
presented
the
sign
up
and
onboarding
flows,
but
I
am
super
excited
about
that.
He
has
some
really
innovative
ideas
for
how
we
can
make
it
easier
to
become
a
new
gift.
Lab
user
and
I
can
also
probably
empathize
with
that
even
more
because
I'm,
a
relatively
new
kit,
lab
user,
so
anecdotally
I
will
get
and
going
wow.
This
would
be
really
really
neat,
so
the
plan
is
for
that
to
happen
within
the
next
couple
of
milestones
and
I.
A
A
C
So
I
mean
I
think
it
honestly.
It
just
wasn't
clear
for
me
where
to
start
I
feel
like
I,
just
kind
of
landed
in
the
middle
of
this
really
robust,
complex
tool,
and
it
was
up
to
me
to
hunt
around
and
see
what
was
available
and
where
things
were
and
how
those
things
connected
to
each
other,
which
is
back
to
so
so
spoiler
that
well,
and
we
need
to
get
this
in
front
of
users
first
to
make
sure
that
it
makes
sense
to
them.
C
But
the
today's
idea
is
around
and
it's
imitate
in
conjunction
with
his
team.
He
would
be
very
upset
if
I
just
kept
saying,
but
a
and
didn't
say
he's
also
working
with
this
product
manager
and
other
designers,
but
he's
leading
the
effort
on
this,
but
a
guided,
onboarding
experience
where
it
actually
takes
you
through
an
issue
board
and
moving
issues
around
and
setting
things
up,
really
really.
Neat
idea
and
I.
C
D
H
Another
question
which
does
a
comment
looking
at
the
link
process,
if
I
feel
about
the
37
actions
together,
feature
yeah
I
mean
this
is
really
funny.
I
I'm
really
feeling
bad
that
we
we
don't
have
enough
time
to
go
through
all
those
kind
of
things
that
you
are
producing,
because
I
think
this
will
be
really
interesting.