►
From YouTube: Create stage User Journey Map: Intro session [APAC/EMEA]
Description
Within this timezone group, various domain counterparts (Engineering Managers, Product Designers, Product Managers, Technical Writer, and/or UX Researcher) contribute to a User Journey Map (UJM) that spans the whole Create stage.
More information:
- Epic: https://gitlab.com/groups/gitlab-org/-/epics/6964
- Issue: https://gitlab.com/gitlab-org/create-stage/-/issues/12944
A
All
right,
so
thank
you,
everyone
again
for
joining.
As
I
was
saying
just
before,
we
I
started
recording
to
sean
and
david.
This
is
the
first
time
that
we're
doing
this
and
it
can
go
very
well
or
very
not
well,
and
it's
still
a
big
mystery.
What
will
come
out
of
this
and
if
nothing,
questions
and
things
to
research,
but
I
think,
or
what
I
hope
for
today
is
that
everyone
has
just
a
good
time
is
excited
about
this
and
just
shares
what
like,
how
you
feel
about
this
user
journey.
A
What
do
you
think
basically
no
no
judgment
at
the
moment
that
will
come
much
later
in
time
right
now,
he's
just
having
fun
and
outputting
ideas,
thoughts,
questions
that
you
have
okay,
so
after
before
we
get
started
what
I
really
want
to
do,
and
I
try
to
do
this
every
time
I
get
a
bunch
of
people
in
the
room
and-
and
that
is
already
familiar
with
this
every
month
when
we
do
the
prioritization
session.
A
So
what
I'm
going
to
ask
everyone
to
do
is
in
the
chat
using
the
emoji
picker
to
express
yourself
and
let
everyone
know
how
you're
feeling
today
and
I'll
do
the
same
at
the
end
of
the
session
so
that
we
can
calibrate
and
and
see
if
everyone
is
feeling
better
or
not
so
I'll.
Give
you
everyone
a
moment
to
do
that.
A
Andres
is
in
the
reflective
mood.
B
I
I
typed
it
wrong.
It's
it's
persevere,
the
emoji
for
persevere
like
prior
to
this.
I
was
like
feeling
pretty
tired,
but
I
had
a
chat
with
marcel
before
this
and
there's
a
chat
with
someone
else
and
that
actually
gave
me
a
lot
of
energy,
so
yeah,
I'm
here,
I'm
happy
to
be
here.
B
A
Yeah,
okay,
david,
I
don't
think
I
have
been
accessed
to
edit
the
mural.
Let
me
see.
A
Yeah
and
I
don't
think
you're
you've
been
given
access
to
to
edit,
but
let
me
see
if
I
so.
What
I
can
do
now
and
I
can
change
that
later-
is
that
I
will
give
anyone
with
the
link
access
to
edit.
So
let
me
paste
that
into
the
chat,
the
link,
although,
if
you
refresh
you,
might
be
able
to
try
to
type
in
one
of
the
blank
stickies.
A
Let
me
know
if
that
works
david,
all
right,
yeah,
michael
but
yeah.
Thank
you
for
sharing
and
yeah
thanks
for
being
with
us.
I
know
it's
very
late
for
you
after
dinner
time,
so
let's
try
to
make
the
best
out
of
this
time.
All
right
david
is
that
working
now.
C
A
But
what
we
will
try
to
do
if
all
of
this
is
successful,
is
to
create
more
user
journey
maps
that
are
linked
to
specific
personas
and
different
jobs
to
be
done
of
and
and
just
show
how
that
persona
is
able
to
accomplish
that
job
to
be
done
with
gitlab
and
initially
I
was
thinking
about
splitting
the
groups
by
by
stage
group.
A
So
you
would
have
a
source
code
stage
group
doing
this
activity
code
review
group
editor
group,
but
I
thought
it
would
be
much
better
to
have
a
more
diverse
audience
with
all
of
the
groups
mingled
together
and
not
thinking
about
just
their
own
future
features,
but
about
everything
that
they
know
and
that
they
think
this
persona
experiences
when
they're
trying
to
accomplish
this
job.
So
we're
just
doing
this
for
this
persona
job
to
be
done
in
the
future.
We
will
try
to
do
more
if,
if
this
is
successful,
perfect,
thank
you.
A
Okay
I'll
say,
I
think,
we're
good
to
go.
So
let
me
share
my
screen
and
here
at
the
top
of
the
mural.
Let
me
see
if
I
can
try
to
summon
everyone's
attention
to
my.
A
You
can
see
a
description
of
the
persona
that
we're
focusing
today,
and
so
this
is
sasha.
They
have
specific
motivations
and
frustrations,
and
essentially
they
are
our
main
persona,
for
I
believe
both
code
review
source
code
and
also
editor
groups,
and
this
is
the
job
to
be
done.
So
what
sash
is
trying
to
do
today
is
when
product
improvements
are
identified.
That
is
a
situation
they
want
to
propose
changes
that
address
them.
That
is
a
job
so
that
I
can
help
build
a
better
product.
A
That
is
the
ultimate
outcome,
the
desired
outcome
of
all
of
this
and
today,
what
we're
trying
to
do
first
is
brainstorm
alone
and
in
silence
the
different
steps
that
sasha
will
perform,
either
in
gitlab,
but
also
outside
of
bitlab.
So
if
there
are
things
that
you
think
some
teams
do
to
accomplish
this
job
to
be
done,
you
know,
for
example,
asking
something
in
slack
or
doing
a
pair
code
review
in
person
or
having
a
meeting
to
decide
on
the
requirements
before
starting
this
journey.
A
So
there
are
many
touch
points
that
don't
exist
necessarily
inside
of
kit
lab,
and
today
this
first
part
about
the
steps
is
salute
our
solution,
agnostic
steps.
So
an
example
here
of,
for
example,
it
could
be
for
a
music
app
is
being
solution.
Agnostic
is
determining
what
songs
to
listen
in
the
moment.
So
this
is
something
a
step
that
all
users
have
to
go
through,
regardless
of
what
product
or
service
they
are
using,
and
even
if
they're,
not
using
any
product
or
service.
A
So
we're
trying
to
think
of
steps
that
are
solution,
agnostic
and,
if
possible,
try
to
keep
to
this
structure
a
verb
object
and
optional,
contextual
clarifier.
So
in
this
case
the
determine
is
the
verb.
Then
the
object
is
what
songs
to
listen
and
the
optional
contextual
clarifier
is
in
the
moment,
but
this
is
this
is,
if
you
can
stick
to
that
better.
A
If
not,
that's
not
a
big
problem,
we
can
certainly
clean
them
up
later
and
for
this
first
step,
which
is
to
try
to
fill
up
these
stickies
here
and
you
can
duplicate
them
by
copy
pasting,
it
or
pressing
command
d,
and
it
will
paste
another
one
beside
it.
Try
to
fill
them
out
as
much
as
possible
across
all
of
these
different
stages,
and
these
are
all
you
know
like
a
checklist.
So
if
you
don't
think,
there's
anything
to
add
under
locate,
you
don't
need
to
add
it.
You
can
jump
to
the
next
one.
A
So
this
is
and
in
the
end
we
might
have
some
empty
stages
and
that's
okay,
but
try
to
fill
them
up
as
much
as
possible
and
don't
worry
if
certain
steps
are
not
in
the
ideal
stage
or
if
you
don't
think
it
belongs
to
one
or
the
other.
We
can
clean
them
up
afterwards,
and
for
this
part
I
will
give
10
minutes
and,
as
it
says,
in
the
instructions
focus
on
quantity,
not
quality
and
again.
This
is
all
just
based
on
your
thoughts.
It
doesn't
have
to
be
right,
validated
or
researched.
A
That's
that's
the
purpose
and
one
thing
that
I'll
experiment
with
today
is
to
actually
create
a.
Let
me
see
where
I
can
do,
that
is
to
create
a
private
mode
so
that
you
will
see
other
people
adding
their
thoughts
on
stickies,
but
you
won't
be
able
to
see
what
they're
writing
and
I'm
I'm
still
unsure.
If
this
is
good
or
not,
but
we
will
give
it
a
try
to
see
how
that
goes.
So
you
won't
be
able
to
see
what
other
people
are.
A
A
A
A
Collaborate
with
their
peer
peers
to
I
don't
know
to
understand
what
is
the
best
way
to
approach
this
problem
and
these
requirements.
You
know
like
hey,
maybe
I'm
thinking
about
coding
it
this
way
or
using
this
library
or
something
like
that,
so
that
is
how
they
can
plan
to
complete
the
job
and
then
they're
trying
to
locate,
gather
the
materials
and
information
needed
for
the
job
might
be
to
find
existing
files
or
things
in
the
code
base
that
they
can
reuse
and
that
they
will
need
to
edit
modify
or
extend
and
and
so
on.
A
So
after
this
you,
you
go
through
all
of
these
stages
until
the
very
end
where,
ultimately,
what
I
assume-
and
that
is
my
personal
view-
and
of
course
I
might
be
biasing
right
now-
is
then
creating
a
proposal
that
can
be
reviewed
by
others
and
that
can
be
ultimately
integrated
into
the
code
base
and
maybe,
after
that,
they
have
some
additional
steps
that
they
need
to
do
after
they've
concluded
or
not.
Does
that
make
sense?
I
don't
want
to
go
through
everything.
That's
that's
the
activity
for
today,
but
does
this
give
you.
A
Okay,
good
any
other
questions
or
comments.
A
All
right,
okay,
so
let's
do
this
I'll,
give
10
minutes
again
focus
on
quantity
in
our
quality,
try
to
fill
out
as
much
as
possible
all
the
different
stages
and
the
timer
will
ring
when
it's
it
has
finished
so
10
minutes
and
or
actually
let
me
start
private
mode.
A
A
Okay
time
is
up:
let's
stop
I'll
give
just
a
few
seconds
if
someone
is
still
writing
anything
down
in
the
meantime,
I
will
open
or
stop
the
private
mode
and
reveal
the
advent
calendar
all
right.
A
This
is
great
and
yeah.
We
got
a
lot
of
quantity
here
and
so
now
what
we're
going
to
do-
and
this
is
also
again
going
to
be
a
silent
activity
for
five
minutes-
is
that
we're
going
to
everyone
together
and
they
don't
have
to
be
neatly
organized
but
we're
trying
to
group
similar
stickies
into
clusters,
and
you
can
do
that
below.
So
let
me
share
my
screen
in
the
blank
area
that
is
available
below
the
gray
stickies.
You
can
drag
them
into
clusters
and
you
can
also
drag
them
across.
A
So
if
you
think
that
a
particular
step
is
best
fit
under
a
specific
stage,
you
can
do
that
and
it's
going
to
be
a
bit
chaotic,
because
some
people
have
different
thoughts
than
others.
But
that's,
okay,
don't
worry,
and
we
can
debate
that
afterwards.
So
right
now,
these
first
two
activities,
the
first
one
we
just
did-
was
create
these
steps.
Now
we're
going
to
cluster
them
together
and
after
that,
we're
going
to
discuss
how
we're
going
to
narrow
it
down
and
reach
some
some
agreement
on
it.
A
Yeah
yeah,
it's
just,
I
think,
think
of
it
as
a
collaborative
clustering
and
we're
all
working
together
to
be
as
fast
as
possible
to
cluster
things,
instead
of
being
just
one
person
trying
to
do
everything
together.
So
if
you
want
to
make
it
easier,
if
you
want,
you
can
pick,
for
example,
a
stage
for
example.
A
Imagine
I
pick
the
prepare
one
to
start,
and
I
start
clustering
here
so
that
we
don't
all
start
with
the
before
phase,
for
example,
but
yeah
five
minutes
will
be
more
than
enough
time
to
cluster
them.
I
think.
A
B
A
A
A
So
now
we
have
almost
all
of
them
kind
of
grouped
and
what
I'm
going
to
ask
if
you're
not
doing
this
already
is
just
to
take
a
quick
glance
at
everything.
That's
there
to
see
if
some
groups,
for
example
in
let's
imagine
in
the
define
stage
if
they
are
repeated
in
the
locate
or
prepare
stage,
because
I
saw
some
stickies
across
those
three
stages
that
were
very
similar,
so
we
might
have
also
duplicate
groups
right
now.
A
A
Okay,
are
we
all
good
with
or
more
or
less
good,
with,
the
the
clusters.
B
A
B
A
That's
that's
a
great
point,
okay,
so
well.
We
can
now
start
everyone
discussing
the
clusters
now
that
we
have
organized
it
and
we
can
start
with
marcel's
question
about
what
concludes
the
job
and
to
to
my
understanding,
I'll
give.
My
personal
view
is
that
the
conclusion
of
the
job
is
sasha,
proposing
the
changes
that
addresses
them.
A
So
in
this
case,
sasha
or
this
specific
job
is
not
about
merging
the
changes,
because
this
persona
might
not
be
the
same
persona
that
merges
them
and
that
reviews
the
code
and
ensures
that
it's
all
according
to
the
standards.
So
in
this
case,
sasha's
job
is
just
to
propose
the
changes
that
she
thinks
addresses
the
product
requirements,
not
necessarily
merging
them.
That
might
be
the
case,
but
that's
that
can
also.
A
We
can
also
consider
that
a
separate
job
right,
because
that
entails
a
lot
of
other
things
that
can
be
done
by
someone
else.
What
what
does
everyone
think.
A
C
Sean
yeah
and
just
to
add
to
that
also,
we
may
have
more
than
one
mr
for
a
given
issue,
and
so
there
may
be
a
step
that
that
sasha
will
need
to
do
at
the
end,
which
is
to
either
the
issue
will
be
closed
automatically
or
the
sasha
will
need
to
close
the
issue
or
there
might
even
be
a
feedback
step
where
you
know.
There's
another
interaction
with
the
original
issue
author,
to
just
confirm
that
we've
covered
everything
or.
B
B
A
Right
and
in
that
sean,
what
you
were
hinting
at
is:
is
there
a
specific
step
that
already
captures
that
thought.
C
But
maybe
sasha
needs
to
close
it,
but
in
fact,
also
in
that
same
section
in
under
conclude,
there's
also
the
alternative
path
which
is
sasha
does
work
and
but
kind
of
towards
the
end
of
the
process.
C
A
decision
is
made
that,
in
fact,
the
issue
won't
be
fixed
and
you
know
it's
marked
what
won't
fix
and
closed,
which
can
sometimes
happen.
You
know
not
not
at
the
upset
but
later
on
in
the
process.
A
Okay,
yeah,
just
overall
david
and
michael,
do
you
have
any
specific
things
you
want?
You
want
to
address
now.
A
Okay,
so
what
what
we'll
do
now
until
the
remainder
of
the
time
is
to
try
to
decide
on
just
one
sticky
that
describes
these
clusters.
A
And
so
we
will
go
through
or
try
as
much
as
possible
to
go
through
the
all
of
the
clusters
that
we
have
here
and
I
can
write
the
the
one
sticky
that
we
can
then
move
to
these
stages.
Sorry
to
these
steps
here
below
the
map.
So
we
then
we
did
this
collaborative
activity
right
now,
we'll
decide
on.
For
example,
what
is
the
the
sticky
that
describes
all
of
these
here
whoops?
A
I
think
I
moved
okay,
I
think
I
moved
to
a
sticky
somewhere.
I
don't
know
where
and
and
then
we
will
move
or
I
can
do
that
later-
move
that
one
sticky
to
the
steps
here
and
again.
These
are
solution.
Agnostic
and
maybe
some
of
the
steps
that
you
had
written
here
can
then
be
used
as
actions
that
people
perform
specific
actions
that
people
perform
to
that
outcome
either
inside
of
gitlab
or
outside
of
kit
lab
so
yeah,
let's,
let's
get
started
with.
Oh
there
you
go.
I
think
this
is.
B
C
So
I
think
on
the
left,
we've
got,
you
know
this
is
the
requirement
that's
come
in,
so
we
could
get
that
via
an
email
or
we
could
discover
it
ourselves
and
then
the
next
step
is:
what
do
we
do
with
that?
Do
we
already
yeah.
A
A
C
I
mean,
I
would
say
the
next
one
is
to
is
to
identify
when
it
gets
worked
on,
so
we
might
have
an
issue,
but
we
don't
necessarily.
It
doesn't
necessarily
go
into
sasha's
chain
straight
away.
A
Okay,
let's,
let's
write
it
this
as
task
and
not
necessarily
issue
okay,
but
it's
more
solution.
Agnostic!
Okay,
in
this
one
understand
the
contribution
headlines
for
the
products.
B
A
A
Oh
and
there's
also
another
one
here
I
mean
not
only
understanding
the
project,
but
there's
one
here
that
calls
make
sure
you
have
a
local
copy
of
the
code.
I
think
this
is
a
separate
step
right,
so
it's
get
access
to
the
to
the
code
base
or
something
like
that.
A
A
Okay,
let's
let's
talk
about
this
one
first,
so
this
one
is
is
a
lot
here
all
right.
It
has
many
many
different
things,
but
in
the
end,
it's
probably,
I
guess,
collaborating
with.
Perhaps
this
one
collaborating
with
peers
to
plan
best
approach,
regardless
of
how
you
do
it.
You
know
there
are
different
ways
to
do
it,
but
the
ultimate
outcome
is
to
plan
the
best
approach
with
your
peers.
B
B
C
B
The
issue
to
estimate
would
match
the
one
on
the
previous
category
that
the
pm
prioritizes
it's
about
prioritization,
because
the
em
engineer
it
fluctuates
not
always
the
same,
but
it's
kind
of
like
the
same
task
like
to
help
with
the
prioritization
mm-hmm.
A
Yeah,
I
think
yeah
I
mean
it
depends
on
on
the
teams
right,
but
I
would
imagine
that
this
can.
A
B
B
For
the
collaborate
with
ps2
plan
best
approach,
I'm
wondering
if
that
actually
should
be
split
into
two
different
headlines,
because
one
we
have
the
find
the
right
solution.
A
Yeah,
I
think
I
mean
we
can
have
the
two
of
them.
If,
if
we
want,
because
there
can
be
like
an
individual
activity
first
and
then
you
share
that
with
others
and
you
get
their
input.
C
Yeah,
I
think
that's
absolutely
right.
I
think
you
might
start
to
investigate
it
and,
as
part
of
that
investigation,
you
might
ask
for
help
from
peers
or
you
might
ask
them
to
validate
your
approach
or
or
you
might
also
not
need
any
help
from
peers,
and
you
might
be
able
to
just
do
investigation
of
the
solutions
by
yourself.
B
A
Right
and
so
in
this
case
the
investigate
potential
solutions,
I
think,
is
related
to
these
two
stickies
right
yeah
I
mean,
and
there
are
other
things
that
you
can
do
as
a
part
of
investigating,
but
right
now
we're
focused
on
you
know,
consolidating
them
into
just
one
step.
C
B
B
B
From
I
was,
from
my
perspective,
being
able
to
navigate
the
doc
site,
fell
in
line
with
locating
the
solution
to
problems
or,
if
you're,
building
out
a
feature
being
able
to
locate
the
patterns.
We
usually
use
for
development
of
gitlab.
B
B
A
All
right-
and
this
doesn't
have
to
be
perfect-
we
can,
we
can
roll
with
it
and
yeah.
Don't
and
again,
don't
worry
that
we
will
have
two
other
groups
doing
the
same
thing
and
in
the
end
we
will
consolidate
everything
together
or
at
least
try
to
so
no
worries
determine
which
project
I
should
lodge
the
logic.
The
issue
find
a
place
encode
based
to
make
changes
to.
B
A
Okay,
so
this
one
is,
I
think-
or
at
least
these
two-
these
three
here
are
about.
You
know
just
access
to
the
project,
and
this
is,
I
believe,
something
that
might
have
come
earlier
here:
understanding
the
project
and
getting
access
to
the
code
base.
What
do
you
think.
A
B
A
B
On
like
the
ios
application
with
it
within
the
world
of
get
lab,
it
be
more
like
which
stage
group
do
I
put
this
label
to
that?
That
is
the
thing
that
or
like
who
should
I
notify,
so
that
was
that
these,
those
behind
that
were
sticky.
A
B
A
Yeah
this
one
also
so
engineers
you
produce
existing
code
base.
I
think
it's
is
that
similar
to
investigating
potential
solutions,
or
would
that.
A
A
Okay,
yeah,
okay,
so
so
this
is,
I
think,
again,
similar
to
investigating
potential
solutions,
but
it's
a
bit
more
practical
and
and
hands-on
that
you're
looking
at
the
code
base
itself
to
find
those
those
patterns.
B
A
Okay,
anyway,
we
still
have
a
few
things
here
to
go
through
and
we're
out
of
out
of
out
of
time,
but
what
I
will
do
is
after
we
end
this.
I
will
go
through
these
myself
and
add
these
yellow
stickies
here
and
then
move
them
down
to
the
steps
area
here,
and
the
next
phase
will
be
a
an
asynchronous
individual
work
so
between
tomorrow
and
the
15th.
A
So
today
we
were
collaborating
on
the
steps
which
I
will
add
here
and
you
can
add
more
steps
if
you,
if
you
want
during
that
async
period,
but
the
idea
is
mainly
to
add
stickies
here
to
the
actions,
feelings,
positive
feelings
and
thoughts
or
negative
feelings
and
thoughts,
pain,
points
and
opportunities
for
improvement
and
just
fill
this
out
as
much
as
possible.
A
And
then,
after
that,
yeah
you
have
the
rest
of
the
the
instructions
here,
but
right
now
that
is
the
main
activity
that
will
all
do
async.
Does
anyone
have
any
questions,
thoughts.
C
A
Exactly
here
now
in
this
this
part,
that's
called
a
map
for
the
actions,
feelings,
pain,
points
and
opportunities.
So
all
of
this,
that
is
blank
here,
try
to
fill
it
out
as
much
as
possible.
Okay,
all
right
and
then,
after
that,
we
will
review
all
of
that
together
in
a
wrap-up
session.
But
you
will
get
all
of
the
instructions
in
due
time
right
now.
A
Just
focus
on
that
part,
and
in
any
case
I
will
ping
you
all
again
in
this
issue,
so
that
you
can
look
at
the
instructions,
so
yeah
parting
thoughts
is,
if
you
still
have
a
bit
of
time,
to
share
your
emoji
of
how
you're
feeling
right
now
after
this
session.
A
Thank
you,
everyone,
thank
you
david,
and
let's
see
how
everyone
is
feeling
all
right.
Everyone
is
feeling
excited.
I
think
some
questions
lingering
of
how
we
will
do
this,
but
it
was
very
good
to
have
you
all
here.
Thank
you
all
for
joining,
and
I
hope
you
have
a
great
great
rest
of
your
day
and
week
thanks.