►
Description
Pedro Moreira da Silva, Staff Product Designer in the Code Review team at GitLab, welcomes the Product Designers from other related teams to a hypothesis generation workshop. The workshop will be focused on generating ideas to a specific problem of the merge request (MR) experience.
- Workshop issue: https://gitlab.com/gitlab-org/gitlab/-/issues/355468
- Epic: https://gitlab.com/groups/gitlab-org/-/epics/7592
A
Hi
everyone
thanks
for
watching
this
video
and
for
participating
in
the
hypothesis
generation
workshop
for
restructure.
Mrs
and
I'm
gonna
walk
you
through
what
the
preparation
is
going
to
be
for
this
workshop,
what
you
need
to
do
before
we
all
meet
together
and
yeah,
just
a
brief
overview
of
the
preparation
materials.
So,
let's
get
to
it.
A
So
this
is
the
issue
where
you've
been
pinged
and
where
you're
assigned
feel
free
to
read
the
description
in
full,
but
right
now
I'm
going
to
focus
on
this
section,
the
prep
materials
so
first
of
all,
I'd
like
for
you
to
get
familiar
with
the
spotify's
thoughtful
execution
framework
and
this
links
to
a
pdf
how-to,
which
I
invite
you
to
read
in
in
full.
It's
very
easy
to
follow.
This
is
the
contents
where
you
learn
step
by
step
about
this
framework
that
we're
using.
A
This
is
the
first
time
we're
experimenting
with
it,
and
I
feel
that
it
aligns
very
well
with
the
way
that
we
work
at
gitlab
and
allows
us
to
focus
and
link
each
step
of
our
design
process
in
a
thoughtful
way,
as
the
framework
is
called.
So
we
will
understand
how
to
set
a
goal.
What
is
the
data
and
insights
and
how
to
support
the
problem
opportunities?
A
How
we
can
then
ideate
on
hypothesis,
the
solutions
and
learnings
and
for
us
the
focus
of
the
workshop
will
be
on
this
fourth
step,
the
hypothesis
and
you
will
see
along
the
way
here
with
examples
of
specific
data
and
insights
and
opportunities
and
hypotheses
how
all
of
this
comes
together.
So
again,
please
read
through
this
14
page
pdf
that
will
show
you
how
all
of
this
comes
together.
A
Then.
I
would
like
for
you
to
review
the
workshop
mural
focusing
on
two
areas:
the
problem
statement
and
relevant
insights,
and
also
the
workshop
area,
which
is
colored
in
pink,
specifically,
the
instructions
of
the
activities
that
we
will
do,
and
that
will
be
the
focus
of
our
workshop.
That
will
be
the
lightning
demos
and
the
hypothesis
generation.
A
What
we
feel
is
the
core
problem
that
permeates
the
whole
structure
and
that
will
you
know,
influence
everything
else
that
we
will
do
around
the
experience,
and
that
is
how
might
we
help
sasha
and
sasha?
Is
a
software
developer
persona
and
there's
a
link
here?
If
you
want
to
learn
more
about
them,
how
might
we
help
sasha,
navigate
and
triage
comments,
findings
and
changes
and
related
to
this?
How
might
we
this
problem
statement?
A
We
have
relevant
data
insights
that
we
put
together
for
you
that
will
provide
you
with
the
support
that
you
need
to
ideate
around
this
problem,
and
we
know
this
is
an
ambitious
problem.
This
is
a
broad
problem,
but
we
wanted
to
keep
it
that
way
if
it
was
too
narrow
or
too
broad,
it
would
trump
and
would
harm
our
ideation
process.
A
So
we
feel
that
this
is
just
the
right
balance
of
broadness
to
encourage
us
to
have
many
different
ideas
and
experiment
with
many
different
directions
to
solve
this
challenge,
as
I
said
here
below
the
relevant
data
insights,
that
will
support
you
in
your
design
process
in
ideation.
In
our
workshop
and
here
on
this
side,
you
can
see
a
user
flow
where
we've
mapped
out
all
of
the
different
steps
that
the
author
of
merge
request
must
take
and
then
below
you'll
see
the
reviewer
and
what
they
also
do.
A
And
again
I
invite
you
to
review
it
and
see
it
throughout,
but
the
focus
of
the
workshop
again
related
to
the
problem
statement
of
how
we
might
help
sasha
navigate
triage
comments,
findings
and
changes.
The
focus
if
we
look
at
this
user
flow
is
this
area
that
is
highlighted
by
this
box
and
inside
of
it
these
two
circles
at
the
top.
We
have
what
we
would
call
the
review
cycle
for
and
those
actions
that
happen
in
parallel
and
that
are
the
focus
of
the
author
and
below.
A
A
You
already
have
your
names
here
to
add
your
own
content
and
try
to
stick
to
the
durations
that
we
explained
here.
So
no
more
that
one
hour
dedicated
to
homework
time
and
to
add
your
demos
to
this
area
here
and
then
please
review
on
your
own
all
of
the
other
instructions
here
with
a
focus
on
the
hypothesis
generation.
So
this
big
area
that
is
numbered
with
the
number
four
it
has
instructions
on
what
we
will
do
so
again
read
through
it,
see
if
it
all
makes
sense
or
not.
A
After
that,
I
would
like
for
you
to
test
uploading
a
photo
to
mural,
because
that's
one
of
the
things
that
we
will
do
here
is
publish
and
share
with
others.
Our
crazy
8
sketches
that
we
will
sketch
out
by
hand
using
pen
and
paper
or
pencil,
and
we
will
then
upload
them
to
mural
during
the
workshop
and
paste
them
here,
so
that
others
can
see
them
so
to
try
this
out.
A
However,
you
would
like,
but
please
make
sure
that
you
have
a
process
for
having
the
photos
here
and
that
it
works
well
before
the
workshop
and
then
finally,
please
continue
to
the
activities
of
the
before
workshop,
and
we
can
take
a
look
at
those
now
so
before
the
workshop
in
total,
we
think
a
maximum
of
two
hours
of
your
time
will
be
needed
for
this
week.
The
week
of
march
21st
again
review
the
prep
materials,
which
is
more
or
less
what
we're
going
through
now,
but
please
do
that
on
your
own.
A
If
you
have
specific
questions
that
could
that
are
related
to
the
mural
of
the
workshop,
the
data
and
insights,
the
problem,
the
user
flow,
this
whole
section
with
the
lightning
demos,
the
hypothesis
generation,
the
workshop
area.
Please
try
to
add
them
as
a
comment,
and
for
that
you
can
just
right.
Click
and
select.
Add
comments
in
the
area
related
to
your
question
and
I'll.
Try
me
and
annabelle
will
try
to
answer
your
your
concerns
other
than
that
any
other
general
questions.
A
If
you
want,
you
can
already
do
this
and
contribute
the
lightning
demo
if
you
want
to
invest
that
time
now,
so
it's
okay,
we're
just
splitting
this
up
in
these
two
weeks,
so
that
it's
easier
for
you
to
manage
your
own
time
and
you
know,
participate
in
this
workshop
clicking
on
this
link.
Lightning
demo
will
direct
you
to
this
area,
which
has
all
of
the
instructions
and
things
that
you
need
to
know
to
contribute.
A
So
you
can
see
those
here
and
after
that,
before
the
workshop,
we
will
remind
everyone
to
watch
the
videos
when
they're
all
done
and
when
everyone
has
uploaded
their
videos
here
and
has
added
their
ideas
in
the
stickies.
So
we
will
remind
everyone
to
watch
the
lightning
demos.
It
will
be
a
maximum
of
30
minutes
because
we're
trying
to
restrict
the
time
of
each
video
to
just
three
minutes
so
very
concise
videos,
focusing
on
just
the
essentials
of
the
solutions
that
you
find
in
the
ideas
and
ideally
watching.
A
This
will
be
on
the
last
day
before
the
workshop
begins.
So
we
have
the
workshop
on
april
4th
if
you're
able
to
watch
the
liking
demos
just
before
the
workshop.
That
would
be
perfect
so
that
it's
fresh
on
your
mind
before
we
jump
into
it
and
start
working,
then
we
will
have
the
workshop
itself,
and
this
is
just
a
an
outline
of
more
or
less
what
we
will
do
during
the
workshop.
A
But
you
don't
need
to
focus
on
that
right
now,
because
I'll
be
facilitating
it
and
I'll
walk
you
through
everything.
On
the
day
after
that,
after
the
workshop
out
on
the
week
of
april
4th,
we
will
review
the
ideas
and
ask
and
answer
questions
in
the
mural
async.
So
after
everyone
has
added
and
contributed
their
sketches
and
ideas
for
potential
hypotheses,
you
are
free
to
review
these
ideas
and
ask
questions
from
others,
and
they
will
reply
to
you
async
during
this
week.
A
A
Thank
you
so
much
for
your
time.
I
hope
that
this
was
informative.
Again,
let
us
know
if
you
have
any
questions.
You
can
add
them
here
in
this
brained-up
mural
or
if
they're
specific,
to
the
structure
of
the
workshop
and
the
activities
and
problems
and
insights.
You
can
add
specific
comments
here
in
the
mural.