►
Description
Pedro Moreira da Silva, Staff Product Designer of Create:Code Review, introduces the activities that will contribute to a hypothesis-based user journey map of the Create stage.
Epic: https://gitlab.com/groups/gitlab-org/-/epics/6964
A
A
A
And
ideally,
this
will
allow
us
to
identify
where
we
have
gaps
in
our
confidence
and
that
will
so
that
we
can
then
dig
deeper
and
perform
research
on
those
gaps.
And
after
that,
ideally,
we
can
then
create
a
research-based
user
journey
map.
That's
the
most
valuable
user
journey
map,
because
it
the
foundations,
are
rock
solid
because
they're
based
on
actual
research
that
we
get
from
users.
A
But
for
now
let's
do
the
hypothesis
base
so
that
we
can
get
this
out
of
the
door.
And
for
this
I
have
split
the
domain
counterparts
across
the
create
stage
groups
into
different
time
zone
groups.
So
we
will
have
engineering
managers,
product
designers,
product
managers,
the
technical
writer
amy
and
our
ux
researcher
ben
join
us
in
different
time
zone
groups,
and
you
will
collaborate
with
people
that
you
usually
don't
work
with,
that
belong
to
other,
create
groups,
and
we
will
all
together,
create
a
create
stage
user
journey
map.
A
So
each
group,
depending
on
their
time
zone,
will
go
through
different
activities.
I
will
be
your
facilitator
and
I
haven't
introduced
myself
for
those
of
you
who
don't
know
me.
I'm
pedro
and
I'm
based
in
lisbon,
portugal
and
I'm
the
staff
product
designer
for
the
create
code
review
group
and
the
activities
that
we're
going
through
are
three
two
of
them
sync
and
one
of
them
async.
So
the
first
one
is
a
synchronous
session
where
we
introduce
all
of
these
activities
and
we
brainstorm
around
the
steps.
A
And
so,
as
you
can
see
here
in
this
mural
that
you
should
all
have
access
to.
The
first
step
is
brainstorming
the
different
steps
that
make
up
this
user
journey.
And
what
do
I
mean
by
this?
So
we
have
the
phases
here
at
the
top
before,
during
and
after
in
the
end
and
below
those
phases,
we
have
stages
and
the
stages
are
basically
high-level
steps
that
are
solution,
agnostic
of
what
the
user
is
trying
to
accomplish,
not
necessarily
what
they're
doing,
but
what
they're
trying
to
accomplish
to
perform
the
job
and
for
further
context.
A
You
can
see
here
at
the
top
that
we
have
identified
a
persona
and
the
job
to
be
done,
and
these
are
very
very
important,
and
I
encourage
you
to
take
a
deep
look
at
the
persona
and
the
job
to
be
done.
In
this
case,
we
will
be
targeting
the
sasha,
so
the
software
developer,
persona
and
there's
a
description
here
and
motivations
and
their
frustrations
and
job
to
be
done
is
when
product
improvements
are
identified.
A
That
is
the
situation
of
the
job
to
be
done.
I
want
to
propose
changes
that
address
them.
That
is
the
job
so
that
I
can
help
build
a
better
product.
That
is
the
outcome,
and
so
with
this
job
to
be
done
with
this
situation
with
this
job
and
with
this
desired
outcome
that
we're
going
to
navigate
that
journey
and
add
steps
below
these
stages.
A
So
we're
going
to
brainstorm
here
in
this
section
where
you
can
see
all
of
these
blank
sticky
notes
and
we're
going
to
together,
add
ideas
about
what
steps
go
under
each
of
these
stages.
So,
for
example,
before
even
users
start
performing
this
job
to
propose
changes
that
address
product
improvements.
A
Collect
or
or
or,
engage,
or
who
they
need
to
engage
with
before
they
even
start
this,
and
then
all
of
the
default
below
each
stage,
for
example,
in
the
defined
stage,
which
is
to
determine
the
objective
and
plan
approach
to
complete
job.
What
do
we
need
to
do
for
the
locate
for
the
prepare
for
the
confirm
and
so
on?
A
So,
in
this
case
for
the
apac
emea
time
zone
group,
it
will
be
between
the
first
and
the
15th
of
december,
where
during
this
time,
what
I
would
expect
you
to
do
is
to
add
stickies
with
ideas
to
the
other
sections
here
and
try
to
fill
this
up
as
much
as
possible
and
remember.
All
of
this
is
just
based
on
your
experience,
your
assumptions,
your
hypothesis,
it
doesn't
have
to
be
right.
A
A
And
after
that
we
will
vote
on
the
things
that
you
have
the
least
and
the
most
confidence
on.
So
ideally,
this
map
will
be
filled
with
stickies
and
you
will
then
say.
Oh
this,
I
have
very
high
confidence.
I
don't
think
we
need
to
do
more
research
on
this,
but
this
part,
I'm
not
so
sure,
and
so
we
will
have
10
votes.
A
I
think
for
each
voting
session
and
we
will
highlight
the
things
that
we
need
to
do
more
research
on
and
the
things
that
we
shouldn't
dedicate
more
time
researching,
because
we
already
have
a
high
confidence
and
that's
a
quick
overview.
I
invite
you
to
look
and
read
through
your
time
zone
group
issue
again,
I
will
assign
you
to
the
issue
so
that
you
know
which
issue
is
your
group?
A
Don't
worry
and
also
linked
here
at
the
top,
and
also
here
in
this
first
section
of
the
goal
you
have
the
epic,
which
I
encourage
everyone
to
read
and
understand
what
is
the
context?
What
is
the
ultimate
goal
of
what
we're
trying
to
do
here
and,
in
the
end
being
a
hypothesis-based
map
and
with
the
synchronous
activities?